From: Borzenkov Andrey <Andrey.Borzenkov@siemens.com>
To: "'Oliver Kiddle'" <okiddle@yahoo.co.uk>,
"'Virginia Mann'" <tuanglen@hotmail.com>
Cc: zsh-users@sunsite.dk
Subject: RE: menu selection and enter key
Date: Tue, 11 Mar 2003 10:19:06 +0300 [thread overview]
Message-ID: <6134254DE87BD411908B00A0C99B044F03A0B66A@mowd019a.mow.siemens.ru> (raw)
In-Reply-To: <2431.1047304522@finches.logica.co.uk>
> "Virginia Mann" wrote:
> > I'm configuring zsh for the first time and trying to understand the
> > features.
> >
> > I find menu completion very useful, and I like seeing the list of
> candidates
> > below it. <tab><tab><tab> yes, that's the one I want<enter>, and it
> > executes.
> >
> > Then I found menu *selection*, which let me see where I was as I tabbed
> thru
> > the candidates by highlighting where I am in the list, which is very
> > convenient. Unfortunately, when I reach the one I want and hit <enter>,
> it
> > no longer executes. Now it just inserts a space and sits there waiting
> for
> > me to enter more. I have to hit enter again to make it execute.
>
But you may just as well continue editing current line without executing it.
> accept-line in menu selection is redefined to do that. If I've
> understood what you want it to do correctly, you can do:
>
> double-accept() {
> zle accept-line && zle accept-line
> }
> zle -N double-accept
> bindkey -M menuselect '^M' double-accept
>
Would not simple
bindkey -M menuselect '^M' .accept-line
be easier?
-andrey
next prev parent reply other threads:[~2003-03-11 7:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-09 6:41 Virginia Mann
2003-03-10 13:55 ` Oliver Kiddle
2003-03-11 7:19 ` Borzenkov Andrey [this message]
2003-03-14 20:45 Virginia Mann
2003-03-17 10:31 ` Peter Stephenson
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=6134254DE87BD411908B00A0C99B044F03A0B66A@mowd019a.mow.siemens.ru \
--to=andrey.borzenkov@siemens.com \
--cc=okiddle@yahoo.co.uk \
--cc=tuanglen@hotmail.com \
--cc=zsh-users@sunsite.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).