41–50 of 131 posts
I wonder, what is the preferred way to install configuration files such as .vimrc, .bashrc etc. across all the machines a user logs into?
It's been a while since I started using vim. I can see some similarities. Though, I didn't really do much configuration in the early days. Currently, I have pretty much no configs when it comes to key maps or some custom or shortcuts. I only add plugins for code completion and highlighting. Nothing else.
It's been a while since I started using vim. I can see some similarities. Though, I didn't really do much configuration in the early days. Currently, I have pretty much no configs when it comes to key maps or some custom or shortcuts. I only add plugins for code completion and highlighting. Nothing else.
The added benefit of this is portability, as in your weird shortcuts aren’t burnt into muscle memory, so you can easily use Vim on any computer.
I've noticed similar pattern with other tools, e.g. git. I've seen coworkers add all kinds off aliases to simplify git commands, and I'm very much against it since I prefer portability.
For me Vim productivity gains have more to do with never leaving the shell. Desktop environments are maddeningly rife with distractions
Same. My normal set up is having a shell window with 4 tabs: 1. Text editing 2. Command Line 3. Program logs 4. Code console Flipping through them is a breeze, and I never have to leave Terminal. The displays are always simple, straight forward, and focused. No distractions. I'm able to just get in the zone with the code and forget anything else exists.
Then you can, for instance, make your development machine a dedicated cloud server, like digital Ocean etc.
This is what I do and it's very nice to be able to use any hardware I want, including cheap underpowered stuff, since it's just a window to my real machine.
The only map that I would say is an absolute improvement over the default is map ; : Using : is a waste of a keystroke (ie. shift) in an editor that I chose specifically to reduce chorded key combos.
The only map that I would say is an absolute improvement over the default is map ; : Using : is a waste of a keystroke (ie. shift) in an editor that I chose specifically to reduce chorded key combos.
I used to map like this, but then I found ; is to repeat f{char}. How do you repeat f command? Map it to another key? Use / instead?
Earlier quoted context omitted.
The added benefit of this is portability, as in your weird shortcuts aren’t burnt into muscle memory, so you can easily use Vim on any computer.
Exactly! I like being able to log in to any server and use vim/vi without any issues. I've noticed similar pattern with other tools, e.g. git. I've seen coworkers add all kinds off aliases to simplify git commands, and I'm very much against it since I prefer portability.
Admittedly, it does get annoying when I'm sudo-ed to another user, but it's vanishingly rare for me that I am both sudo-ed to another user, and doing enough editing that I really want those configs. Usually a sudo-ed vi for me is just updating a couple lines in a config, I don't need a full config for that
Earlier quoted context omitted.
The added benefit of this is portability, as in your weird shortcuts aren’t burnt into muscle memory, so you can easily use Vim on any computer.
Exactly! I like being able to log in to any server and use vim/vi without any issues. I've noticed similar pattern with other tools, e.g. git. I've seen coworkers add all kinds off aliases to simplify git commands, and I'm very much against it since I prefer portability.