I see the terminal settings for “Send Keybindings To Shell” and “Allow Chords” and “Commands To Skip Shell”
There seems to be no combination that allows me to have, for example, “ctrl-q k” set to a command and then “ctrl-q l” still go to the shell.
If I set “send keybindings to shell” but then unset “allow chords” then none of the chord commands work, everything is sent to the terminal.
If I set “allow chords” then the chord command works, but the chorded keys that don’t have any commands just report “The key combination (…) is not a command”.
Trying to use “skip shell” to specify the command that I have bound to the “ctrl-q k” doesn’t actually skip the shell for the chorded command.
It doesn’t seem like any combination of the booleans, with or without the command in the “skip shell” list will allow me to use a chorded key in the terminal to run a command, but any other keys using that first part of the chord to go to the terminal.
It seems like the easiest thing would be to have a “chord passthrough” list where you could specify chorded keys that would go through to the terminal list regardless, and/or the opposite, allow all chords to go through except those on a list and/or those connected to commands.
Or, easiest of all, instead of giving me “The key combination (…) is not a command” - just send that key combination to the terminal!