20 Aug
2010
20 Aug
'10
4:29 p.m.
On Fri, Aug 20, 2010 at 10:19 AM, Tim Harper <[email protected]> wrote:
... I don't fully understand how vimpulse-surround had repercussions and was affecting vimpulse surround behavior, I will read more carefully into it.
I understand now. I've pulled the latest vimpulse code, and it appears to have addressed this issue. It still seems like it would be wise to define the "vimpulse-define-operator" macro. Vegard: Would the defadvice route [1] not work? (as opposed to option #2, the null range selector). Tim [1] http://permalink.gmane.org/gmane.emacs.vim-emulation/527