when typing a message in composer on macOS, ctrl+n should go down a line instead of creating a new composer (reserved for cmd+N)
2 Likes
Hey, try pressing Shift + Enter instead to start a new line.
not for new lines, it’s about navigating through a complex multiline prompt for composer
1 Like
This behavior is ruining my experience with Cursor. Using Ctrl+N to move the cursor to the next line or select the next item in a suggestion has become instinctive for me, as it is the canonical Unix shortcut in a text area. In Composer, I always need to write a long prompt for my tasks, and even though I have told myself many times not to use Ctrl+N in Composer, I still end up doing it several times a day. Each time, my already written prompts are cleared due to creating a new Composer. I have even removed the keybinding for the “New Composer” action and searched for Ctrl+N actions to ensure none of them create a new Composer, but none of these solutions have worked. Please fix this for the sake of being a programmer’s tool.
3 Likes
Echoing reorx - for me, even after over a year of using Cursor I still find myself drafting prompts in other applications to avoid this problem.
Presumably this is a relatively low risk change?
2 Likes
Chiming in here. Ctrl-N and Ctrl-P should go to the next and previous quick search, results, definitely. Instead, it clears stuff from the input.
