[Feature request] Let the user decide the behavior of pressing Enter

[leafcutterant]

• I have searched open and closed issues for duplicates

---

Feature request

Most of us have had the frustrating experience (on any platform) of inadvertently sending an unfinished message, either by pressing Enter wanting to insert a line break, or by pressing Enter by mistake. Facebook's comments ushered in an annoying era where Enter means "Send" by default, but it needs not be this way on every platform. Many messaging clients (Pidgin and Skype come to my mind, but surely there are others) let the user decide what Enter does, because a good deal of people are not able or willing to rewire their text composing practices.

It would be nice to have this choice in Signal too. Therefore, I'd like to request a setting that controls the function of these two sets of key combinations:

1 Enter
2 Shift+Enter, Ctrl-Enter, Alt/Cmd+Enter*

One state of the setting would tie set 1 to sending and set 2 to a inserting line break, the other state would switch it all around. (*Maybe with the exception of Alt/Cmd+Enter - this combination for sending a message feels out of place.)

The default state of the setting should understandably be the former one in order to not confuse the users who already got used to the way these key combinations works now. Those looking for a change would easily find and set it.

Platform info

Operating System: Windows 7 x64
Signal version: Desktop 1.0.35

[DirkPitt1]

I totally agree. Android app has such option but Desktop don't. Very frustrating sometimes.

[sm8ps]

I just started writing a feature request when I found this existing one. The current behavior of the Signal desktop app is highly unintuitive on a regular keyboard and has led to so many "disrupted" messages.

Please, please add a setting like in the Android app to the desktop app as well! -- I am sorry that I cannot be of help because my experience with JavaScript is nil.

[sm8ps]

Meanwhile I have discovered that the issue does have at least a work-around. Since a while the input box can be enlarged from the single line to multiple ones. In this state, the enter key behaves as expected in an input box.

I cannot recall since when this behavior has been available, but I would call it a solution to the issue and suggest closing it.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.