do not send messages when <enter> is pressed. change to another shortcut key.
I have to edit my messages several times because every time I press enter for a Carriage Return, it sends instead. I know the shortcut key for Carriage Return is SHIFT+ENTER but its not very intuitive and makes for miscommunication. Thank you for your consideration.
I've hit Enter accidently so many times for several reasons.
Can we get a "user option" of sorts to turn off Enter as the mechanism to send messages and instead have to click the Send button with the mouse and/or use some keypress combination?
That would be SUPER helpful! Thanks.
To those that swear by having Enter be the Send command. I get it, but we all have different styles, finger shapes and sizes, keyboards, etc. Having the OPTION, everyone would get what works best for their situation.
Michael Fricklas commented
i completely agree. could also add a button for send rather than Enter! Way too many unintended sends
Do not send messages when <enter> is pressed. It is annoying and time wasting.
What's wrong with pressing the arrow key to send or Ctl-S to send?
agreed. Should have option to turn this off. or use Shift+Enter to send...
Stig Nygaard commented
100% agree. I keep sending wrong or unfinished messages.
Either make it possible to assign another shortcut or disable shortcut for this completely.
This is ridiculous. Change it back to Enter sending the message, Shift+Enter adding a new line like very other chat program on the planet! >:|
Teams is a messaging service, not a proposal-writing, collaboration tool. That should be done with shared documents in OneDrive or email.
Timo Kunze commented
In pretty much every program that accepts multi-line texts, ENTER enters a carriage return. I keep sending messages accidently in MS Teams because it behaves different and this is really annoying. It is also not consistent that you must press ENTER to enter a new list item, but must not press ENTER to enter a carriage return. In my opinion it should be like this:
- ENTER enters a carriage return or a new list item
- SHIFT+ENTER enters a carriage return within a list item
- CTRL+ENTER sends the message
I agree that the behavior for the first two actions is not 100% consistent either, but it is how most programs work. For me it would also be fine if ENTER within a list item enters a carriage return within this list item, while SHIFT+ENTER adds a new list item.
Dan Masci commented
Please add! This makes for SO MUCH miscommunication - especially when trying to send a message to a Client and sending a half-finished, non-proof-read, supposedly-professional message.
I agree with Bart too. Absolutely, 100%
Agree 100% with @Bart Read
+1 Good idea to stop sending on ENTER, and force using the send arrow instead.
Bart Read commented
Sending on ENTER is extremely annoying, and it doesn't help that the behaviour on ENTER changes when you enter a bulleted list or preformatted text.
I've lost count of the number of times I've sent a message when I wanted to add a new paragraph, and this can actually be a pretty serious problem.
1. You send the message unedited, people read it and start responding to it.
2. They end up responding to an incomplete thought: it's unhelpful and can side-track debate.
3. People may not notice or read your edited message.
4. All of the above leads to time wasted due to misunderstandings and clarifications.
5. All of the above problems are exacerbated when you're using Teams to communicate about an incident, where accurate and clear communication is key because people are under pressure to get the incident resolved as quickly as possible.
Please at least offer the option to disable ENTER as the shortcut to send a message, or offer CTRL+ENTER to send as per Outlook which, after all, is also part of the Office 365 suite and predates Teams by a couple of decades. Let's try to get some consistency across the tools here, please!
Ok, I agree with "sending by pressing ENTER ist standard in chat", but what should be the problem leaving this decision to the user? If MS made it configurable all the people crying around "this is standard behaviour of chat programs" are fine and all the others too? So why arguing what would be the better way when you can have both???
Vítězslav Ackermann Ferko commented
The `Enter` key is widely inconsistent in the app. Consider how differently it behaves in text, code blocks and lists.
If you are in a list or code block, you need to hit Enter three times to send the message, because
1. creates new line
2. exits the code block/list
3. submits the message
Not making a mistake with this is much more cognitively difficult than having an extra key combination to send a message.
Just look at this gif and I can tell you, I rehearsed several times and I still did all kinds of mistakes.
Jim Mundane commented
Unlike the previous comment suggests we can't say everything we need to say i simple slogans in Teams Conversations.
Our work requires more complex messages than "yup" and likes. We often describe technical issues in the Channels. The Enter as send make me rage several times a day.
Otherwise we might aswell just to go back to using e-mail and keep the internal talk outside Teams.
But I agree that a Chat function use Enter for send. But that is an entire different function than we expect from the Team Channel Conversations.
Please reverse this back to making ENTER send the message, like all the other chat clients. It isn't a word processor. It's a chat client. HipChat, Slack, Discord, Google Hangouts, they all SEND when you hit ENTER.
Yes!! CNTL Enter= send, Enter= next line. Kind of like ALL other programs since the dawn of word processing ...
Why did MS change this?
Oh, wow... enter takes meto the next line here in this comment section .... how novel.
Pls fix ASAP.
Justin Dao commented
+1 Would love the option to stop sending on ENTER, and force using the send arrow instead.
+1 from me - so annoying to have to continually go to ... / Edit
LinkedIn changed it years ago, so i am sure Micrsosft can introduce a similar functionality to be more user friendly
Reverse ENTER with SHIFT+ENTER