When you’ve finished browsing the available plugins and found the one you want to use, add its name to the plugin() function in the /.zshrc file to activate it. For example, to activate the python plugin, simply add the following line to the ~/.zshrc file. plugins=(python pip) After changing the theme, use Ctrl-O to save and Ctrl-X to exit. Find the '.zshrc' file: Open Terminal. Type open ~ to access your home directory. Press Cmd + Shift + . to show the hidden files in Finder. Locate the .zshrc. Map .bash_profile to .zshrc file, map .zshrc file to the ~/bin/dotfile/zshrc file, zshrc file just load 3 files which is environment, alias, config. ( Those 3 files are the logic separation of the .zshrc file ) That is my setup. It is currently working the way it should. I could use alias which I set in alias file, etc. I never put real content on the ~/.bashrc or ~/.bash_profile files, instead those files are just symlinks to the real configuration files kept in a subdirectory in my home folder, for example ~/dotfiles/bashrc and ~/dotfiles/bash_profile. I keep the ~/dotfiles folder under source control using Git, and hosted at GitHub.com Fantastic, thank you! I removed the manual compinit from my ~/.zshrc (what I gather from your answer is that OMZ runs its own compinit and thus it's unnecessary in my ~/.zshrc), and ran chmod g-w,o-w on the two directories returned by compaudit, now the warning is gone. . After you make the changes, press Ctrl+O and then Enter to save the file. Press Ctrl+X to exit nano afterwards. Now, whenever you open the Ubuntu shortcut (or other Linux distribution shortcut) on Windows, it starts up with the Zsh shell. To reverse your change, edit the .bashrc file again and delete the section you added. I just installed Kali in a vm and I don't need to source ~/.zshrc at all to make the aliases work after I open a new terminal window. If you still want to use zsh you could just create a file in /etc/profile.d that sources your zshrc, something like this. Code: cat /etc/profile.d/szshrc.sh source ~/.zshrc. When you start Zsh for the first time, it will create a default configuration file at `~/.zshrc`. This file contains settings and options that control how Zsh behaves. You can edit this file to customize your Zsh environment. Some common options to consider include: ZSH_THEME: sets the appearance of the prompt. You can find a list of available @TheWhiteFang That the shell is using another set of files from bash should get you over the first hurdle at least. The zsh has a fair number of more features compared to bash, but I won't be trying to summarize them here. See the zsh manual and the manuals that this refers you to. Apart from that, search this site if you run into more issues. if you happen to need to share your .zshrc across different OS, you can do some OS check in your zshrc file to see if it is macOS or linux/wsl:

how to find zshrc file