bpstahlman / vim-sexp Goto Github PK

Your clone commands are great and on first inspection look to behave exactly as I had in mind in guns#32 (comment). What if they could insert the contents of a register instead? There are a couple of specifics about behavior that would have to be figured out but I for one would be very happy if this were realized.

I believe the problem lies in Vim-sexp's pervasive use of visual selections to mark text to be operated on. Either save and restore the selection, or use more non-invasive mechanisms: e.g., yankdel_range and put_at functions.

Noticed a need for this while dog-fooding the new targeted-jumps feature.
Note: I'm also thinking that it would be nice to have operator-pending versions of the targeted jump commands.
Note: I'm now thinking this may be pointless, as the real advantage of the "till" commands is seen when they're used with operators, but we currently don't support operator-pending versions of commands that violate list structure...

Appears to be catching upper->lower case transitions rather than lower->upper.

I believe vim-repeat plugin provides support for both repeat operator (dot) and undo/redo. Need to make full us of the latter capability, as the inability to undo vim-sexp operations is very annoying.