> At least, command line interfaces have the merit of often being documented (that feature is documented line 91 of my offline `man git commit`)
By default, pressing "Enter" in VS Code adds a new line. I don't think that needs to be documented. And the input box for the commit message says as its placeholder "Cmd+Enter to commit on [branch]", which is a whole lot more discoverable than going to line 91 of some man page. Plus, every keybinding can be searched and configured using the built in keybinding editor.
>> but using Shift+Enter to get a newline is fairly common and easy to try and guess.
> How on Earth is that intuitive? User interfaces (coomand line, GUI, web, voice) typically rely on common patterns
You'll find many "Enter to submit" boxes across the technosphere have some way of adding a new line, typically shiftenter, ctrlenter, etc. So this is a common pattern.
By default, pressing "Enter" in VS Code adds a new line. I don't think that needs to be documented. And the input box for the commit message says as its placeholder "Cmd+Enter to commit on [branch]", which is a whole lot more discoverable than going to line 91 of some man page. Plus, every keybinding can be searched and configured using the built in keybinding editor.
>> but using Shift+Enter to get a newline is fairly common and easy to try and guess.
> How on Earth is that intuitive? User interfaces (coomand line, GUI, web, voice) typically rely on common patterns
You'll find many "Enter to submit" boxes across the technosphere have some way of adding a new line, typically shiftenter, ctrlenter, etc. So this is a common pattern.