My journey started when someone just dropped their .vimrc and I tried it out... So I'll do the same: https://tinyurl.com/y4d7rx6f
Typically I clone that into my home directory. Then I link everything to it with:
ln -s ~/vim/.vimrc ~/.vimrc && ln -s ~/vim ~/.vim
The .vimrc is kind of documented, but a quick version is:
tt: select a file name to open into a new buffer
fr and fR: go forward or backward through buffers (open files)
fd: close buffer
f2: if the needed commands are installed, reformat code
There's a few other remappings, but those are the most frequent ones I use, hence making it easier.
<tab> completion works everywhere as well. There's a bunch of other stuff for navigating windows and tabs, but once I realized that "buffers" are actually the "vim way" of file navigation, I stopped using those short cuts.
Edit: Yes I realize this is probably what the article is complaining about, but oh well.
Typically I clone that into my home directory. Then I link everything to it with:
ln -s ~/vim/.vimrc ~/.vimrc && ln -s ~/vim ~/.vim
The .vimrc is kind of documented, but a quick version is:
tt: select a file name to open into a new buffer
fr and fR: go forward or backward through buffers (open files)
fd: close buffer
f2: if the needed commands are installed, reformat code
There's a few other remappings, but those are the most frequent ones I use, hence making it easier.
<tab> completion works everywhere as well. There's a bunch of other stuff for navigating windows and tabs, but once I realized that "buffers" are actually the "vim way" of file navigation, I stopped using those short cuts.
Edit: Yes I realize this is probably what the article is complaining about, but oh well.