CTRL+Enter posts replies
-
Issue: CTRL+Enter posts a reply
Expected: CTRL+Enter starts a newline
-
-
I'm pretty sure Ctrl+enter is the accepted combination for "Send now" in multi-line inputs.
-
Go ahead and do it in excel (or google docs version of excel)
Jeff seems to compare his software in every other way to it.
-
Tab+Enter is the way I always submit. Ctrl+Enter should be a new line.
-
On OSX, you'd expect Cmd+Enter to submit. (And it does…)
-
In areas where enter is usually expected to send a message (e.g. IM clients like facebook messenger, MSN messenger, steam messenger and probably many more) CTRL+ENTER provides a carriage return.
It seems to make some sense to me that in this inverse situation (where enter is NOT expected to submit) CTRL+Enter would do so.
maybe that's just me though.
-
What exactly is the point of pressing Ctrl+enter though? Just enter does newlines fine.
-
Sometimes Enter sends the message (Facebook or Office Communicator) and in that instance I always use Shift+Enter for a new line, which I've always understood to be the standard for a new line where Enter submits.
I'd expect Ctrl+Enter to submit a message where Enter does a new line, but only because that's what Outlook does, although I didn't expect Discourse to have a keyboard shortcut.
-
Gmail sends a mail with CRTL Enter as well.
I'd guess this is as designed?
Our replies aren't single line IMs flying back and forth, more like longer, less frequent email type communications...?
-
Considering they're using vi keyboard commands for navigation with j and k I guess we're lucky they didn't opt for :wq or something.
I've just noticed if you use j and k then you get a red bar against the 'current' post but the current post green bar still shows the post number for the one at the bottom of the viewport. More Discoursistency.
-
Speaking of keyboard short cuts, is it listed on '?' Menu?
/Mobile
-
Negative. For Discoreasons it's the tooltip on the Reply button.
-
Wait, what? D:
-
In areas where enter is usually expected to send a message (e.g. IM clients like facebook messenger, MSN messenger, steam messenger and probably many more) CTRL+ENTER provides a carriage return.
You know on Classic Mac, SINCE EVERYBODY LOVES TO HEAR ME TALK ABOUT THAT, "Enter" and "Return" were too different keys, solving this particular problem EVEN BEFORE IT CAME UP!
-
Hypercard also solved everything. Also, why doesn't every town have blacksmiths anymore? @blakeyrat?
-
You know on Classic Mac, SINCE EVERYBODY LOVES TO HEAR ME TALK ABOUT THAT, "Enter" and "Return" were too different keys, solving this particular problem EVEN BEFORE IT CAME UP!
what made them too different? was it their two different functions?
Filed Under: Pedantic Dickweedery
-
Feh, it's obvious to anybody who used a typewriter!
Return issued a carriage return.
Enter entered the information into the computer.
Since they were too different keys, you didn't need the modifiers modern OSes do because they stupidly overload these two completely different functions onto one physical key.
-
Feh, it's obvious to anybody who used a typewriter!
Heh...now that's funny, I don't care who you are.
-
Bug: Hold down J or K for a few seconds to jump past a bunch of posts.
Expected: Topic scrolls up/down how many ever posts you just jumped past.
Actual: watch browser spaz out and start jumping up and down for a few seconds after you let go of key, eventually stopping barely a few posts from where you started.
--it works a little better if the topic is small and all the posts are already loaded into memory.
-
Hmm...and then it goes down to the suggested topics. Isn't that new? Still spazzy.
-
The clear resolution to this issue is to send a PR to the DiscoTeam so that Discourse loads on whatever web browser Mac Classic uses.
-
I got multiple posts highlighted at the same time by doing that.
Do I win?
-
then it goes down to the suggested topics. Isn't that new?
Nah, it's done that for a long time. It makes no sense, but is apparently BYDESIGN WONTFIX.
-
-
wtf i just got a 'You do not have permission to view that topic' error when clicking on the notification to view this topic.
@sam.
-
Ctrl+Enter has become commonplace in desktop apps and web apps using multiline or rich text fields over the years. As loopback0 said, use plain old Enter or Shift+Enter instead.
This is one of the few things that Discourse does right. Seriously, legitimate case for WONTFIX here.
-
The whole reason i was using ctrl+enter was accidental since I was doing so many bug posts. But When I did it my replies just vanished (ie: posted)
-
Yes, that's the only way I've used ctrl+enter here.
-
wtf i just got a 'You do not have permission to view that topic' error when clicking on the notification to view this topic.
You sometimes get that if you got a notification about a topic you're already viewing and clicked it before the topic finished populating whatever the notification was about... RACE CONDITIONS FTW.
-
What exactly is the point of pressing Ctrl+enter though?
To submit a post? That's what I use it on here for. Sometimes accidentally...
Hmm...and then it goes down to the suggested topics. Isn't that new? Still spazzy.
Old. J, J, Jdown to last post, one more J, to select the first topic in suggested then O to open it.
-
-
This is one of the few things that Discourse does right. Seriously, legitimate case for WONTFIX here.
Yeah - it's just a shame it's not more discoverable.
-
I've just noticed if you use j and k then you get a red bar against the 'current' post
Until some event, e.g., liking, causes Dicsores to forget it has a current post.
-
Actual: watch browser spaz out and start jumping up and down for a few seconds after you let go of key,
Yes, J-ing faster than AJAX can load new stuff into the DOM has unpredictable results. It happens to me somewhat often on that topic when I'm liking without reading.
-
You should only be able to submit via Alt + S
-
True. It's one of those emerging UI 'unspoken rules' like the hamburger menu, but much more mature.
-
-
Feh! Missing an obvious opportunity to make a CyberDog joke! I am disappoint.