A Vim/NeoVim Configuration for Writing and Writers
OVIWrite (as in Oh-We-Write) is an attempt to make (Neo)Vim writer friendly out of the box.
I am a writer, not a tech person.
Coming across Vim for the first time last year was revelatory, but I'd be lying if I said the adoption process was easy. Indeed, it took me over two months to get Vim ready for my writing workflow. I was persistent but most users and writers aren't, which is a crying shame. Most writers would abandon Vim as too complex a beast. I too would have abandoned it but the Vim community on YouTube came to the rescue.
This repo is an attempt to address that potential loss of a user-group who stand to gain much from Vim.
Vim/NeoVim is the writing instrument of my dreams. I am a long suffering user of the ubiquitous Word by Microsoft. While Word has served me well, and allowed me to write a novel, it was always getting in the way of my writing. This is why I used Windows Notepad along with MS Word - it provided a more distraction-free writing environment than Word did, even if it wasn't powerful.
What I needed was a powerful text editor that was fast, portable, extensible (i.e. around a writer's workflow or rather my writing workflow), and with support for version control.
Vim ticked all these boxes, and then some.
I presented my use-case and workflow, contrasting the tools and workflows before and after Vim at the 2021 VimConf.
I could, but my personal .vimrc is a representation of my current work, which isn't only writing. Since I am engaged in teaching myself to code, much of my .vimrc aims to bridge my writing and coding workflows. I am assuming that most writers are interested in using Vim for writing.
The assumption here is that you, a writer, have already downloaded and installed Vim/GVim/NeoVim on your system. I have also assumed that you are on the verge of configuring your .vimrc file to be writer friendly.
If both of the above cases are true, then all you need to do is to download the vimrc in this repo and paste it into the appropriate file in the appropriate location based on your system. Default destinations for .vimrcs:
MacOS and Unix: $HOME/.vimrc or $HOME/.vim/vimrc MS-Windows $HOME/_vimrc, $HOME/vimfiles/vimrc or $VIM/_vimrc
I primarily use Vim-Plug to manage Plugins within Vim. Mostly because I've found it to be the easiest. The conventions used here will be for Vim-Plug but they can be adapted for your package manager of choice.
I will probably adapt this to Packer at some point in the future as I move to NeoVim, and a Lua-based config file, instead of the standard .vimrc.
This .vimrc has served me well on Linux, MacOS and Android (via Termux). I've tested it on the following systems:
Linux
- Ubuntu 20.04. Should work on Ubuntu derivatives such as pop!OS, Kubunutu, etc.,
- Debian 11
- Arch. Worked on Vanilla Arch, Arco-Linux and Garuda Linux.
MacOS High Sierra (I have a 10 year old Mac so this is the best I can do for the time being)
Android I have a OnePlus7T, running Android 11 (or OxygenOS 11.0.a.1 more precisely), with Termux. A note on Termux available on the Google Play Store: it seemingly doesn't get any updates and I can barely install any packages any more, which is why I moved to Termux version available on F-Droid. The repos are fresh, updated and have had no issues since moving.
Windows Yet to attempt testing on Windows.
The key-bindings I've used here are built around my (admittedly) wonky typing and keyboard recall. The SPACEBAR is the Leaderkey because it is the most ergonomically sound for me. If you feel otherwise, you are free to change.
As this .vimrc aims to be plug and play for writers interested in using Vim for their writing, I have chosen a fairly opinionated approach to what plugins (see section on Plugins for more details), what defaults (line-wrapping, relative numbers, etc.,), are necessary to begin writing on Vim immediately. This doesn't mean that this .vimrc can't be changed based on user preference; indeed Vim truly shines when you take the time to mould it for your exact specifications. The .vimrc has extensive comments to enable the final user to add, remove, and modify to their heart's content.
Most of these plugins are written in VimL, as opposed to NeoVim plugins written in Lua. The general rule of thumb that I follow is: Most plugins written for Vim work on NeoVim, but plugins written in Lua for NeoVim will not work on Vim.
Therefore, all plugins curated in this vimrc will be Vim-first i.e they should run perfectly fine on any any Vim install on any system as long as Vim 8.0 or greater is installed.
Plugins will be organized into levels.
Level 1 is what I would consider the bare minimum for writing and writers: spelling support, distraction-free writing, dictionary and thesaurus functionality, and maybe a Grammerly-like function that suggests changes to a given text.
GOAL: Make Vim the fastest, smartest, most portable writing scratchpad.
Level 2 plugins will turn Vim into a note-taking machine. At this point, you can conceivably use Vim as a note-taking tool in lectures, as I do. We will combine markdown, org-mode and vim-wiki to give users three distinct and incredibly powerful tools to take down better, more effective notes.
GOAL: Make Vim the fastest, smartest, most portable note-taking environment.
Level 3 plugins will turn Vim into a cutting edge production-ready writing environment that gives writers end-to-end granular control of their writing output. We will add Pandoc and Latex support, making it easier to produce beautiful documents that are a couple of key presses away.
GOAL: Make Vim the Writing Environment of your dreams. From initial idea to final output, nothing should be beyond the reach of this final version of Vim.
Please, and thank you.
Contributions are encouraged. Feel free to make a pull request with modifications. If you want to contribute at a deeper level - maybe even forking NeoVim for writing outright - do reach out to me. I will be happy to collaborate and learn from the community.
- Demo []
- Windows Testing []
- Tutorials []
- Detailed documentation
- Screenshots []
- @MiragianCycle, Theena Kumaragurunathan