Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: push-input and vared
- X-seq: zsh-workers 28367
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh workers <zsh-workers@xxxxxxx>
- Subject: Re: push-input and vared
- Date: Tue, 26 Oct 2010 07:35:52 -0700
- In-reply-to: <AANLkTin4=81tGqUEaUGmzbf2jF+iBvt9g1R+4FfVFwSZ@xxxxxxxxxxxxxx>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <AANLkTin4=81tGqUEaUGmzbf2jF+iBvt9g1R+4FfVFwSZ@xxxxxxxxxxxxxx>
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.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author