push-input and vared

push-input and vared

[Mikael Magnusson]

When you run vared after push-input, the cursor location is restored
from the pushed line when varediting, and then when you're done, the
command is restored with the cursor at the end.

You can also push-input from inside vared which doesn't do anything
useful, maybe that should just be inhibited?

-- 
Mikael Magnusson

(Maybe I should have just stuck this in the other thread I just made,
but I feel like this is more of a bug and that is more of a user
thing.)

Re: push-input and vared

[Bart Schaefer]

On Oct 26,  3:31pm, Mikael Magnusson wrote:
}
} You can also push-input from inside vared which doesn't do anything
} useful, maybe that should just be inhibited?

Although it's true that push-input aborts the current vared, you can
still use the pushed input with get-line, even in a subsequent call to
vared.  (push-line-or-edit is a bit *less* useful because it performs
the get-line for you.)

You can "fix" this yourself by creating a keymap that doesn't have the
bindings for those functions, and then installing it with "vared -M ...".
I don't think the confusion of creating a built-in vared keymap would be
worth the effort.