From: Mikael Magnusson <mikachu@gmail.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: $KEYMAP in command, isearch and menuselect
Date: Mon, 23 Aug 2010 12:08:03 +0200 [thread overview]
Message-ID: <AANLkTinisz1UJTPyXY7neiw_0KMmTdETnQhAcfMkwvH9@mail.gmail.com> (raw)
In-Reply-To: <20100823110127.7566d360@csr.com>
On 23 August 2010 12:01, Peter Stephenson <Peter.Stephenson@csr.com> wrote:
> On Mon, 23 Aug 2010 10:36:38 +0100
> Peter Stephenson <Peter.Stephenson@csr.com> wrote:
>> Basically, the only thing you can do
>> is bind one of the names listed in the documentation to a different
>> key. The documentation should probably be clearer the behaviour isn't
>> extensible. Internally, this is because those modes are each
>> implemented within a single function, not by looking up function
>> behaviour like standard editing behaviour.
>
> (Moved to zsh-workers.)
>
> This might clear up the documentation a bit. isearch already has a note
> about limitations thought it doesn't explicitly say you can't extend the
> list of commands.
>
> I'm now scratching my head over this in the isearch doc:
>
> Any multi-character string that is not bound to one of the above
> functions will beep and interrupt the search, leaving the last found
> line in the buffer. Any single character that is not bound to one of
> the above functions, or tt(self-insert) or tt(self-insert-unmeta),
> will have the same effect but the function will be executed.
fwiw, git blame says this paragraph comes from the "Initial revision"
commit from 1999.
--
Mikael Magnusson
next prev parent reply other threads:[~2010-08-23 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <op.vg6lcz2hvocxtk@tabole>
[not found] ` <20100823103638.2fb7e695@csr.com>
2010-08-23 10:01 ` Peter Stephenson
2010-08-23 10:08 ` Mikael Magnusson [this message]
2010-08-23 13:43 ` Bart Schaefer
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=AANLkTinisz1UJTPyXY7neiw_0KMmTdETnQhAcfMkwvH9@mail.gmail.com \
--to=mikachu@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).