From: "Bart Schaefer" <schaefer@brasslantern.com>
To: gak@klanderman.net, zsh-workers@sunsite.dk (Zsh list)
Subject: Re: compctl "-y" argument busted in 4.0.6
Date: Tue, 4 Feb 2003 10:05:53 +0000 [thread overview]
Message-ID: <1030204100553.ZM16338@candle.brasslantern.com> (raw)
In-Reply-To: <15935.4988.372615.650168@phl.itasoftware.com>
On Feb 3, 8:12pm, Greg Klanderman wrote:
}
} % setopt autolist noautomenu nolistbeep listambiguous listtypes
} % compctl -k "(foo bar baz)" -y "(FOO BAR BAZ)" foobar
} % foobar <TAB>
}
} displays no completions at all!
This is fixed in 4.1.0-dev-6. I don't know exactly what fixed it; there
are no obvious patches meant for it, but it must have been something in
one of zsh-workers/17195 or 16483.
next prev parent reply other threads:[~2003-02-04 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 1:12 Greg Klanderman
2003-02-04 10:05 ` Bart Schaefer [this message]
2003-02-05 2:08 ` PATCH: " Greg Klanderman
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=1030204100553.ZM16338@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=gak@klanderman.net \
--cc=zsh-workers@sunsite.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).