vundo VS deadgrep

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.

Deadgrep (uses ripgrep and evil-collection has a binding) takes me to my happy place -

https://github.com/Wilfred/deadgrep

theres a package for this that’s god tier: deadgrep

this is cool too Wilfred/deadgrep: fast, friendly searching with ripgrep and Emacs

rg.el or deadgrep: Emacs interfaces to ripgrep, a grep-like tool that is very fast. This lets us search across a large number of files for a pattern of text. The disadvantage of searching for text is that if you are looking for the method called foo and there are hundreds of them that exist, it can be hard to know which one you really want. On the other hand, at the scale and complexity that you are talking about, I can imagine that more IDE-like tools just start failing.

Yes in this area (text search) there is many alternatives. Wilfred Hughes (author of deadgrep) has listed them in: https://github.com/Wilfred/deadgrep/blob/master/docs/ALTERNATIVES.md

Anyone interested in this should also check out deadgrep: https://github.com/Wilfred/deadgrep

Deadgrep does this, IIUC (I use ripgrep.el instead, but I think deadgrep does something like what you want)

deadgrep is an interface to ripgrep.