I've spent the last couple days updating my ancient personal
viper/Vimpulse configuration to the current devhead.  Pretty happy,
especially with these:

  - working visual mode
  - text objects
  - /- and ?-style searching integrated with isearch for better
    highlighting

So, great work. :-)  It's really nice to see development moving forward
again.

Now, the single impacting regression I've run up against so far is with
undo.  Unlike Vim and my old version of Vimpulse, reverting a change
with e.g. "cw" requires two undos instead of one.  This is a pretty
significant deviation, at least for my workflow.

I scanned through the code and saw vimpulse-connect-undos, currently
disabled because of a dependency on undo-tree.el.  A couple questions:

  1. What makes undo-tree.el preferable to redo.el, for Vimpulse's
     purposes?
  2. Is fixing "cw" and friends a priority, or is it something that
     users of Vimpulse have learned to live with?

Thanks,
Stephen

Attachment: signature.asc
Description: Digital signature

_______________________________________________
implementations-list mailing list
[email protected]
https://lists.ourproject.org/cgi-bin/mailman/listinfo/implementations-list

Reply via email to