From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers <zsh-workers@sunsite.dk>
Subject: Re: #c flag wrong behaviour
Date: Sat, 29 Mar 2008 10:50:37 -0700 [thread overview]
Message-ID: <080329105037.ZM21861@torch.brasslantern.com> (raw)
In-Reply-To: <20080329161300.GA19193@okita>
On Mar 29, 5:18pm, Anthony Charles wrote:
}
} Saito% print *.?(#c1,2)sh
} test.bash
} Saito% print *.?(#c1,)sh
} zsh: no matches found: *.?(#c1,)sh
} Saito% print *.?(#c1,)
} test.bash test.ksh test.zsh
} Saito%
}
} It seems that #c flag is too greedy. Am I wrong?
Those results do appear incorrect to me. Unfortunately I can't tell if
the problem is in the compilation of the pattern, or the execution. I
suspect the compilation because it doesn't parallel ## in the way I'd
expect, but I'm not very familiar with that part of the code.
next prev parent reply other threads:[~2008-03-29 17:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-29 16:18 Anthony Charles
2008-03-29 17:50 ` Bart Schaefer [this message]
2008-03-30 21:10 ` Peter Stephenson
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=080329105037.ZM21861@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--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).