Zsh Mailing List Archive
Messages sorted by:
Re: Why the widget bound to menuselect isn't called?
- X-seq: zsh-users 24058
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Sebastian Gniazdowski <sgniazdowski@xxxxxxxxx>
- Subject: Re: Why the widget bound to menuselect isn't called?
- Date: Sat, 13 Jul 2019 09:39:34 -0700
- Cc: Oliver Kiddle <okiddle@xxxxxxxxxxx>, Zsh Users <zsh-users@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1fLnEVJmiPev8gMDn9peKx1lz9ncBDlPFvrtJhxIdy0=; b=xLujD2v6Hu9w2vvd4dFsIKpTXz78SbbIKaigtUyDQCG6aHsbKrun7wl/7/sok4vc1b PTRoi1c50IRm0OG33kmLo6yunyr46XKEzyZcXeRsdpZNxI7vbsV/OFWMVZyaazYZCiPg NqKPh0ztH3HQb84myH4kv3xFSij4N9mEjGr3GgdPOHoqYELbARlz+m53omSJLEIyGfqt LhbYCzZx6SYuRWzfHTvOgJp2mtxpqRGNLd7U0sk7KzOviBubEBGXU/FKTqo4Dz24qS1Q IcsD6m9ZfCkWTYYVYNNXP5n8LpI4tvkyR7VmFQ/LDxYwr4ovRVvXh5fmTzBjrw/hfuU9 aHzg==
- In-reply-to: <CAKc7PVDktOywqbY28eMgrha2pQ30QxO4eA7QdA1C5a54=8B99w@mail.gmail.com>
- List-help: <mailto:email@example.com>
- List-id: Zsh Users List <zsh-users.zsh.org>
- List-post: <mailto:firstname.lastname@example.org>
- List-unsubscribe: <mailto:email@example.com>
- Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
- References: <CAKc7PVAyX6-J1r-E-pRbzdajofQ4CG8tK3WxpD3N0vR9+zoECQ@mail.gmail.com> <33999-1563008359.364082@ccgB.SxHS.A_VB> <CAKc7PVDktOywqbY28eMgrha2pQ30QxO4eA7QdA1C5a54=8B99w@mail.gmail.com>
On Sat, Jul 13, 2019 at 5:20 AM Sebastian Gniazdowski
> The docs also say:
> "any other zle function not listed leaves menu selection and
> executes that function."
> so the widget should be apparently still plainly executed.
What you're missing is this bit:
Any key that is not defined in this keymap or that is bound to
`undefined-key' is looked up in the keymap currently selected.
That means you exit the menuselect keymap and return to the "current"
keymap before the binding for the keystroke is looked up; it doesn't
mean that the function looked up in the menuselect keymap is executed
> It seems to me that the main problem / idea is to replace the above
> check(s) which are keymap-specific to a more general solution
Menuselect is restricted in this way deliberately so that the user
can't perform any action that would garble the screen or confuse the
cursor placement. The right thing would probably have been to create
a new set of widgets specific to menuselect and simply declare that
they couldn't be changed, but as a shortcut the most similar existing
actions were simply co-opted.
Messages sorted by: