vundo VS ido-at-point

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.

(defun completing-read-at-point (start end col &optional pred) "Inspired by https://github.com/katspaugh/ido-at-point" (if (minibufferp) (completion--in-region start end col pred) (let* ((init (buffer-substring-no-properties start end)) (all (completion-all-completions init col pred (length init))) (completion (cond ((atom all) nil) ((and (consp all) (atom (cdr all))) (car all)) (t (completing-read "Completions: " col pred t init))))) (if completion (progn (delete-region start end) (insert completion) t) (message "No completions") nil)))) (setq completion-category-defaults nil) (setq completion-in-region-function #'completing-read-at-point)