Update search so that “Enter” submits the search and “Shift+Enter” creates a new line.
complete
R
Roland Boquiren
> I don’t think multi-line search should be the default. If you want multilines in search it should be Shift+Enter.
From John:
> Reasonable. I kinda expected more people to feel this way when I implemented search, but you’re the first to comment on it (there has also been at least one comment in the opposite direction, expressing enthusiasm for the current choice). What you’re requesting is obviously the convention though. Even though I like the current approach, I tend to think you’re correct.
I think the (unproven) argument in favor of keeping the current approach would be:
> 1. Most users have no idea that
Shift+Enter
is possible, so switching to the convention is, for most users, akin to removing the ability to break a search up into multiple lines.> 2. Most users would prefer to be able to break search into multi-lines and submit with
Command+Enter
vs not being able to break a search into multiple lines and submit with Enter
.>
Maybe we can include a question asking about this in the next Comms Monthly Survey
RN Guerrero
complete
Ivan Erceg
In Comms we use Return to format the search terms across multiple lines and then use Command+Return to actually start searching. We do this for convenience but I personally find this very inconvenient. I am not away of any search that works this way (e.g. Google and other search engines, browsers, Slack, Visual Studio Code, Superhuman, etc.) so my muscle memory is very much trained at Return-means-search and I habitually (multiple times a day) get the new line rather than searching. Even beyond search, ChatGPT works this way where Shift+Return is reserved for “new line” and Return means “action”.
My feeling here is “make it as unsurprising” rather than “hey user develop some new muscle memory” :) I get that we are making it consistent across the Comms but I feel it’s inconsistent with the context of Search vs the context of Writing Communication.