Conversation
Notices
-
Why is pressing enter default for line break? Shouldn't that be shift+enter?
Wednesday, 13-Nov-13 17:01:35 UTC from web-
@nerthos It is shift+enter, and it should just be enter.
Wednesday, 13-Nov-13 17:02:47 UTC from web-
@balance As a general rule, changing methods that have been used for over two years without a good reason is bad.
Wednesday, 13-Nov-13 17:04:30 UTC from web-
@nerthos Then the change to shift+enter never should have happened. I am, of course, talking about the decades of just enter being used, not this specific site.
Wednesday, 13-Nov-13 17:05:44 UTC from web-
@balance Shift+enter is a better option for systems where short, fast messages are used, like this site. Just enter is better when the interaction is based on long text posts with marked paragraphs.
Wednesday, 13-Nov-13 17:07:37 UTC from web-
@nerthos You are indeed correct, although standardization is often appreciated. If you've had a pile of RAM while building a computer from spare parts... You'll understand my point (though not necessarily agree).
Wednesday, 13-Nov-13 17:16:56 UTC from web-
@balance Yeah, I'm familiar with building things. I try to classify parts though.
Wednesday, 13-Nov-13 17:19:05 UTC from web
-
-
-
-
-
-
@nerthos Or maybe there's something that causes it to work that way sometimes without any notification.
Wednesday, 13-Nov-13 17:03:28 UTC from web -
@nerthos I'm not able to reproduce any of these. Try a hard refresh, and if it still doesn't work, try it without your RDN Refresh enabled.
Wednesday, 13-Nov-13 17:03:57 UTC from web
-
