-
Notifications
You must be signed in to change notification settings - Fork 28.5k
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
Is it possible to configure Babun/ZSH for the integrated terminal on Windows? #24588
Comments
I went another route and installed Cygwin with ZSH and Oh My Zsh and configure VS Code like this: "terminal.integrated.shell.windows": "C:\\Cygwin\\bin\\zsh.exe",
"terminal.integrated.shellArgs.windows": [
"-lic",
"cd $OLDPWD; exec zsh"
] For now this is working nicely and it's probably a better a option than Babun which hasn't been updated in a while. Feel free to close this if no longer relevant... |
Updating my solution about... It works most of the time, but in some situations For instance, after running some commands (I noticed this by running |
Good to hear you got it working. This might be useful for you as well #14977 |
@Tyriar The solution on that issue didn't work for zsh instead of bash. The terminal opens and immediately closes. Anyway to debug this? |
@rfgamaral no way to debug currently, an immediate close typically means if you ran the command in an external terminal it would exit immediately as well. |
@Tyriar The following worked: "terminal.integrated.shell.windows": "C:\\Cygwin64\\bin\\bash.exe",
"terminal.integrated.shellArgs.windows": ["/bin/xhere", "/bin/zsh"] Just started |
Is it only me who didn't have do do much. I just did this:
and it works fine. Or is it due to recent updates? |
hey, i tried following to run bash in current open folder |
This is "working":
The only problem is that a new window is opened instead of the integrated terminal.
The command and arguments were taken from here.
Does anyone if it's possible to have the ZSH shell on the integrated terminal and on Windows?
The text was updated successfully, but these errors were encountered: