There are several other threads asking to please help address the issue of not being able to navigate text via Ctrl+N in the Composer/Chat windows, because Ctrl+N automatically creates a new chat instead of Cursor-Down.
Changing the Keyboard Shortcuts does not work. Changing the keyboard shortcuts .json file does not work.
This seems like a very simple bug to fix. Can we please address it? Tons of prompts are getting lost because we are used to standard keybindings.
Thank you,
Shaun
Exactly! It’s so annoying. Do the guys on the Cursor team not use the macOS version? How can this still be a thing?
Hey, a lot of us use Mac but I guess not many use the CTRL+N shortcut to move up and down!
I’ve added this to our feedback tracker, so we can hopefully add a solution to this in a future update.
Thank you so much @danperks That would be tremendously helpful.
I irrecoverably lose several prompts per day because I forget about this.
Even an “Undo” functionality for the text would be useful. Or something that saves the history for non-submitted prompts.
Thanks for taking account !
It is really annoying and I suppose the number of developers who use this shortcut may be underrated 