I've really been considering learning zsh. The main reason I haven't bit the bullet is because bash is everywhere. I don't want to become as fluent in zsh as I am in bash, only to feel crippled when I inevitably have to work without zsh.
So, for those that frequently shift between zsh and bash (or ash, dash, etc.), what is the experience like?
Since both bash and zsh are 'sh' derived shells, it's not a huge context flip. It's analogous to flipping between your highly tuned (vim|emacs) config, vs logging into a new AWS image with the default version's config: You still know how to get around, but all the bells and whistles are turned off.
I haven't had much trouble with flipping back and forth. At my company the sys admins won't install zsh on live boxes, but are willing to put it on dev boxes. So I end up dropping to bash whenever I'm on a live box.
I tried zsh when it came out, but gave up (too rough then). Recently, I made the move and I am quite happy. This workshop will hopefully help me get deeper into it. (I used the oh-my-zsh linked above).
I love how you can type "vim " and press up-arrow, to get previous commands with vim. In bash, after typing "vim " i would have to erase the line, do "C-r" and then type vim again.
Looking through the feature list, is there anything that stands out as something bash cannot do, that is useful and not superfluous(like checking the mailbox?!)?
13 comments
[ 3.2 ms ] story [ 38.7 ms ] threadSo, for those that frequently shift between zsh and bash (or ash, dash, etc.), what is the experience like?
There's also a Steve Losh blogpost about that's quite cool http://stevelosh.com/blog/2010/02/my-extravagant-zsh-prompt/
I love how you can type "vim " and press up-arrow, to get previous commands with vim. In bash, after typing "vim " i would have to erase the line, do "C-r" and then type vim again.
http://www.acm.uiuc.edu/workshops/zsh/why.html
1999, my senior year at UIUC. I remember sitting in this workshop, and I still use zsh today. Good times, great ACM student chapter.