Suggestion for dealing with keybind conflicts in vscode terminal?

[digitalsignalperson]

For example C-j in multiline is the default keybind in vscode to open/close the terminal panel.

Do people here change all the keybinds in vscode, or in ble.sh, or is there some other trick maybe? Aside from not using vscode.

[akinomyoga]

Do people here

The community hasn't grown up, so there are no people here.

When there are conflicts in the keybindings with the terminal, usually, the keybindings of either need to be changed.

I'm not familiar with VS Code Terminal, but after a quick search, the config terminal.integrated.commandsToSkipShell might be related. You can press C-, to open Settings and type terminal.integrated.commandsToSkipShell in the textbox to find the configuration. The description of the config says

A set of command IDs whose keybindings will not be sent to the shell but instead always be handled by VS Code. This allows keybindings that would normally be consumed by the shell to act instead the same as when the terminal is not focused, for example Ctrl+P to launch Quick Open.

Many commands are skipped by default. To override a default and pass that command's keybinding to the shell instead, add the command prefixed with the - character. For example add -workbench.action.quickOpen to allow Ctrl+P to reach the shell.

The following list of default skipped commands is truncated when viewed in Settings Editor. To see the full list, open the default settings JSON and search for the first command from the list below.

Default Skipped Commands:

[...very long list...]

You need to pick up the command name that is bound to C-j, and add an item "-<command name>" to revert the skipping.

[akinomyoga]

I found a simpler config: terminal.integrated.sendKeybindingsToShell.

You can find it by pressing C-, (Control + comma) to open Settings and by typing terminal.integrated.sendKeybindingsToShell and just turn on the check box. This made it possible to input C-j in VS Code Terminal in my environment.

[akinomyoga]

The description of terminal.integrated.sendKeybindingsToShell says

Dispatches most keybindings to the terminal instead of the workbench, overriding terminal.integrated.commandsToSkipShell, which can be used alternatively for fine tuning.

so if you need fine-tuning on which should be sent to the terminal and which shouldn't, you'll need to configure terminal.integrated.commandsToSkipShell mentioned in another reply.

[digitalsignalperson]

Thanks for those tips, that seems like a pretty complete set of possibilities. I'm used to C-j for opening/closing the vscode integrated terminal panel, so maybe I'll pick one to re-bind. Otherwise I'd have to think if set/unset that sendKeybindingsToShell on demand can be of any use. For keybindings, I like the multi-line editing experience in the python qtconsole, so maybe I'll try copying those keybindings (Ctrl+Enter = new line, Shift+Enter = execute, or Enter = execute if on the last line)

Btw I'm also happy to be checking this project out. I heard ble.sh is the largest shell program in the world! I was getting frustrated with fish as my main shell when all the scripting I'm doing is with bash. This is really cool to have a bash environment with practically all the nice bits from fish.

[akinomyoga]

I'll try copying those keybindings (Ctrl+Enter = new line, Shift+Enter = execute, or Enter = execute if on the last line)

I actually tried to enable those key combinations, Ctrl+Enter and Shift+Enter, for VS Code Terminal using workbench.action.terminal.sendSequence in keybindings.json, but somehow the VS Code Terminal ignores the settings and always sends just Enter. (Edit: It turned out that to use ctrl+enter and shift+enter, I need to turn off terminal.integrated.sendKeybindingsToShell.) Here's my settings in keybindings.json.

    { "key": "shift+enter", "command": "workbench.action.terminal.sendSequence", "args": { "text": "\u001b[27;2;13~" }, "when": "terminalFocus" },
    { "key": "ctrl+enter", "command": "workbench.action.terminal.sendSequence", "args": { "text": "\u001b[27;5;13~" }, "when": "terminalFocus" },
    { "key": "ctrl+shift+enter", "command": "workbench.action.terminal.sendSequence", "args": { "text": "\u001b[27;6;13~" }, "when": "terminalFocus" },

I'm not sure if it is possible to bind those key combinations for VS Code Terminal.

I heard ble.sh is the largest shell program in the world!

Yeah, that's the estimate by Andy Chu, the author of the Oil shell. There is still some auto-generated large scripts like ./configure for GNU coreutils, but for the hand-written shell scripts available publicly, maybe this would be the largest one. At least, I'm not aware of other scripts that has the same scale. However, I feel there might be a larger script privately used in a company. Anyway, thank you for trying it!

[akinomyoga]

I sorted out how to bind C-RET, etc. in the VSCode Terminal. I summarized it in the wiki page: Visual Studio Code Terminal - Manual A2.

[digitalsignalperson]

Thanks for the thorough wiki guide.

A question on the multiline bindings themselves,

-- MULTILINE -- (RET or C-m: insert a newline, C-j: run)

Is it possible to change those RET/C-m/C-j bindings?

e.g. I tried changing any ble-bind -f 'C-j' instances I could find but there was no effect.