Zsh Mailing List Archive
Messages sorted by:
Re: Why the widget bound to menuselect isn't called?
- X-seq: zsh-users 24061
- From: Sebastian Gniazdowski <sgniazdowski@xxxxxxxxx>
- To: Oliver Kiddle <okiddle@xxxxxxxxxxx>
- Subject: Re: Why the widget bound to menuselect isn't called?
- Date: Sun, 14 Jul 2019 23:56:01 +0200
- Cc: Zsh Users <zsh-users@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=bmlfLmpjiDqxA+TB5PHPfgkzGiGQHK8nm4QPY28kJ1E=; b=VPTOHI7+CYLjqxC5qYSeU9CxVK0lCyHpkp0XII/8YiFFmpLgeDyHlB+FpOLpvbSjWl cvjOO9hYjODkBqbTlgCzCTxVBqQ1BJMcUoYb3vUSb2V9aVLIxqT1NtDisixJ8RTNkDh0 6Dz7BHsFCSh7ir+5ssldJ3/7a/wYPNUt9/HUTQ9KPdy+xmQ539GMZNxCDR4jJb4Jm9dT ii9SvWxr5R9Fc5lBfWzdnbFbJt3E3OMRZNjDqz+/eAIsIT07LjkY+Jhw5CmI7j/Gd/74 ouMgf3zoYkPee32h8/LopocS1bQw9GUxQMER7oZ7aepKScBP4OSqNFDhAv8WxPe2YJ12 f9Xg==
- In-reply-to: <53445-1563100701.603642@DtMP.e8mM.jHzi>
- 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> <53445-1563100701.603642@DtMP.e8mM.jHzi>
On Sun, 14 Jul 2019 at 12:38, Oliver Kiddle <okiddle@xxxxxxxxxxx> wrote:
> The automatic mapping is harder
> because an approach needs to be worked out and designed.
> I'm not sure I follow what you're saying. It may have been better if
> there had been fine-grained widgets to begin with but that alone is not
> sufficient (either now or at the time of the module's inception).
I was making a point that the automatic mapping solely for the
menuselect case is actually available – despite being probably not at
the level of quality and design that we would expect from it – because
the complist module does automatically get the calls if they're done
on the menuselect keymap. So to solve the particular issue with
non-overloadable menuselect widgets what has to be done is to provide
the rest of the Zle widgets – to give them meaning in the menuselect
keymap, so that there's no risk that user's overloading widget will
call something's unimplemented – the Zsh script code isn't a threat
here, only the dot- i.e. original zle .widgets are.
> > It seems that it is about forwarding the keymap-specific mechanism to
> > the Zshell code in an consistent way with the C code. The question is
> > is this necessary?
> Consistency with Functions/Zle/keymap+widget isn't necessary.
> Not breaking backwards compatibility that allows menu selection key
> bindings to reflect users' normal key bindings is necessary. I was
> trying to outline some vague ideas on how this might be approached.
I wonder if the enabling of overloading of the menuselect keymap
doesn't break the backwards compatibility. The "always leave
menu-selection" behavior, for example, will be changed by it. An
configuration option, rather preferably zstyle, could be used to guard
the compatible behavior (BTW. are zstyles used to influence Zshell at
the C level currently?).
Messages sorted by: