(See my 1-minute guide on How to add Git Bash to Windows Terminal) If you are as experimental as I am, please proceed ahead. TLDR: My advice is to stick with git bash for Windows as it is good enough for most cases. It turns out it is not as straightforward as I initially thought. Git Bash and Windows Subsystem for Linux (WSL).Īs macOS has replaced bash with zsh since Catalina, I decided to use zsh on Windows too, so that I have an unified experience across 2 different OS, with the same (or similar). Today, this argument holds little weight as there are plenty of ways Windows users can install a Unix shell like bash easily with However, since most servers worldwide are UNIX-based, it is common advice for developers to be familiar with Unix commands as much as possible.

I haven't seen any implication yet - I can still open jupyter notebooks and work on them, still, I wanted to solve this.One of the long-time arguments that favor macOS over Windows for developers is that macOS Terminal can run Unix commands while Windows Command Prompt cannot. zprofile files, as suggested by the error message.

profile file, and also included export PYENV_ROOT='$HOME/.pyenv' export PATH='$PYENV_ROOT/bin:$PATH' eval '$(pyenv init -path) in the end of both the. I have tried including the line eval '$(pyenv init -) in the end of my. You'll need to restart your user session for the changes to take effect.

To fix this message, add these lines to the '.profile' and '.zprofile' files Work correctly for non-interactive shells (for example, when run from a script). I set up Zsh (with OhMyZsh) within Windows Terminal app 8 months ago, and used it many times to develop Python apps.Ī couple months ago, I started getting the following error message when opening the terminal: # Load pyenv automatically by appendingįound pyenv, but it is badly configured (missing pyenv shims in $PATH).

Zsh windows terminal