VSCode-like Shell Integration #13445
Comments
heartacker
added
the
Issue-Feature
ghost
added
Needs-Tag-Fix
|
I'm tempted to leave this open as a megathread, linking the other things we have planned across the repo: |
|
Also #6632 |
|
I actually intentionally omitted #6632 from that list. #6632 is more about an autocomplete menu who's contents are populated based on the words that are currently in the buffer. The rest of these VsCode features are more driven by specific metadata in the prompt to indicate things like the CWD, the command that's run, where the prompt is, etc. One is something exclusively powered by the terminal, the other is powered by a cooperating shell/commandline program. It's definitely related, but not necessarily "shell integration" 😄 |
zadjii-msft
added
Area-User Interface
|
Kitty also has shell integration for various shells. But seems to really intermingle with shells in a way that Iterm2 does not. Wezterm is also looking to implement Iterm2 shell integration from what I saw but nothing has come of that yet other than implementing OSC 7 quite awhile ago. |
zadjii-msft
removed
the
Needs-Triage
|
iTerm also has a really cool password manager that integrates with 1Password for example |
|
VS Code has now enabled its shell integration by default in 1.70. |
|
I know it's trivial but I really like the command decoration circles too... |
|
And copy entire command's output! |
Adds a "Select command" and a "Select output" entry to the right-click context menu when the user has shell integration enabled. This lets the user quickly right-click on a command and select the entire commandline or all of its output. This was a "I'm waiting for reviews" sorta idea. Seemed like a reasonable combination of features. Related to #13445, #11000. Tested manually. --------- Co-authored-by: Dustin L. Howett <[email protected]>
_targets #14943_ When this is true, this will re-use the existing commandline to pre-filter the results. This is especially helpful for completing a suggestion based on the text that's already been typed. Like with command history, this requires that shell integration is enabled before it will work.## Summary of the Pull Request ## References and Relevant Issues See also #13445 As spec'd in #14864 ## Validation Steps Performed Tested manually
_targets #15027_
Adds a new suggestion source, `tasks`, that allows a user to open the
Suggestions UI with `sendInput` commands saved in their settings.
`source` becomes a flag setting, so it can be combined like so:
```json
{
"keys": "ctrl+shift+h", "command": { "action": "suggestions", "source": "commandHistory", "useCommandline":true },
},
{
"keys": "ctrl+shift+y", "command": { "action": "suggestions", "source": "tasks", "useCommandline":false },
},
{
"keys": "ctrl+shift+b", "command": { "action": "suggestions", "source": ["all"], "useCommandline":true },
},
```
If a nested command has `sendInput` commands underneath it, this will
build a tree of commands that only include `sendInput`s as leaves (but
leave the rest of the nesting structure intact).
## References and Relevant Issues
Closes #1595
See also #13445
As spec'd in #14864
## Validation Steps Performed
Tested manually
Description of the new feature/enhancement
https://github.com/microsoft/vscode-docs/blob/vnext/release-notes/v1_69.md#shell-integration
Maintainer note: I'm hijacking this issue body, for issue tracking purposes
Main elements of shell integration
Tasks
sendInputshould be previewable #12861Related, indirectly
References
The text was updated successfully, but these errors were encountered: