vim-arpeggio VS goyo.vim

Might be able to pull something like this off with https://github.com/kana/vim-arpeggio

If the reason for not liking jk is that it doesn't work for visual mode, and you are not using the which-key plugin, I would suggest the vim-arpeggio plugin. You'll have to hit jk very quick for exit so it won't interrupt j and k movement in visual mode

kana/vim-arpeggio for the jk ==> mapping

But today, I found the plugin vim-arpeggio, it maps key chords, i.e., keys pressed (seemingly) simultaneously. I tried it out and omg, it solves everything. No longer do I need to wait for timeoutlen, no longer do I miss a k at the end of word: jk and kj only triggers when pressed simultaneously, and I don't have to set timeoutlen insanely short.

vim-arpeggio: Keychords for custom mappings (since there are not enough 'free keys' available)

The half keyboard basically mirrors the keyboard while the spacebar is held down (so you have, for example, normal “asdf” that then turns into “;lkj” while space is pressed). It sounds weird but if you touch type it’s surprisingly easy to get used to because the same fingers press the same keys—your index finger presses both “f” and “j” as normal. You might be able to emulate it with something like vim-arpeggio.

But there is e.g. this plugin, that tries to achieve it, possibly others as well: https://github.com/kana/vim-arpeggio

I wrote a manuscript in vim a couple Novembers ago, for NaNoWrimo. I used a couple plugins, primarily Goyo [1] to add some margins, but otherwise, yeah, plain vim.

I don't think it was really any more productive than my current workflow in Obsidian. Vim keybindings are more useful for editing than for writing (and for editing code in particular, where the changes you're making are much more structured). Also, while the extra features afforded by Obsidian don't really make a difference during the writing process, I find they're really useful for outlines and other preliminary work, which is something of a point against a vim-only workflow unless you want to use vimwiki [2] or something.

Granted, Obsidian is still a markdown-based tool, so there's still some level of minimalism going on there, but by that point we're really discussing markup vs word processors, which is its own conversation—and to my mind, a much more important one. I much prefer working in markup than in a rich text editor, because plain text is easy to edit and process through the terminal, and because it lets me separate style choices from content.

I find that the markdown live preview that editors like Obsidian and Typora provide (and which vim doesn't) is a really nice compromise between a slick composing experience and the technical affordances of markup. Between that and Obsidian's hypertext features, I think I'll stick with Obsidian for the foreseeable future.

[1]: https://github.com/junegunn/goyo.vim

[2]: https://vimwiki.github.io/

Maybe https://github.com/junegunn/goyo.vim could be useful then.

Goyo is a distraction free plugin for vim/NeoVim. https://github.com/junegunn/goyo.vim. Typically used for people wanting to write inside of NeoVim. There isn’t a real purpose for me to use it other than I like the aesthetic looks. Thanks for replying!

Maybe not of use, but what about just one of your editors + the terminal? Using vim with the goyo extension similarly without the overlay. I write my notes with markdown.

I haven't maintained a Vim config in a few years now (more of an Emacs man now), but I do remember using Goyo in college. Looking back at it, I think it might scratch your itch as far as Vim plugins go, it even allows you to resize the area on the fly.

https://github.com/junegunn/goyo.vim

I went from https://github.com/junegunn/goyo.vim to https://github.com/folke/zen-mode.nvim and now this

Can't see https://github.com/junegunn/goyo.vim mentioned anywhere in this thread.

This feels real similar in concept to limelight and goyo. Nice! 👍🏻