zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] don't treat alone grouping pattern as glob qualifier
Date: Mon, 18 Nov 2013 10:42:49 +0000	[thread overview]
Message-ID: <20131118104249.05348e57@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <131117194226.ZM3733@torch.brasslantern.com>

On Sun, 17 Nov 2013 19:42:26 -0800
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Nov 18,  8:30am, Han Pingtian wrote:
> } Subject: Re: [PATCH] don't treat alone grouping pattern as glob qualifier
> }
> } On Sun, Nov 17, 2013 at 10:40:41AM -0800, Bart Schaefer wrote:
> } > However, I can't immediately think of any reason why a paren should be
> } > considered part of a "trailing set" when nothing precedes it ...
> } 
> } Yes, because there is nothing before (s*), it wouldn't be treated as
> } qualifiers, I think.
> 
> Anybody else going to chime in on this?  Are there other cases where
> the (s == str) test in the patch could be true but the paren really
> should be treated as introducing a qualifier?

Another relevant factor leading me to suppose this is probably OK is
that we don't apply glob qualifiers unless there are files that match,
and a file can't match the empty string.  So for example (in the Src
directory, with NO_NOMATCH, and before the patch although it doesn't
affect this):

% print signames.c(:t)
signames.c
% print signames(:t)
signames(:t)

So I contend there is no case that worked before the patch that fails
afterwards.

pws


  reply	other threads:[~2013-11-18 10:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-17  5:24 Han Pingtian
2013-11-17 18:40 ` Bart Schaefer
2013-11-18  0:30   ` Han Pingtian
2013-11-18  3:42     ` Bart Schaefer
2013-11-18 10:42       ` Peter Stephenson [this message]
2013-11-18 10:31   ` 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=20131118104249.05348e57@pwslap01u.europe.root.pri \
    --to=p.stephenson@samsung.com \
    --cc=zsh-workers@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).