Vim and this blog
I'm a writer. I use vim for the bulk of my writing.
I've used vim and vi for more than fifteen years.
This blog documents vim from a writer's viewpoint.
Writers who grok vim can get more work done in less time than with a word processor.
Most of writing is editing. Vim cuts down on editing time.
My aim is to take anyone interested in vim to the point of self-sufficiency.
It's easy to go down the rabbit hole with a complex piece of software like vim.
That's not necessary!
Nearly all the benefit of vim comes from plucking the low-hanging fruit.
If you're a writer, don't learn emacs instead of vim.
Emacs has killer features that programmers need, but is clunky with text.
My teaching philosophy is, "Monkey see, monkey do."
Don't just read the blog. Follow along with vim! Things will start to click.
Every blog post is based around an exercise.
When I learned vim, I read technical documentation.
I learned a new key and thought, "Great. Now that I know that, what do I do?"
Nothing made sense out of context!
In addition to key definitions, writers need to see vim in action.
That's why this blog uses vim commands on real files, as a writer might.
If you follow the blog posts, you'll have success.
You'll understand things I don't explain well or don't explain at all.
I'm introducing everything at once, in a circular way.
The other approach would be linear, to exhaust topics one by one.
If you prefer the linear approach, it's out there! Lots of documentation exists already.
I will also work on a linear reference section, together with my blog posts.
I hope this blog is helpful to writers who want to harness the power of vim.