Skip to content

[vscode] TerminalState#shell property added #15433

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Tracked by #15434
rschnekenbu opened this issue Apr 9, 2025 · 0 comments · May be fixed by #15514
Open
Tracked by #15434

[vscode] TerminalState#shell property added #15433

rschnekenbu opened this issue Apr 9, 2025 · 0 comments · May be fixed by #15514
Assignees
Labels
vscode issues related to VSCode compatibility

Comments

@rschnekenbu
Copy link
Contributor

A new property has been added to TerminalState

 /**
 * The detected shell type of the {@link Terminal}. This will be `undefined` when there is
 * not a clear signal as to what the shell is, or the shell is not supported yet. This
 * value should change to the shell type of a sub-shell when launched (for example, running
 * `bash` inside `zsh`).
 *
 * Note that the possible values are currently defined as any of the following:
 * 'bash', 'cmd', 'csh', 'fish', 'gitbash', 'julia', 'ksh', 'node', 'nu', 'pwsh', 'python',
 * 'sh', 'wsl', 'zsh'.
 */
readonly shell: string | undefined;
@rschnekenbu rschnekenbu added the vscode issues related to VSCode compatibility label Apr 9, 2025
@rschnekenbu rschnekenbu self-assigned this Apr 9, 2025
rschnekenbu added a commit that referenced this issue Apr 24, 2025
fixes #15433

Contributed on behalf of STMicroelectronics

Signed-off-by: Remi Schnekenburger <rschnekenburger@eclipsesource.com>
@rschnekenbu rschnekenbu linked a pull request Apr 24, 2025 that will close this issue
2 tasks
rschnekenbu added a commit that referenced this issue Apr 24, 2025
fixes #15433

Contributed on behalf of STMicroelectronics

Signed-off-by: Remi Schnekenburger <rschnekenburger@eclipsesource.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
vscode issues related to VSCode compatibility
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant