From: Bill Pemberton <wfp5p@cthulhu.itc.virginia.edu>
To: zsh-users@sunsite.auc.dk
Subject: Wildcard completion question
Date: Tue, 27 Nov 2001 15:21:04 -0500 (EST) [thread overview]
Message-ID: <200111272021.fARKL4E23188@cthulhu.itc.Virginia.EDU> (raw)
I have a hopefully simple completion problem with version 4. Really
it's just a difference from 3 to 4, but I haven't been able to make 4
behave the way I want. With version 3 (3.0.8, for example, I know
works this way) I can do something like this:
cd /lv*/bla<TAB>
And have it do completions based on that. It'll even deal with
something like there being a /lv1/blah and an /lv9/blah2 by cycling
through both.
But I just haven't been able to figure out how to make version 4 work
the same way.
--
Bill
next reply other threads:[~2001-11-27 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 20:21 Bill Pemberton [this message]
2001-12-06 16:13 ` Oliver Kiddle
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=200111272021.fARKL4E23188@cthulhu.itc.Virginia.EDU \
--to=wfp5p@cthulhu.itc.virginia.edu \
--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).