A text editor is so much more than mere software.
I still remember the first time I came in contact with Vim; it was during my very first job. It was a part-time gig in a government office. A few months in, they decided to go 100% open-source. Out the window went Windows and in came Linux. At the time, I was doing PHP development, and I was sorry to have to let go of my dear Dreamweaver.
I decided that if I had to work on Linux, I would go all the way, no compromises for me. That meant getting used to working on the console and learning Vim.
When one of the resident Linux gurus walked by my seat and saw my screen, he said, “Are you using Vi? Maybe you’re not so useless after all.” (Funny story, I came across him on facebook the other day. Now that he’s bald, he doesn’t look intimidating at all).
Lately, I’ve been writing a lot. I found that armed with the right plugins, Vim is a great tool writing:
- vim-pencil: my favorite writing plugin. Vim-pencil brings a ton of nice things like navigation aids, smarter undo based on punctuation, and proper soft wrapping.
- vim-ditto: ditto highlights repeated words in a paragraph, just what I need to avoid repeating words all the time.
- vim-goyo: a Writeroom lookalike for Vim, goyo removes all distracting elements like modeline and line numbers.
- vim-colors-pencil: an elegant, low contrast colorscheme geared towards writing.
- vim-litecorrect: litecorrect automatically corrects common typing errors like “teh” instead of “the”.
vim-lexical: combined spellchecker and thesaurus. Vim-lexical lets me navigate between spell errors with
[sand quickly find synonyms with
vim-textobj-sentence: a plugin for better sentence navigation. I can move between sentences with
), I can cut a sentence with
dis. Depends on vim-textobj-user.
- vim-textobj-quote: this plugin smartly creates “quotes” so I don’t have to.
- ALE: the Asynchronous Lint Engine is a polyglot analysis tool that is not limited to code. It supports a bunch of style checkers like proselint and LanguageTool.
- vim-orgmode: I’ll admit that, before I saw the errors of my ways, I communed with the one that should not be named. During the time I used Emacs, I never fully switched away from Vim, that alone should have told me something.
For my labors, I gained something invaluable: I found Org mode. For me, Org-mode is the most intuitive and straightforward way of interacting with text. This filetype plugin only implements a subset of all its features, but even so, it’s good enough for my purposes.
While not Vim-related, I also find these tools irreplaceable in my workflow:
- pandoc: a command-line markup converter. Supports dozens of formats, including Org-mode and markdown. I usually write in Org and then export to the target type.
TitleCase.pl: John Gruber’s title case Perl script. I haven’t found a good native Title Case plugin for Vim, so I just use a
- grip: view local Markdown files with GitHub renderer. I use it to preview how my files will look before pushing them.
My complete Vim config can be found in my dotfiles.
Install gnu stow.
Clone the repository on $HOME
git clone firstname.lastname@example.org:TomFern/dotfiles.git
- Install links
cd ~/dotfiles stow .