if [[ ! -f "$/.zsh/iterm2_shell_integration.zshĬopy this to your home directory on any Mac/Linux computer and it should just work. Set zsh as your default shell by running the following command in iTerm2, and then relaunch the terminal: chsh -s / bin /zsh You can verify the shell you're running with the echo command. We want to change that to Zsh so we can get all the fancy features Open iTerm Preferences, and in the Command. In case it's helpful, here's the ~/.zshrc snippet I ended up with that so far works perfectly on all my servers. Changing iTerm to Use Zsh It’s likely that iTerm is using the default shell, Bash. Which left me with zgenom, which to my delight, just worked. Even weirder it occasionally worked for no reason I could discern and gave different errors on each of my computers. Seemed to be something to do with its parallel execution using xargs or parallel. Zpm seemed good but again ran into weird bugs where it would work the first time I used it but would errors as soon as I opened a new shell. I really liked the look of miniplug but for some reason it would not work on one of my servers. Most hadn't been updated in over a year which left me with a few, very new projects (only a handful of commits) and miniplug, zpm, and zgenom as the most likely candidates. So I went spent a day going through every single plugin manager on the awesome zsh page. Most hadn't been updated in a long time, had many unanswered issues in their GitHub and had serious bugs when I tried to use them. I avoided larger frameworks like om-my-zsh and prezto as they seemed like overkill.įirst I tried the popular ones like zplug and antigen. I wanted a simple, lightweight zsh plugin manager which I could deploy to a new server by simply copying across my ~/.zshrc. In case this can save some one else some pain.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |