vundo VS hydra

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

Actually I put together vundo diff functionality which I use everyday; it's very simple so you can easily stick in your .emacs. Or perhaps will get added to vundo (maybe with a special color for the "diff-from" circle, or the ability to set a "from" and "to" for diffing across a few undos) . It's "on demand" rather than automatic, but I actually find it easier to get a diff buffer where I want it, then leave it as I move around the tree. Very happy with vundo.

And if you want a graphical undo without the large underlying data structure, give vundo a try. It just re-uses the same undo data structure emacs already keeps.

If you still want undo visualization, there's vundo that gives you a tree display of the state of the built-in undo: https://github.com/casouri/vundo

Is there anything like vundo for winner-mode? Or is any body have a winner-mode configuration that would behave like vundo?

Take a look at vundo:

vundo: Visualize the undo tree.

You could try vundo

I switched from undo-tree to vundo and am favorably impressed.

Submitted a PR to simplify that.

You can also use Hydra for Emacs.[1] Once I discovered how to configure Hydra, I made it a habit to make one for every new major mode I need to use.

[1] https://github.com/abo-abo/hydra

Have you considered a hydra?

An Emacs specific example: I'm working on a few go projects at the moment and go requires recompilation after changes. Step one was finding auto-recompilers for my projects (I'm using both air and reflex in various projects). Step two was realizing that I spent a lot of time switching to the buffer where the output is printed, so I wrote a little hydra menu to make that easier. Then I found myself having to restart those processes each time I restarted Emacs, so I went digging and found detached to manage the processes. Then I got tired of having to hunt for where the detached output was displayed in my frame so dug into sidebars to manage the windows more effectively.

I think the goal of the hydra package is to provide such functionality.

I would I also encourage anyone who does not want to use modal editing to look into repeat-mode, hydras, and key-chord.

The C-c prefix is designed for you, the user, to use for your nefarious deeds. Some things that may help with both binding and knowing what key does what would be a menu such as hydras or transient menus (which apparently are part of Emacs now so that's new).

For the very same reason, I started to use hydras: https://github.com/abo-abo/hydra - see my config at https://github.com/novoid/dot-emacs/blob/master/config.org

Hydra lets you define mini-modes with limited scope.

general.el also works well with hydra.el. Here's my hydra for window operations - it activates when I press ,w: