5 ms·

We already have two keys, they are called Shift and Enter

sippeangelo 1y ago
I think I have about a 50% success rate in typing a multiline message without accidentally sending it early, having to edit / copy and delete the message and finish typing it before the recipient has a chance to read it, confusing both me and them in the process.
- pytness 1y ago
  Same but with editing a message on a browser and trying to delete a word with Ctrl+w
- lelanthran 1y ago
  > I think I have about a 50% success rate in typing a multiline message without accidentally sending it early, having to edit / copy and delete the message and finish typing it before the recipient has a chance to read it, confusing both me and them in the process. That won't change if you had a different dedicated key for "move one line down but don't send `enter` keycode". You'd still accidentally hit `enter` due to muscle memory. After all, if you could get past muscle memory, you'd simply press Shift while hitting Enter.
- xnorswap 1y ago
  A similar frustration / reason for getting it wrong sometimes: in slack, the behaviour of shift+enter entirely reverses if you're inside a multi-line code block. If you normally have enter to send and shift+enter to line break, then it'll do the opposite while inside a code block. This is useful if you're trying to type verbatim inside a block, it's less so if you have a strong muscle-memory to shift+enter and do so while in the code block and find yourself sending half a message. I also use a mixture of teams, discord and slack, and while slack does allow for customisations, I'd always rather get used to defaults to avoid having to configure on every machine I use. There isn't quite a consistent well agreed default for the behaviour across applications, and that too is a source of frustration. So I've taken to typing up any long messages in a PM to myself, and then copying that out to my intended target once I'm ready.
  - arp242 1y ago
    > in slack, the behaviour of shift+enter entirely reverses if you're inside a multi-line code block There's a setting to turn that off so it behaves consistently. Or there was last time I used Slack.
    - xnorswap 1y ago
      Indeed, it was browsing settings which made me realise the root cause of why I was accidentally sending so many messages. But changing settings on platforms which I need to use across different computers and accounts is also cause for frustration, so I try to adapt to the defaults, no matter how frustrating.
    - pletnes 1y ago
      Thanks!
fedeb95 1y ago
yes but you have to type sfhit+enter, while a single "new line key inside the message" would be better for the specific task.

I think I have about a 50% success rate in typing a multiline message without accidentally sending it early, having to edit / copy and delete the message and finish typing it before the recipient has a chance to read it, confusing both me and them in the process.

pytness 1y ago
Same but with editing a message on a browser and trying to delete a word with Ctrl+w
lelanthran 1y ago
> I think I have about a 50% success rate in typing a multiline message without accidentally sending it early, having to edit / copy and delete the message and finish typing it before the recipient has a chance to read it, confusing both me and them in the process. That won't change if you had a different dedicated key for "move one line down but don't send `enter` keycode". You'd still accidentally hit `enter` due to muscle memory. After all, if you could get past muscle memory, you'd simply press Shift while hitting Enter.
xnorswap 1y ago
A similar frustration / reason for getting it wrong sometimes: in slack, the behaviour of shift+enter entirely reverses if you're inside a multi-line code block. If you normally have enter to send and shift+enter to line break, then it'll do the opposite while inside a code block. This is useful if you're trying to type verbatim inside a block, it's less so if you have a strong muscle-memory to shift+enter and do so while in the code block and find yourself sending half a message. I also use a mixture of teams, discord and slack, and while slack does allow for customisations, I'd always rather get used to defaults to avoid having to configure on every machine I use. There isn't quite a consistent well agreed default for the behaviour across applications, and that too is a source of frustration. So I've taken to typing up any long messages in a PM to myself, and then copying that out to my intended target once I'm ready.
- arp242 1y ago
  > in slack, the behaviour of shift+enter entirely reverses if you're inside a multi-line code block There's a setting to turn that off so it behaves consistently. Or there was last time I used Slack.
  - xnorswap 1y ago
    Indeed, it was browsing settings which made me realise the root cause of why I was accidentally sending so many messages. But changing settings on platforms which I need to use across different computers and accounts is also cause for frustration, so I try to adapt to the defaults, no matter how frustrating.
  - pletnes 1y ago
    Thanks!

fedeb95 1y ago

yes but you have to type sfhit+enter, while a single "new line key inside the message" would be better for the specific task.