To be able to specify the ACTIVE TERMINAL for bang command processing

[MonkeyNinja]

To be able to specify the ACTIVE TERMINAL for bang command processing Currently is uses the host OS's "default" (sort of!) /bin/sh on unix and COMSPEC on windows...

I use docker remote containers for nearly all my projects, so I'm on windows, but developing in/on Linux( usually Debian) containers via the Remote Container VSCode functionality

I wanted to insert the results of a command, jq, ls, cat etc.... so:

v
:
<,>! ls

doesent work on my set up... but:

v
:
<,>! dir

injects the dir listing for the vscode install directory...

There is a setting vim.shell but this is a path to a shell on the host....

---

As a workaround I can run vim in the in terminal and load my file and then !dir or !jq etc, but this kind of counters using vscodevim.

[berthin]

Got same issue and request. My local vscode instance is running on a windows and the vscode server on a remote docker container. Bang commands use the shell from the local instead of the remote. I installed the Vim plugin on my local vscode and also only in the remote, and for both cases the results are the same. They use windows cmd.

[ScratZa]

same boat here - not sure if theres appetite to address this ?