vim-arpeggio VS vim-mundo

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

there's also telescope-undo and vim-mundo

I don't always need it, but when I do I find vim-mundo incredibly helpful. Understanding the vim undotree is hard without a visualization and mundo's ability to search my undo chunks makes it easy to revive some previous change that wasn't committed to version control.

Still using mundo here (https://github.com/simnalamburt/vim-mundo)

You mean undo/redo? that's u and . To view undos visually you can use a plugin like [vim-mundo](https://github.com/simnalamburt/vim-mundo

I'm glad you found something that works for you, and I don't mean to dissuade you even if I could, but to me that feels like an antipattern if you only use it for typed text.

Consider that with a text editor like Vim, for example, you can "time travel" [0] through your file's edits, or even have undo branches/trees [1][2] available per file. That saves you the trouble of having to transcribe text from screenshots, and also barely uses any storage space.

Plain text is also highly more portable and more likely to be recoverable in case of drive failure or file corruption.

Additionally, or alternatively, you could try any sort of manual versioning system or background automatic backup solution that keeps versions of files as you work on them.

[0]: https://vimtricks.com/p/vimtrick-time-travel-in-vim/

[1]: https://neovim.io/doc/user/undo.html#undo-tree

[2]: https://github.com/simnalamburt/vim-mundo

mundo undo tree

It's not just minutes either, you can do seconds with s, hours with h, days with d and get this - "writes" with w. You can also just simply go back to an arbitrary n number of buffer states before; but just like writes, that's hard to keep track of mentally and instead you should probably use a proper plugin for that.

I used to use Typora before I got into Neovim and realised that it wasn't free software either. Now I'm quite satisfied with my current setup, which uses: - aerial.nvim for header outline and navigation - run-code.nvim for running code blocks - vim-mundo for persistent undo history traversal (like Mac's time machine) - Prettier for auto-formatting Markdown as well as code blocks to their respective languages

Using a plugin like undotree (or Gundo, or Mundo) to visualize the edit history is by far the most practical solution to OP's problem, and I'm shocked you're the only person to suggest it.

There's a fork called mundo which has an inline diff mode that I'm a big fan of — https://github.com/simnalamburt/vim-mundo