Closed
Description
openedon Jul 19, 2022
This issue tracks cleaning up the shell integration sequences, documenting and encouraging third parties to use the sequences.
Possible users:
- Windows Terminal (cc @zadjii-msft)
- Powershell vscode ext (cc @andschwa, @SeeminglyScience)
- Julia vscode ext (cc @pfitzseb)
- powerlevel10k (cc @romkatv)
- Python vscode ext
- Third party shell integration scripts (eg. if the fish community wanted to create a script Support fish shell integration automatic injection #139400)
Some things to look into:
- The continuation (
F
,G
) and right prompt (H
,I
) sequences are not thoroughly tested, we should investigate whether we need these at all considering. - Review and document all known properties (
P
)?- Should we support one of the common cwd properties instead of roll our own? Hostname and different sequences for different operating systems were some of the complications here.
- How should cwds be treated in ssh where VS Code's shell integration is installed?
- The
Task
should should be more generic
- Improve command line (
E
) serialization of special characters - Should
633 A
-D
be removed in favor of133 A
-D
? p10k works in a degraded state when sending these, if it also sentE
(andP
?) would it be fully functional?
The current sequences are lightly documented in code here:
vscode/src/vs/platform/terminal/common/xterm/shellIntegrationAddon.ts
Lines 54 to 118 in f8aeb20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment