vim-mundo VS undo-tree

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

vundo is a simpler implementation: it reuses Emacs's tree and just implements the visualisation part.

undo-tree is a reimplementation of Emacs's tree based undo, that supports a visualization.

* undo-tree LOC: 4700. https://gitlab.com/tsc25/undo-tree/-/blob/master/undo-tree.e...

* vundo LOC: 1350. https://github.com/casouri/vundo/blob/master/vundo.el

That said, the situations seems murky still: the version in ELPA is newer (0.7.5), but it's still outdated, the home page advertises 0.8.2 as the latest version. And it moved to a different repository location. And looking at its history, it seems to never have included the version 0.7.5: https://gitlab.com/tsc25/undo-tree/-/commit/5da2a7aee98393d26a93c499dc79fcf793f161e1

It’s easier to mentally map that the default behaviour undo/redo for Emacs (which is not unreasonable, just complex).

The source for undo-tree contains documentation which very effectively describes the way the library works with examples and comparisons with how Emacs does things by default: https://gitlab.com/tsc25/undo-tree/-/blob/master/undo-tree.e...

Looks like the repo is moved to https://gitlab.com/tsc25/undo-tree