From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: push-input, accept-and-hold, etc., and vared
Date: Thu, 9 Mar 2000 10:44:38 +0100 (MET) [thread overview]
Message-ID: <200003090944.KAA18799@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Mon, 6 Mar 2000 06:59:35 +0000
Bart Schaefer wrote:
> Using push-input or accept-and-hold during vared has unexpected (to me,
> at least) behavior -- to wit, the value of the variable is pushed onto
> the command input stack, and vared exits, whereupon the value of the
> variable is immediately popped into the PS1 editor buffer.
>
> There may be obscure circumstances in which this is what is meant, but
> (particularly in the case of "vared mapfile[...]") that's seldom so.
>
> I'm not precisely sure what to suggest we do about it, though. It might
> be nice to have accept-and-hold set the variable but not exit vared (this
> would be particularly useful with "vared mapfile[...]"). I'm at a loss
> with respect to push-input and friends. Perhaps they just shouldn't work?
>
> On a semi-related question, is it time that vared had its own keymap?
> The problem is initializing it properly, I suppose.
I was thinking about an option to vared allowing users to say which
keymap they want to use there. And allowing users to define keymaps.
But this would require some more discussion, I think, so I held myself
back (also thinking about the things Anthony once spoke about -- quite
a while ago in a message which number I don't seem to have any more).
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-03-09 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-09 9:44 Sven Wischnowsky [this message]
2000-03-10 10:30 ` Andrej Borsenkow
-- strict thread matches above, loose matches on Subject: below --
2000-03-06 6:59 Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200003090944.KAA18799@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).