Ctrl+n in composer panel

Discussion
1

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)

9 Likes
2

Hey, try pressing Shift + Enter instead to start a new line.

3

not for new lines, it’s about navigating through a complex multiline prompt for composer

1 Like
4

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.

12 Likes
5

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?

3 Likes
6

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.

CleanShot 2024-12-11 at 14.36.33

5 Likes
7

Echoing this. This is the default readline / macos / emacs way to move around and for some of us, this is second nature to use these keybindings. I’m insanely frustrated with this behavior and it breaks flow.

3 Likes
8

I’ve tried multiple configurations to fix Ctrl + N, including:

{
    "key": "ctrl+n",
    "command": "cursorDown",
    "when": "textInputFocus && (focusedView == 'workbench.panel.composerViewPane2.view' || focusedView == 'workbench.panel.aichat.view')"
},
{
    "key": "ctrl+n",
    "command": "cursorDown",
    "when": "inChatInput || composerInput || chatInputFocus"
},
{
    "key": "ctrl+n",
    "command": "cursorDown",
    "when": "inputFocus && !editorTextFocus && !suggestWidgetVisible && !inQuickOpen"
}

Despite this, Ctrl + N still stubbornly creates a new composer. I’ve already reported this as a bug:
MacOS: Fix Ctrl+N for CursorDown

3 Likes
9

Just posted a temporary solution that requires Karabiner Elements on MacOS here:

10

This is bug !

4 Likes
11

This behavior is very frustrating. Please address this.

1 Like
12

Just FYI, ctrl-z or cmd-z will bring back if you happen to accidentally click Ctrl+n

Ryan Lambert

Follow me on LinkedIn or Twitter

1 Like
13

confirmed fixed in

0.48.8
7801â– â– â– 6824585b7f2721900066bc87c4a09b740
arm64

keyboard shortcut:

    {
        "key": "cmd+n",
        "command": "-composer.createNew",
        "when": "composerFocused || focusedView =~ /^workbench.panel.aichat.view/"
    },
14

confirmed fixed in

0.48.8
7801â– â– â– 6824585b7f2721900066bc87c4a09b740
arm64

keyboard shortcut:

    {
        "key": "cmd+n",
        "command": "-composer.createNew",
        "when": "composerFocused || focusedView =~ /^workbench.panel.aichat.view/"
    },
2 Likes