From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Cc: Olivier Teuliere <ipkiss@gmail.com>
Subject: Re: Limitations of menuselect
Date: Wed, 27 Feb 2013 18:09:09 +0000 [thread overview]
Message-ID: <20130227180909.4e0ef40d@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <20130227175330.0b9e8c5c@pwslap01u.europe.root.pri>
On Wed, 27 Feb 2013 17:53:30 +0000
Peter Stephenson <p.stephenson@samsung.com> wrote:
> On Wed, 27 Feb 2013 18:27:31 +0100
> Oliver Kiddle <okiddle@yahoo.co.uk> wrote:
> > It seems any keybinding picked up from the main keymap
> > will work though menu selection is exited first. For anything from the
> > menuselect keymap, it hard codes the actions with various widgets being
> > overloaded from their original meanings. I'm not sure that I get the
> > point of this. If it meant that your existing key-bindings would do
> > something appropriate it might make sense but you do have to duplicate
> > them in the menuselect keymap. Was this perhaps a bug introduced later
> > such as when local keymaps were added?
>
> Hmm, I think the main keymap is supposed to show through the menu
> selection map in places where nothing's explicitly set, so you don't
> need to rebind the widget. So that probably is a bug.
Actually, I think this *does* work, it's just hard to find a widget that
isn't overloaded, but now I have, it does cause exit from menu select
and then the widget's normal effect, without any additional binding
required.
(Unless you meant overloading widgets was a bug, but that's been there
all along.)
pws
next prev parent reply other threads:[~2013-02-27 18:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 21:49 Olivier Teuliere
2013-02-27 17:27 ` Oliver Kiddle
2013-02-27 17:53 ` Peter Stephenson
2013-02-27 18:09 ` Peter Stephenson [this message]
2013-02-28 1:07 ` Oliver Kiddle
2013-02-28 9:34 ` Olivier Teuliere
2013-02-28 10:15 ` Bart Schaefer
2013-02-28 1:59 ` Bart Schaefer
2013-03-01 23:59 ` Oliver Kiddle
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=20130227180909.4e0ef40d@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.com \
--cc=ipkiss@gmail.com \
--cc=zsh-workers@zsh.org \
/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).