🦒 How To Find Zshrc File

If your experience has been anything like mine, there is not a clear answer for you out there in the wild. However, if you read the Oh My Zsh docs carefully on github, very carefully. You will which stays the same with this solution as long it's set in your ~/.zshrc file and overwrites this assignment. Off-Topic but potentially useful While searching for the solution which fits the most I found out that you could have a different history files for VSCode only by adding also In this case, Oh My Zsh plugins are installed in the ~/.oh-my-zsh/plugins directory, so running the following command will return a list of your installed plugins: ls ~/.oh-my-zsh/plugins. To enable a plugin, just add its name (as shown from the above command) in plugins= () in your ~/.zshrc file. From the Oh My Zsh wiki: If you had the following (using fake plugin names) in your .zshrc file: plugins=(first-plugin another-plugin third-doohickey favorite-thingy) While the following directories existed (notice the incorrect dash vs underline): Check if any copy of the zshrc still exists. This didn't happen in my case, but if by chance there is a version of the .zshrc somewhere (notably if your code editor of choice autosaves files to a specific location), there is a small possibility of it still existing somewhere. To find it, run this: sudo find . -name ".zshrc" 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. 1. Activate Plugins Using the Zsh Configuration File. To see which plugins are available, open the Oh My Zsh Plugins page on GitHub. Here you will find a list of all the plugins that you can use in Oh My Zsh. After you have decided which plugin you want to use, open the Zsh configuration file using nano: nano ~/.zshrc @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. Scroll down to find the guid for the WSL; Copy that guid and scroll back up; Paste the WSL guid inside the defaultProfile setting; Now every time we run the terminal, the default profile will be the WSL one. Install and setup zsh and Oh-My-Zsh. The next thing we need to do is installing the zsh shell in our WSL. Open the Windows Terminal (if Actually, there is no default .zshrc file, but if you need to edit is as a simple notepad, do these: Goto /Users/ Folder via Finder App. Click Shift + Command + . 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. You can add them to your ~/.zshrc file, then reload your terminal (using source ~/.zshrc) for them to take effect. The syntax for declaring a (simple) alias is as follows: alias [alias-name ALLqF.

how to find zshrc file