From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-users <zsh-users@sunsite.auc.dk>
Subject: Re: Using buffer for history-incremental-search-backward
Date: Wed, 4 Jul 2001 14:39:07 +0000 [thread overview]
Message-ID: <1010704143907.ZM1306@candle.brasslantern.com> (raw)
In-Reply-To: <20010704061454.6952.qmail@web10401.mail.yahoo.com>
On Jul 3, 11:14pm, Felix Rosencrantz wrote:
}
} I actually thought my h-i-s-b was still in the history
} search, it sort of looked like it from the trace output....
Unfortunately, all it manages to do is abort the search. Really, even
when you name the widget history-incremental-search-backward, it's not
calling your widget after the first time ... it's calling the internal
one, until you break out of repeating the same search and start again.
} Though it would also be useful if there was a parameter that explicitly
} says you are in the mini-buffer (or whatever the mode is).
Unfortunately there really is no mini-buffer. Each of the commands that
uses a "mini-buffer" implements it (and key reading for it) separately.
This could get worked on, though, now that we actually do have multiple
keymaps.
} So is there anyway to history-incremental-search-backward (and related
} commands to show a list of matching commands. Sort of like the w2k "F7"
} key in a cmd.exe window.)
Not without interrupting the search. But one could write a completion
function that would do it; just search the $history hash:
compadd - "$history[(R)$BUFFER]"
or something like that.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-07-04 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-03 7:30 Felix Rosencrantz
2001-07-03 8:34 ` Bart Schaefer
2001-07-04 6:14 ` Felix Rosencrantz
2001-07-04 14:39 ` Bart Schaefer [this message]
2001-07-06 6:32 Felix Rosencrantz
2001-07-06 8:24 ` 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=1010704143907.ZM1306@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-users@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).