Question:
Any idea why terminal.integrated.allowChords is true under Workspace and false under User settings by default?
Context:
I am trying to find workaround for a bug that is seen in recent versions of Cursor. When integrated terminal is in editor area, and in focus, all keybindings go for a toss and gets eaten by the terminal. For instance, Ctrl + K is sent to terminal, Ctrl + Tab does not move focus across open tabs and instead sent to terminal. However, if I run “Developer: Reload Window” when integrated terminal tab (in editor area) is in focus, all keybindings gets fixed and work as expected. Although this “Developer: Reload Window” is a good workaround, I am trying to see if any combination of the following can be set to make things work:
terminal.integrated.commandsToSkipShell
terminal.integrated.allowChords
terminal.integrated.sendKeybindingsToShell
So, back to the question: Any idea why Allow Chords has different defaults? Or even better question is, any idea how to fix the actual problem?