4 ms·

I personally use no plugins [1]. Zero friction moving from host to host. Vim is a great text editor, not a great IDE. For anything more sophisticated I prefer j

by crehn 8y ago

I personally use no plugins [1]. Zero friction moving from host to host. Vim is a great text editor, not a great IDE. For anything more sophisticated I prefer just switching to something like VS Code (with Vim bindings of course). [1] https://github.com/hoffa/dotfiles/blob/master/.vimrc https://github.com/hoffa/dotfiles/blob/master/.vimrc

iforgotpassword 8y ago
Same. I had quite a lot some time in the past, but also made the "using vim on some foreign machine and being confused as hell" experience by trying to use hotkeys or commands that didn't exist. Also just keeping the config synched between my own hosts was more annoying than I anticipated. Not to mention resolving conflicts between different plugins, or random stuff breaking when updating anything. Nowadays I have a vimrc that just tweaks vanilla features the way I like, plus some highlighting for certain keywords regarding a C codebase I occasionally work on. The only plugin I use is a modified version of DetectIndent.
- JackCh 8y ago
  > "Same. I had quite a lot some time in the past, but also made the "using vim on some foreign machine and being confused as hell" experience by trying to use hotkeys or commands that didn't exist." I've found that setting a custom colorscheme in vim averts this problem completely. If I see my colorscheme, my muscle memory is primed for my config. If I see the default vim colorscheme, my muscle memory reverts to default vim. If somebody gave me a copy of otherwise vanilla vim to use that had my colorscheme, that would certainly throw me for a loop. But so far nobody has been that diabolical.
arnarbi 8y ago
During periods where I needed to regularly edit on other machines, I found it easy enough to adjust without giving up customization everywhere. Tbh, the only thing that gets in my way are the exact tab-related settings you also have.
sodapopcan 8y ago
I've never really understood this argument. Using vim locally with a bunch of plugins and then vanilla vim remotely is really the exact same thing as using any other editor locally and vanilla vim remotely.... especially if you are using vim bindings in said other editor! In any event, I just mitigate this problem by not overriding a bunch of standard behaviour. Also, none of the many plugins I use modify any standard behaviour in any serious way, they just help speed up certain actions when working in a large code base. There is very minimal context switch for me when editing a file remotely.
h1d 8y ago
It's really non constructive to think sticking to the painful default config of vim as a virtue. Why don't you just copy your vim config around? or if you're sharing users, ask to create your own user or just source your own config when you're using it.

by crehn 8y ago

iforgotpassword 8y ago

Same. I had quite a lot some time in the past, but also made the "using vim on some foreign machine and being confused as hell" experience by trying to use hotkeys or commands that didn't exist. Also just keeping the config synched between my own hosts was more annoying than I anticipated. Not to mention resolving conflicts between different plugins, or random stuff breaking when updating anything. Nowadays I have a vimrc that just tweaks vanilla features the way I like, plus some highlighting for certain keywords regarding a C codebase I occasionally work on. The only plugin I use is a modified version of DetectIndent.

JackCh 8y ago
> "Same. I had quite a lot some time in the past, but also made the "using vim on some foreign machine and being confused as hell" experience by trying to use hotkeys or commands that didn't exist." I've found that setting a custom colorscheme in vim averts this problem completely. If I see my colorscheme, my muscle memory is primed for my config. If I see the default vim colorscheme, my muscle memory reverts to default vim. If somebody gave me a copy of otherwise vanilla vim to use that had my colorscheme, that would certainly throw me for a loop. But so far nobody has been that diabolical.

arnarbi 8y ago

During periods where I needed to regularly edit on other machines, I found it easy enough to adjust without giving up customization everywhere. Tbh, the only thing that gets in my way are the exact tab-related settings you also have.

sodapopcan 8y ago

I've never really understood this argument. Using vim locally with a bunch of plugins and then vanilla vim remotely is really the exact same thing as using any other editor locally and vanilla vim remotely.... especially if you are using vim bindings in said other editor! In any event, I just mitigate this problem by not overriding a bunch of standard behaviour. Also, none of the many plugins I use modify any standard behaviour in any serious way, they just help speed up certain actions when working in a large code base. There is very minimal context switch for me when editing a file remotely.

h1d 8y ago

It's really non constructive to think sticking to the painful default config of vim as a virtue. Why don't you just copy your vim config around? or if you're sharing users, ask to create your own user or just source your own config when you're using it.