Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

When you have access to a lot of machines run by different organizations but not administration privileges on most of them, it's a hassle.


So put your zsh config in a git repo, clone it wherever you need it and symlink to the repo?


Uh huh. Now I have to install git on all those computers as well as make sure there's a recent-enough copy of zsh. Much less work that way.

Or I can just use the bash that's already there.


Your concern about git however is unrelated to shell choice. I customize bash quite a bit (my own completions, etc.) and maintain dotfiles in a git repository. I have a post-receive hook that tars up my dotfiles and puts them at a public location on my http server that only I know about so that I can easily get them when I'm on a machine without git. I'm not going to do that for every machine, but if I'm stuck debugging something on some odd machine, at the very last I want my vim settings around.


It makes more sense for vim than zsh though. What color your prompt is has a lot less bearing on your productivity than your editor configuration. (Though I don't do much of that either).


I am of the same practice as fusiongyro. I also expand on that and have a very simple configuration for Vim. Once you go beyond a handful of machines, you never know what to expect on the system. "Lowest common denominator" wins out for me almost everytime.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: