3 ms·
I understand the need to build tools and I would have used this too, if it was a simple enough bash script with a bunch of aliases and some sweet bash_completio
by devnonymous 12y ago
I understand the need to build tools and I would have used this too, if it was a simple enough bash script with a bunch of aliases and some sweet bash_completion love.
However, I don't see why I should replace this ...
$ mv ~/.vimrc{,~}
$ mv ~/.vim{,~}
$ git clone --recursive git@github.com:lonetwin/lonetvim.git ~/.vim
$ ln -sf ~/.vim/dot_vimrc ~/.vimrc
# -- work --
^profiles^ could just as well be branches ...although, I don't think I have use
for them.
- priomsrb 12y agoOP here. VimSwitch does something similar to what your script does. It just makes it a bit more convenient. Here is a use case that I plan to use it for: # log into production server $ vimswitch priomsrb/vimrc # -- work -- $ vimswitch default $ logout This puts vim back into it's original state for the next person who logs in. In future versions I hope to make the above workflow even simpler: # log in to production server $ vimswitch --launch priomsrb/vimrc # log out The --launch command will launch vim with your settings without altering the home directory.
- zimbatm 12y agoIf that's the symptom then I would recommend using different SSH users instead of everyone sharing the same account. It allows each user to use it's own config and also makes `who` more useful.
- priomsrb 12y agoThat's a good point. My example comes from experiences where the only available users are 'admin' or 'logs'.
- xyzzy_plugh 12y agoI tend to agree, I don't understand how this problem warrants literally thousands of lines of code, when a few lines of bash will do...