(it's a nit because I did discover in place of [zero], TL bound "|" to
this function, so just something to get used to...)

On Jun 18, 12:25 am, yarko <[EMAIL PROTECTED]> wrote:
> Another nit - but has to do with key binding machinery,
> so I'll bring it up:
>
> Motion in VI:
>
> up-down-left-right work fine with k-j-h-l...
>
> the other motions I often use are beginning / end of line, so I've
> noticed
> beginning (first non-blank on a line) => ^ works;
> beginning of line => 0 [zero] doesn't work.
>
> Notes in vi bindings say "0 not used because if bound it won't be
> inserted during insert/editing mode".
>
> And an even nittier:  "dw" (delete word" deletes to the next word in
> VI, but not in Leo.
>
> As long as you and Edward are thinking
> about this stuff...
>
> Regards,
> Yarko
>
> On Jun 17, 10:02 pm, TL <[EMAIL PROTECTED]> wrote:
>
> > I support removing the "@mode d::Delete... " you refer to.  However,
> > it is not the cause of the delete line problem.  The problem Yarko
> > raised is simply Leo executing the "delete line" code as I implemented
> > it.  Coding the @mode functions in general is limited by a lack of
> > conditional branches and an existing set of available @mode commands
> > that weren't designed with Vi functionality in mind.  As a result,
> > some Vi commands don't work correctly under all situations.
>
> > I'll wait a few days before checking in the improved "delete line"
> > code.  I need the time anyway to test some vi bug fixes and new vi
> > commands that I've implemented as well as updating the documentation.
> > Let me know when you have finished with your changes.
>
> > Regards,
> > TL
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to