-
Notifications
You must be signed in to change notification settings - Fork 34
Handle all shells’ de/activation #137
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
Conversation
|
Thanks for the PR! Love the new shell command handling. |
|
Thanks for doing this @flying-sheep The list on https://github.com/microsoft/vscode/blob/e8346324cfb8b5d680ad657bb67153eb838aebc5/src/vscode-dts/vscode.proposed.terminalShellType.d.ts are subject to change, so feel free to let me know if anyone thinks more shell types could be added to make the workload easier on the extension side. As we want to make sure to cover extensive list of shell types for their specific activation. |
Fixes #138 This adds shell activation for - gitbash - wsl - ksh - tcshell - xonsh - nushell and fixes shell activation for C shell. it also makes sure that it’s impossible to add a terminal to the enum without also adding shell activation/deactivation commands by using a `Record` type that needs to be exhaustive.
Fixes #138
This adds shell activation for
and fixes shell activation for C shell.
it also makes sure that it’s impossible to add a terminal to the enum without also adding shell activation/deactivation commands by using a
Recordtype that needs to be exhaustive.