From: Mikael Magnusson <mikachu@gmail.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: completion
Date: Wed, 7 Jan 2015 17:58:39 +0100 [thread overview]
Message-ID: <CAHYJk3QbHjSai-hLzK_uwiYZs+E1BDJk8kfkpr2WgknSsKJwrA@mail.gmail.com> (raw)
In-Reply-To: <20150107152856.0a347dec@pwslap01u.europe.root.pri>
On Wed, Jan 7, 2015 at 4:28 PM, Peter Stephenson
<p.stephenson@samsung.com> wrote:
> On Wed, 7 Jan 2015 16:01:09 +0100
> Vincent Lefevre <vincent@vinc17.net> wrote:
>> On 2014-12-11 11:34:20 -0800, Ray Andrews wrote:
>> > Anyway, knowing that the star replaces the colons cracks it open.
>>
>> This is a bit old, but... When can an asterisk replace a colon?
>
> Colons aren't special to pattern matching at all.
>
>> If an asterisk can match anything, there may be an ambiguity on
>> which field some given word will match.
>
> Yes, they are ambiguous. The examples probably could do with fixing.
>
> With some of the more complicated things you can do, this can actually
> be hard to work around, I seem to remember.
Does [^:]# work in this context?
--
Mikael Magnusson
next prev parent reply other threads:[~2015-01-07 16:58 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 23:15 completion Ray Andrews
2014-12-10 23:31 ` completion Lawrence Velázquez
2014-12-11 0:34 ` completion Oliver Kiddle
2014-12-11 1:17 ` completion Ray Andrews
2014-12-11 5:44 ` completion Bart Schaefer
2014-12-11 16:40 ` completion Ray Andrews
2014-12-11 17:28 ` completion Bart Schaefer
2014-12-11 19:34 ` completion Ray Andrews
2015-01-07 15:01 ` completion Vincent Lefevre
2015-01-07 15:28 ` completion Peter Stephenson
2015-01-07 16:58 ` Mikael Magnusson [this message]
2015-01-07 17:06 ` completion Peter Stephenson
2015-01-07 18:33 ` completion Ray Andrews
[not found] ` <CAH+w=7Z_B2ghc21QgHxA8FEV7W8uQnjEwtPqK3tL-kjPihjicA@mail.gmail.com>
2015-01-07 19:54 ` completion Bart Schaefer
2015-01-07 18:48 ` completion Bart Schaefer
2015-01-07 19:24 ` completion Ray Andrews
2015-01-07 19:33 ` completion Lawrence Velázquez
2015-01-07 20:06 ` completion Ray Andrews
2015-01-07 19:51 ` completion Bart Schaefer
2015-01-07 20:15 ` completion Ray Andrews
2015-01-07 20:42 ` completion Bart Schaefer
2015-01-07 23:00 ` completion Ray Andrews
2015-01-08 5:09 ` completion Bart Schaefer
2015-01-08 8:31 ` completion Bart Schaefer
2015-01-08 16:52 ` completion Ray Andrews
2015-01-08 0:43 ` completion Vincent Lefevre
2015-01-08 0:57 ` completion ZyX
2015-01-08 1:15 ` completion Vincent Lefevre
2015-01-08 6:03 ` completion Bart Schaefer
2015-01-08 5:26 ` completion Bart Schaefer
2015-01-08 12:36 ` completion Vincent Lefevre
2015-01-10 2:12 ` completion Bart Schaefer
2015-01-12 9:09 ` completion Vincent Lefevre
2015-01-12 16:43 ` completion Bart Schaefer
2015-01-13 16:03 ` completion Vincent Lefevre
2015-01-14 2:56 ` completion Bart Schaefer
2015-01-08 17:12 ` completion Ray Andrews
2015-01-09 9:37 ` completion Vincent Lefevre
2015-01-10 5:33 ` completion Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
2012-12-03 17:44 completion Ray Andrews
2012-12-03 18:31 ` completion Ray Andrews
2007-05-15 15:27 Completion Anonymous bin ich
2007-05-15 16:23 ` Completion Peter Stephenson
2006-02-20 12:54 Completion Etienne Chové
2006-02-20 18:51 ` Completion Clint Adams
2006-02-20 19:47 ` Completion Etienne Chové
2003-12-22 23:15 Completion Seth Kurtzberg
2000-02-22 14:58 Completion Sven Wischnowsky
2000-02-22 14:47 Completion Sven Wischnowsky
2000-02-22 15:01 ` Completion Andy Spiegl
2000-02-22 11:36 Completion Sven Wischnowsky
2000-02-22 14:24 ` Completion Andy Spiegl
2000-02-22 18:01 ` Completion Bart Schaefer
2000-02-15 8:42 Completion Claus Alboege
2000-02-21 22:20 ` Completion Bart Schaefer
2000-02-22 10:37 ` Completion Andy Spiegl
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=CAHYJk3QbHjSai-hLzK_uwiYZs+E1BDJk8kfkpr2WgknSsKJwrA@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=p.stephenson@samsung.com \
--cc=zsh-users@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).