• 🔥 Transform your Neovim into a full-fledged Integrated Writing Environment (IWE): Write, Edit and World-build at the speed of thought
• 💤 Easily customize and extend your config with lazy.nvim
• 🚀 Stupid fast
• 🧹 Sane default settings and options for writers
• 😻 Eye candy in the form of beautiful color schemes, in dark and light modes, including flavours of Catppuccin, Gruvbox, Nord, NightFox
• 📦 Comes with a wealth of plugins for longform writing, interconnected note-taking (wikis, etc.), and screenwriting. All pre-configured and ready to use

OVIWrite is a NeoVim powered Integrated Writing Environment (IWE) built using LazyVim and 💤 lazy.nvim.

The goal is to make it as easy as possible for writers to start using NeoVim out of the box.

This begs the question: what kind of writer would gravitate towards OVIWrite in the first place? Good question. I spend some time discussing it below.

At first Vim, and now NeoVim, have formed the basis of my dream writing environment. Who even dreams of their writing tools? I have no answers except to say that I do venture outside regularly to touch grass and talk to people - don't worry.

I wanted a writing tool that ticked these boxes:

• Fast AF
• Switches seamlessly between three specific kinds of writing
  • Long form prose (i.e. novels, academic writing, reports, essays)
  • Research and note-taking
  • Screenwriting
• Supported a wide range of plain text standards including Markdown and LaTeX.
• Adaptable to any platform, Unix style OSs (MacOS, Linux) or otherwise (Windows), desktop or mobile, Android or iOS
• Offered the features of traditional word processors (Spell and Grammar checking for instance)
• Offered opinionated quality of life improvements such as Version Control through Git

This is a tall order to ask for word processors. It is why conventional word processing software such as MS Word fails, at least for me.

Granted I wrote my first novel on MS Word, I came to find that it wasn't extensible enough to scale with my needs, nor was it nimble and fast.

An ideal writing tool should adapt to a writer's needs at a moment's notice.

• Get back to working on the novel? Sure, here's a beautiful LaTeX template for me to work on my novel.
• Write a screenplay? Why not?
• Build an inter-connected network of notes like Obsidian or Notion? Done.

Here are two demos I presented at the NeoVimConf where I presented two early versions of OVIWrite.

• Writing, Editing and World-Building at the Speed of Thought (version 0.1) (Nov 2021)
• Vimkipedia: Or How I Built my Second Brain Using Vim (version 0.2) (Dec 2022)

Essentially, these two talks served as early demos of OVIWrite versions 0.1 and 0.2. However, the eagle-eyed among you will notice I used a combination of Vim and NeoVim during these talks. This was because I couldn't get some Vim-specific plugins to work with NeoVim, a problem that has since been solved.

This version of OVIWrite is built entirely in Lua, and follows the modular structure of LazyVim.

This is version 0.4 (Dec 11th 2023)

You will notice that Vim and NeoVim are used interchangeably here. This might appear confusing at first so let's be clear:

• Vim is a text editor whose roots go back to the early 80s. Its creator was the late Bram Moolenaar . Among its many innovations that have aged well in its four decades is the notion of Modal Editing. Modal editing text editors like Vim change your keyboard functionality based on what mode you are in.
• Vim allows for a number of modes: Normal, Insert, Visual, Command and Replace modes.
• NeoVim is a 'fork' of Vim, a modern interpretation of what Vim can be. It's about a decade old and is maintained by a core group of maintainers, led by Justin M. Keyes. It inherits Vim's modal-editing philosophy, but has moved to a modern programming language: Lua
• Both Vim and NeoVim have rich eco-systems that extend the editor's functionality to suit the exact needs of the user.
• These eco-systems are thriving as a result of tireless plugin makers, some of whom have created, and continue to maintain, dozens of plugins
• Most plugins are created for explicit software engineering/programming tasks. A few plugins are created for writing of prose or other text manipulation tasks outside of conventional programming
• OVIWrite is based on NeoVim; specifically it is based on an existing NeoVim starter kit LazyVim
• OVIWrite uses a curated list of writing-centric plugins along with some plugins that are traditionally for software engineering tasks, but whose functionality has application in the work of writers or anyone working with large chunks of text

I hear you: Who is this for?

Personally, I think of Vim/NeoVim as analogous to a musical instrument, say a piano. Are pianos meant only for world-class pianists? No.

The first interaction with a piano is often messy, confusing and overwhelming; stick with it, and there is a little bit of magic waiting to be experienced.

This mindset has helped immensely in scaling the steep learning curve that comes with Vim's modal editing philosophy.

But unlike me, writers like you don't have to invest the additional time in learning how to wrangle Vim to be a tool for writing. All you need is a couple of weeks practicing Vim motions and understanding its different modes.

Once you overcome that hurdle, install OVIWrite and get writing!

Only you can answer that. I don't consider myself to be a tech person - tech savvy, yes but I can barely read code myself.

So no lies here: (Neo)Vim motions and modal editing requires a rewiring of our writer brains. But the good news is that it shouldn't take more than two weeks of 10-15 minutes a day. Vimtutor, built into Vim, is the best place to practice.

There is also some steep knowledge acquisition required to understand NeoVim's internal nuts and bolts. This is only required if you want Vim to work exactly as you want it to. I did, which is why I set off on this journey three years ago.

You don't.

OVIWrite offers a higher floor from which to start your own explorations.

You don't need to know how to program or read Lua code, to use OVIWrite. All that work has been done for you. Nothing is stopping you from peaking behind the curtains at the source code. Add or modify the code as you see fit if you are feeling extra adventurous

More good news: Vim is almost 40 years old. The community has been around for decades, and have extensively documented tips, tricks and hacks. Chances are the error message you are seeing has been seen countless times before by countless people, and in all those occasions there was an experienced Vim user helping out a new-comer. I can speak from experience on this last fact.

Once again, thinking of OVIWrite as akin to a musical instrument might be the best way to overcome its apparent complexity; instead of music, OVIWrite is purpose-built for efficient (and damn near magical) textual recall, creation and manipulation.

TL;DR:

Being tech-savvy will make this easier but it is not a requirement.

Being patient is.

Heavy Googling is (as any programmer will tell you).

I can only offer personal anecdotes here in lieu of a more scientific approach.

I have steadily become very productive in the three years since my first encounter with Vim.

The procrastination associated with writing has disappeared, and I believe part of that is because I don't have to struggle through the bloated mess that is MSWord.

Editing, too, has become a joy because editing is Vim's superpower. Combined with the curated plugins included in OVIWrite, you should be writing, editing and world-building at the speed of thought!

Most writers writing on word processors use Rich Text. Rich Text, for all its benefits, does come back with significant drawbacks: vendor lock-in being a primary concern. Rich Text also doesn't age well. Rich text's older, less glamorous kin, Plain Text ages better, doesn't lock you into a vendor, and gives you the freedom to choose the tools that are suited for your work. For more, read The Case for Plain Text

Git is a robust version control system initially designed for software development, and has emerged as an invaluable asset for my writing workflow. Really, I think it's damn near criminal that we don't teach writers Git at some point in their developmental stage. Read more here

• Write, Edit, World-Build at the speed of thought: OVIWrite liberates your writing process by focusing on plain text, freeing you from vendor lock-in for unparalleled flexibility.
• Effortless Collaboration: Built-in version control using LazyGit ensures seamless tracking and collaborative writing experiences
• Versatile Syntax Support: From LaTeX to Markdown and from Org-mode to Fountain, enjoy comprehensive syntax support for every writing endeavor—from reports and essays to screenplays and personal wikis
• Flawless Composition: Spellcheck, thesaurus, and dictionary tools integrated for a seamless writing experience
• Built-in Translator: A built-in translator effortlessly translates between English and a diverse range of languages, breaking down language barriers with ease.

I use OVIWrite for the following use-cases:

• LaTex documents for my novels and academic writing
• Fountain files for writing scripts and screenplays
• Markdown and Org Mode files for writing simpler reports and blogs
• Vim-wiki for my personal Zettelkasten

See screenshots below.

I needed an Integrated Writing Environment, a toolkit that was fast, yet extensible enough to scale with a writer's changing requirements.

I spent a lot of time writing on diverse IDEs to get a sense of what I wanted out of my IWE; in fact, my inspirations for OVIWrite were VSCode, PyCharm and indeed the many Vim/NeoVim inspired distros like NVChad, LunarVim, and Doom Emacs.

I currently run this version of OVIWrite on my Mac (MacOS Sonoma 14.1.2), Linux (popOS 22.04 on my desktop, and Ubuntu Server 22.04 on my server), and Android 12 (OxygenOS 12.1 on a OnePlus 7T). I don't have a Windows machine to test at the moment. iPad testing is ongoing. I am fairly confident that OVIWrite will work pretty great on a semi-recent Android tablet (I don't have an Android tablet to test), as long as Termux is installed.

Note: The screenshots below show a variety of color schemes at play: Nightfox, DawnFox and NordFox. Also included in the config: Gruvbox and flavours of Catppuccin. I've included my favourite color schemes; users are, of course, free to add whatever color scheme that is available in the NeoVim ecosystem.

• Longform Writing; LaTeX

• Longform Writing; Org-Mode

• Longform Writing; Markdown

• Screenwriting in Fountain format

• Zettelkasten

• Neovim >= 0.8.0 and its associated dependencies (needs to be built with LuaJIT)
• Git >= 2.19.0 (for partial clones support)
• a Nerd Font (optional but highly recommended)
• LaTeX compiler
• Pandoc

Detailed Installation instructions can be found on our wiki

You can download the zip file containing all the source code. Copy it into the appropriate folder.

git clone https://github.com/MiragianCycle/OVIWrite.git "${XDG_CONFIG_HOME:-$HOME/.config}"/nvim

Command Prompt

git clone https://github.com/MiragianCycle/OVIWrite.git %userprofile%\AppData\Local\nvim\

Powershell

git clone https://github.com/MiragianCycle/OVIWrite.git $env:USERPROFILE\AppData\Local\nvim\

OVIWrite uses which-key.nvim to help you remember your keymaps. Just press any key like <space> and you'll see a popup with all possible keymaps starting with <space>.

• default <leader> is <space>

    - [ ] Public demo on YouTube
    - [X] LSP integrations for Grammarly, Proselint
    - [X] Autocomplete
    - [ ] Testing 
	    - [X] Linux (Debian and Ubuntu-based): ✅
	    - [X] MacOS (> 10.0): ✅
	    - [X] Linux: ✅
	    - [X] Android (> Android 10)(via Termux): ✅
	    - [X] iPad: ❌
	    - [0] Windows: 
    - [ ] Documentation
	    - [X] Website on GitHub maybe?
		    - [X] Blog: The Case For Plain Text
    - [ ] In-depth Help Documentation
    - [ ] Installation streamlining
    - [ ] Features planned for version 0.5
	  - [ ] Snippets
	  - [ ] BibTex and Zotero integrations

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.

• @MiragianCycle, Theena Kumaragurunathan
• @mhegreberg, Mark Hegreberg

None of this would be possible without the contributions of the entire Vim and NeoVim eco-systems. Please contribute in anyway, financial or otherwise, to these incredible projects and the tireless people who maintain them.

GNU GPLv3

1. Friction: Or How I Learnt to Stop Worrying and Love Vim
2. Configuring Vim as a writing tool
3. Every year is someone's year of Linux Desktop