From: Felix Rosencrantz <f_rosencrantz@yahoo.com>
To: zsh-users <zsh-users@sunsite.auc.dk>
Subject: Re: Using buffer for history-incremental-search-backward
Date: Thu, 5 Jul 2001 23:32:30 -0700 (PDT) [thread overview]
Message-ID: <20010706063230.6788.qmail@web10402.mail.yahoo.com> (raw)
>} 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.
Maybe I'll play with that a little. Though I was sort of under the
impression that the completion system could only complete a single word
at time, and not sets of words, like a previous command line would be.
I've sort of fancied the idea that zsh might have a completer for sets
of commandline args/flags at once. For example, with the tar command it
would be possible to complete standard sets of flags that I use (e.g.
xzf, czf, xvf, etc.), which is possible since the flags are together as
a single word. But what if I had a command that only has long options
that I wanted to complete all at once as a group ( for example for
GNU tar "--extract --gzip --file archive" , "--create --gzip --file
archive", etc.) Can the completion system handle that?
Thanks very much, Bart, for your help with the h-i-s-b, it works just like I
want.
-JT.
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/
next reply other threads:[~2001-07-06 6:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-06 6:32 Felix Rosencrantz [this message]
2001-07-06 8:24 ` Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
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
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=20010706063230.6788.qmail@web10402.mail.yahoo.com \
--to=f_rosencrantz@yahoo.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).