To be able to specify the ACTIVE TERMINAL for bang command processing
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing bang command processing and reviewing how the vim.shell setting selects a shell. Clarify how the active VS Code terminal should be selected, including remote-container use, and consider the issue complete when bang commands run through that terminal rather than the host OS shell.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100