This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I am often working in other windows but have a lot of teams messages that I need to address. This results in my sending meaningless messages accidentally when I hit ENTER thinking I am in a different window but I am really in teams. How do I by default prevent the ENTER button from sending a message?
Conversations involving multiple participants, allowing collaboration and information sharing in Teams
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
You might try mapping enter to shift-enter, and mapping shift-enter to ctrl-enter.
If you hit ctrl-enter, it sends from either mode, and shift-enter enters a newline in either mode. There might be a combo that gets you the behavior you want.
This portion of my example script:
#HotIf WinActive("ahk_exe ms-teams.exe")
will limit this hotkey to ONLY swap the keymapping within teams.
I had independently tried an AutoHotKey fix to map shift+enter to enter and vice versa. I threw it away because I couldn't find a way to make the script understand the format vs normal mode. Swapping the keys just swaps the mode in which the accidental sends happen, and it turns out I use both.
If there is to be an keyboard shortcut for something that isn't related to entering text, it needs to be constant through editing modes. An exception for letters and caps lock, but if I miss that mode toggle then I'm only shouting and that I can edit before the message is sent out.
Funny thing, in this text entry box, enter does as enter should even before I click a format function.
This portion of my example script:
#HotIf WinActive("ahk_exe ms-teams.exe")
will limit this hotkey to ONLY swap the keymapping within teams.
I noticed that copilote opened as side widow in Edge actually doesn't use return key as send.
So why not change it everywhere? Open AI even professional part still has the same problem. For a web app it must be even easier, unless the basic on event javascript can't tell if the key is sent or return.
So why don't they do it?
This is starting to sound sinister.
I just made a new modal interface for my car. It has normal mode, and hill mode. Toggle by clicking the mode button next to the start/stop button.
In hill mode, press the accelerator to slow, and the brake pedal to accelerate. There will be a light just behind the steering wheel to tell you what mode you are in. I recommend looking at the road while you drive.
This is how using 'shift+enter to linefeed', except when it is 'enter to linefeed' feels to me.
A less extreme metaphor: there are vi, emacs, and notepad people. Each gets used to their interface and it becomes physical memory. Very very few of them toggle back and forth on a paragraph to paragraph basis - that way lies madness.
In the mobile app, there is no issue using two separate keys to perform these independent functions regardless of input mode. Surely a more consistent customer feel would be achieved by giving an option to change this default functionality.