Re: [ELPA] propose to add vundo.el to ELPA

[Yuan Fu <casouri@gmail.com>]

> On Apr 4, 2022, at 8:41 PM, Michael Heerdegen <michael_heerdegen@web.de> wrote:
> 
> Yuan Fu <casouri@gmail.com> writes:
> 
>> I wrote vundo.el a while ago and it’s now quite stable. It displays
>> the undo history in a tree form like undo-tree. Unlike undo-tree,
>> vundo doesn’t require you to replace undo commands and track changes
>> itself, rather it generates the tree fresh from ‘buffer-undo-list’. Do
>> you think vundo would be a good addition to ELPA?
> 
> Tried it out shortly.  Looks very useful and cool and easy to use and
> well done.
> 

Thanks for you kind words and suggestions!

> Some minor comments:
> 
> - Maybe mention the arrow keys in the introduction (that they work)?
> 
> - In undo-tree, one had to select a different branch before one could
> "walk" into it.  For vundo it's the other way round: you first have to
> select the first element of the active branch, after the root, and only
> after that you can activate a different (sibling) branch (or did
> undo-tree add virtual roots or so?).  Dunno what interface approach I
> like more.  But because I had tried undo-tree, your approach feels
> unfamiliar.  Dunno how others see that (AFAIR, undo-tree felt strange
> in the same aspect when I had tried it first, too=.

I now added further explanations.

> - Question: here in the comment:
> 
> ;; update. Vundo catches up the next time you invoke any command:
> ;; instead of performing that command, it updates the tree.
> 
> do you mean "next time you invoke any _vundo_ command"?  Otherwise I
> don't understand the sentence - buffer changes happen via commands - so
> what command actually do update?

Yes, any vundo command. Pressing f/b/n/p will not move in history but update the tree.

> 
> - And here are some typos I think (without warranty, I'm not perfectly
> speaking English):

Thanks, applied!

Yuan