🌬️ How To Find Zshrc File

Check your .zshrc (or the file dates) to see which one you're currently using. How zsh opens the file, and therefore what happens if it is a symbolic link, depends on several options. If one of the options append_history (set by default), inc_append_history or share_history is set, or when the history is saved explicitly with fc -AI , zsh 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. 4 points. zshrc file, .zsenv file. Config file. I am learning how to write and run scripts from Terminal window. I understand that it is related to content of files where i specify location of my scripts. directory, my own functions and granting proper permissions to my scripts. These files are: Most of the time you don’t want to maintain two separate config files for login and non-login shells — when you set a PATH, you want it to apply to both. You can fix this by sourcing .bashrc from your .bash_profile file, then putting PATH and common settings in .bashrc. To do this, add the following lines to .bash_profile: That might indeed be worthy of a second question. But you can also add more debug output than just echo $(date) - you could also add pstree -pal to the log. You could also perhaps move the relevant scripting from .zshrc to .zsh_profile (presuming that's a thing) or modify your scripting to set an environment variable, and only run if it's not already set. Here is a basic list for the system bashrc: /etc/bashrc (Redhat, Fedora, etc) /etc/bash.bashrc (Debian, Ubuntu, Linux Mint, Backtrack, Kali etc) /etc/bash.bashrc.local (Suse, OpenSuse, etc) Then there is the private single-user bashrc, which, for the most part is stored in ~/.bashrc for basically every distro Add a comment. -1. Here is an interesting hack that doesn't require you to use sym-links. In your .xsession, (or .*wmrc) have the following: xterm -e 'zsh -c ". ~/.dotfiles/.zshrc; zsh"'. instead of just: xterm. Make sure to put the -e at the end after all of your other xterm options. ZSH startup scripts are ~/.zshrc and ~/.zshenv. I usually put global environment variables like PATH in ~/.zshenv. It is possible that some other instructions in your startup scripts are overwriting/replacing your PATH. To see what is happening during zsh startup, run: zsh -x 2>&1

how to find zshrc file