From: Harm te Hennepe <dhtehennepe@gmail.com>
To: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: history-incremental-search-backward string argument regression
Date: Sun, 10 Dec 2017 23:46:27 +0000 [thread overview]
Message-ID: <CAMxkEGJkOZvOO_UatK33MLooJyNc9CTLnYK9ba2nxWj+QrpkqA@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7bFey5U3UP8=MOB87Y25U1q1aaAn5y92A41=RPbSnOvrA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
Thanks for your check. Somehow I completely forgot to run the code with
'zsh -f' :-( Seems that some other code in my .zshrc is interfering. I'll
figure out what causes this, and let you know if I still believe it
shouldn't happen.
Harm
On Sat, 9 Dec 2017 at 09:10 Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Mon, Dec 4, 2017 at 2:50 PM, Harm te Hennepe <dhtehennepe@gmail.com>
> wrote:
> >
> > I was trying to let ^r prefill the incremental search minibuffer with the
> > current buffer contents.
> >
> > I've created a widget calling this, but the minibuffer stayed empty.
>
> Hmm, this is working for me (zsh-5.4.2-114-g45f3169):
>
> % setopt histnofunctions
> % revsrch() { zle history-incremental-search-backward waggle }
> % zle -N revsrch
> % bindkey '^R' revsrch
> %
> failing bck-i-search: waggle_
>
>
> > I manually type something into the minibuffer, it does the usual search,
> > but when I then press ^r again to find the next result, I get an empty
> > minibuffer again, instead of the next result.
>
> There are a few reasons why repeating the binding might not repeat the
> search when a user-defined widget is involved. Perhaps post your
> function?
>
prev parent reply other threads:[~2017-12-10 23:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 22:50 Harm te Hennepe
2017-12-09 8:10 ` Bart Schaefer
2017-12-10 23:46 ` Harm te Hennepe [this message]
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=CAMxkEGJkOZvOO_UatK33MLooJyNc9CTLnYK9ba2nxWj+QrpkqA@mail.gmail.com \
--to=dhtehennepe@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).