The configuration file for zsh is called .zshrc and lives in your home folder (~/.zshrc). locate that file and open it. open ~/.zshrc Modify your Plugins 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. There is an alternate and easy way instead of manually setting up each configuration. This is the way I prefer normally. Instead of choosing the option "1" and going to the main menu to set each setting, we can choose option "2" which will populate the .zshrc file with default parameters. We can change the parameters directly in the .zshrc file. 18. I recently switched from bash to zsh. In bash, I used the dot alias . for the source command, e.g. . .bashrc. It worked with . .bashrc, . ~/.bashrc, . ./.bashrc. However with zsh, the dot alias does not work in the same way. It only works with a path to the file. But not if I use a file without path: It is a hidden file and simple ls command won’t show the file. To view hidden files, you can run the below command: $ ls-a. You can see the .bashrc command in the first column. The contents of .bashrc can be changed to define functions, command aliases, and customize the bash..bashrc file has a lot of comments that makes it easy to understand. source ~/.bashrc. fi. Most mac users running bash will put everything into .bash_profile. For mac users running ZSH, the ~/.zshrc file is evaluated every time a shell is launched. The ~/.zprofile file is only evaluated when you login to your mac user account. The .zprofile should be used for any commands and variables which need to be set once Zsh has a built-in feature allowing it to find a file in the current or any other subdirectory. For instance, assume you have two files called foo.txt. One is located in your current directory, and the other is in a subdirectory called foo. In a Bash shell, you can list the file in the current directory with: $ ls foo.txt This allows project-specific environment variables without cluttering the ~/.profile file. zsh-autoenv - a feature-rich mixture of autoenv and smartcd: enter/leave events, nesting, stashing (Zsh-only). It's possible to do this - here's a screencast, using the Grml ZSH configuration. The chpwd_profiles () function in the Grml ZSH configuration. Bash shell uses a few startup files to set up the environment. These files determine certain Bash shell configurations for the shell itself and system users. In this tutorial, we’ll learn about a few startup files such as .bashrc, .bash-profile, and .profile and their differences. 2. Interactive Shells and Non-Interactive Shells The thing I made back in 2013 was an "extended" history file of my own devising where the pwd of the command in question is always logged. It could be optimized to a log for only when it changes, as well, since I track the tty/pty in that history too. But capturing all the metadata all the time has been working out very well for me. – Ijxy.