"df" not deleting the searched charactor

York Zhao gtdplatform at gmail.com
Mon Jun 13 21:00:28 CEST 2011

Nice "fix", thanks a lot.
Another minor issue I've just noticed after started using the "undo-tree"
was that the "hjkl" are not working in the undo-tree-visualizer-mode. But
that's just small inconvenience.


On Sun, Jun 12, 2011 at 4:28 PM, Vegard Øye <vegard_oye at hotmail.com> wrote:
On 2011-06-12 00:59 +0200, York Zhao wrote:

> It turned out that it was because I re-binded the 'f' key to my
> function. But what my function did was simply a check on whether
> edebug was active, if edebug was not active, it simply called the
> old function.

Some Viper motions need to be called with a special argument in order
to work properly in Operator-Pending state. As your function called
`viper-find-char-forward' without this argument, it behaved
differently. Commit 3221608 tries to eliminate this trap by using
`defadvice' to generate the argument automatically.

I have also added some edebug compatibility bindings in commit 4bdc95f.
I usually run edebug in Emacs state or Insert state, but now it should
also work reasonably well in vi state.


implementations-list mailing list
implementations-list at lists.ourproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ourproject.org/pipermail/implementations-list/attachments/20110613/8c23a641/attachment.htm 

More information about the implementations-list mailing list