From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: More local keymaps?
Date: Tue, 29 Jun 1999 13:15:00 +0200 (MET DST) [thread overview]
Message-ID: <199906291115.NAA17852@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Tue, 29 Jun 1999 14:51:26 +0400
Andrej Borsenkow wrote:
> I currently have Alt-RETURN (actually, ESC-RETURN) bound to
> accept-and-menu-complete. That's fine and nice ... but after last patches it
> seems quite wasteful. There are much more places where I'd like to use these
> keys ... and I have to reserve it for very special single case.
>
> What about local keymap for normal menu completion (menucomplete?) It looks
> logical - most widgets you'd like to use cannot be used outside of menu
> completion in any case. And binding cup -> menu-complete and cdown ->
> rverse-menu-complete would give you nice way to scroll through matches even
> without menu select.
Problem is that currently local keymaps are realy very very local ;-)
As soon as we fall back into the main key-read-loop, the local keymap
is removed (in fact, widgets installing a local keymap should remove
it).
However, I agree, that it would be nice to (be able to) do more with
local maps. This menu-completion thing is one (small problem: you
don't get any visual feedback when menucompletion is started or
exited). The vared-option I mentioned is another one. And I would also
like to add (initially empty) maps for isearch, execute-named-command
and the other builtin widgets which have their own key-loop.
> Releated question: how useful would local keymaps be for user defined widgets?
> It differs from current 'bindkey -N newkeymap xxx; bindkey -A newkymap main' in
> two aspects:
Only if we add a way to read a key sequence (and get the widget name
as the result). But that may be interesting to have anyway... (so that
you can implement real key-loops in shell code).
> - it is sparse (is it really?) You do not need to define all possible bindings
Yes, really. Look at complist, it defines only a couple of keys.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-06-29 11:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-29 11:15 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-06-29 10:51 Andrej Borsenkow
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=199906291115.NAA17852@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.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).