Zsh Mailing List Archive
Messages sorted by:
Re: Why the widget bound to menuselect isn't called?
- X-seq: zsh-users 24060
- From: Oliver Kiddle <okiddle@xxxxxxxxxxx>
- To: Sebastian Gniazdowski <sgniazdowski@xxxxxxxxx>
- Subject: Re: Why the widget bound to menuselect isn't called?
- Date: Sun, 14 Jul 2019 12:38:21 +0200
- Authentication-results: amavisd4.gkg.net (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.co.uk
- Cc: Zsh Users <zsh-users@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s2048; t=1563100703; bh=PHtrOljqH+gCjeW4LzgqZel47lL4brsGiyUt3TcxJwI=; h=From:References:To:Subject:Date:From:Subject; b=fKot0nFIqQmvUYwqBpjOTnQIa6enSIQlfain3PShJYf0SMByqmu9mGrkmigZxa6Gnp7feK+fHT8RflnZv315hZmYk9o0C8tqAOGaox9v/gUP6VI8Vl8yv0RXoyLkfLHkAruMiGQK/1uTlMp+tuLf5+COZbW9LzZ+4ZNjGc55x0QawJIqv4fb+8qMoC9ZhUOh9wY5QqetkesGt40wsWK3riLnHHAjbRfUns0ltO3QK9dDETJ7nHSSfrdgU7wdRC0coEMwjMG7t6ysnp/FVHe2V7sTcHPxTy6H8AgOanEEGYNNOyBqwLBAnYoC4Lm9E8zP120YkeI0C1QWYM3bfCwhMQ==
- In-reply-to: <CAKc7PVDktOywqbY28eMgrha2pQ30QxO4eA7QdA1C5a54=8B99w@mail.gmail.com>
- List-help: <mailto:firstname.lastname@example.org>
- List-id: Zsh Users List <zsh-users.zsh.org>
- List-post: <mailto:email@example.com>
- List-unsubscribe: <mailto:firstname.lastname@example.org>
- 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>
Sebastian Gniazdowski wrote:
> 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, which
> ??? allow automatic mapping of an invocation of a widget to a
> $KEYMAP-variant of the widget
> ??? provide a set of base widgets that are $KEYMAP-specific, so that
> users can use them as the building blocks of custom widgets.
Yes. However, there would be further problems like ensuring that non-
menu selection widgets abort menu selection and preserve backwards
compatibility as far as possible. Providing basic widgets
would be the easy (but tedious) part. The automatic mapping is harder
because an approach needs to be worked out and designed.
> ??? the above check(s) are an entry point to a set of such
> keymap-specific widgets and seem to implement the keymap-specific
> automatic selection of the widgets, however they're a high level
> widgets, not a fine-grained building blocks,
> ??? because of this lack of fine-grained widgets the designers of the
> code decided to not allow overloading of them.
> Is this correct? Because if yes, then it would seem that the existing
> mechanism can be still used, if the fine-grained widgets will be
> provided and the overloading of the widgets will be enabled.
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).
> 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.
Messages sorted by: