3 ms·
Yes, I already know vim- it's the only text editor I've used for the last eight years or so [1]. OK, I accept that some users will find vimtutor helpful, like
by YeGoblynQueenne 7y ago
Yes, I already know vim- it's the only text editor I've used for the last
eight years or so [1].
OK, I accept that some users will find vimtutor helpful, like you did. On the
other hand- I would never have learned to use vim if it meant I had to read 4
chapters before I could "survive" in it.
The way I learned vim was ... to not try to learn vim. This is much like the
article above describes it. Before vim I was using Notepad++. At some point, I
switched to vim and just did all the things I was doing in Notepad++, except I
did them using vim. That meant I only had to climb the smoothest learning
curve and my productivity never dropped from having to stop and search for
advanced stuff.
I was a bit annoyed originally by the Mikado of escape slashes in regexes, but
I got used to them reasonably quickly. Then at some point, when I needed to
do more advanced stuff that I'd never have considered doing with Notepad++ [2]
I looked that stuff up and learned how to do it, but only as and when I needed
it.
In the first year or so I was keeping a notes file with all the weird-syntax
commands that I needed with enough frequency that I wanted to keep handy, but
I couldn't bother to memorise. I still occasionally consult this file, e.g.
when I need to remember the syntax for look-ahead or look-behind regexes. It
turns out, you can go a _long_ way without really, really having to do a
lookahead.
I should say, I also tried a few vim plugins here and there, but mostly they
seemed to mess up my install, so I was turned off them for good. Pretty much
the only plugin I use nowadays is the excellent highlight script from the vim
wiki (https://vim.fandom.com/wiki/Highlight_multiple_words https://vim.fandom.com/wiki/Highlight_multiple_words). It's just perfect
for highlighting logs and, er, logs.
So while I appreciate that vimtutor can be useful to some users, it is by no
means the only, or the simplest, way to get to a point where you're feeling
comfortable using vim.
________________
[1] The one exception is the Emacs-based editor in the Swi-Prolog IDE, which
has a very good Prolog mode that actually compiles your code so it flags
errors and so on. It'd take a while to do this in vim, and there's no real
reason to. Although I miss being able to scroll with Ctrl+E/Y.
[2] Like using netrw to edit files directy on a remote server over a
powershell remote session, which got me some impressed comments by a senior
dev in my company, since everyone else just RDP'd to the server.