zsh-users
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: "Peter Slížik" <peter.slizik@gmail.com>, zsh <zsh-users@zsh.org>
Subject: Re: A wrong bindkey command breaks the way bck-i-search (Ctrl+R) works
Date: Wed, 28 Jul 2021 00:35:27 +0200	[thread overview]
Message-ID: <CAHYJk3R5ovOG=XQO4VYXsqq5995KiBCaBKN0UHVDaJ-ObNNuqg@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7Y9FG=sZn1+KgdA9=ec7rCZKGEmPQOxcr+bD5JUjAwqiA@mail.gmail.com>

On 7/27/21, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Tue, Jul 27, 2021 at 3:31 AM Peter Slížik <peter.slizik@gmail.com>
> wrote:
>>
>> bindkey -M emacs ' ' expand_abbreviations
>>
>> But alas, this changes the behavior of isearch, too. The documentation is
>> really sometimes too wordy and, in cases like this, too terse.
>
> I think that's because emacs == main and isearch is initialized from
> main ... so if you did that bindkey but only after isearch was
> initialized, it might work.  I don't know how you assure that order of
> events, though.

I think isearch is used as a "local keymap", ie it falls back to main
at runtime if a key is not found in the isearch keymap. Unless you add
bindings to it, it is completely empty.

-- 
Mikael Magnusson


  parent reply	other threads:[~2021-07-27 22:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-26 14:13 Peter Slížik
2021-07-26 15:58 ` Mikael Magnusson
2021-07-26 21:10   ` Bart Schaefer
2021-07-27 10:31     ` Peter Slížik
2021-07-27 14:51       ` Bart Schaefer
2021-07-27 15:09         ` Peter Slížik
2021-07-27 15:42           ` Bart Schaefer
2021-07-27 15:44             ` Peter Slížik
2021-07-27 22:35         ` Mikael Magnusson [this message]
2021-07-27 22:38           ` 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='CAHYJk3R5ovOG=XQO4VYXsqq5995KiBCaBKN0UHVDaJ-ObNNuqg@mail.gmail.com' \
    --to=mikachu@gmail.com \
    --cc=peter.slizik@gmail.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-users@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).