From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: PATCH: updated _zstyle and cleanup of related stuff
Date: Mon, 14 Jan 2002 19:03:07 +0000 [thread overview]
Message-ID: <1020114190307.ZM18938@candle.brasslantern.com> (raw)
In-Reply-To: <13601.1011033792@csr.com>
On Jan 14, 6:43pm, Peter Stephenson wrote:
} Subject: Re: PATCH: updated _zstyle and cleanup of related stuff
}
} "Bart Schaefer" wrote:
} > See the thread beginning with zsh-workers/15950.
}
} I think we can do (#q) as proposed there, except as I already said, I'd
} prefer simply to ignore (#q) where it isn't treated as a glob qualifier
Hm. Where, exactly, would it not be treated as one? You mean that, at
least for now, you won't implement my `*(#qG)/*(#q.^G)' example?
} i.e. gets through to the pattern code, since it means you no longer need to
} rewrite glob patterns to test against the filenames, which I consider a
} highly desirable feature.
I'm not sure I follow that.
} Causing an error if the (#q) gets through to the pattern code would be
} fairly simple, however.
In fact, it should be no work at all? At the moment:
schaefer<501> setopt extendedglob
schaefer<502> echo foo(#q)bar
zsh: bad pattern: foo(#q)bar
} The natural rule for bareglobs is that they work if and only if they appear
} at the end, if and only if BAREGLOBQUAL is set, so (.)(#q*) is just one
} qualifier, but (#q*)(.) is two.
I agree.
} The only hairy bit of implementing this is that we'll need an extra level
} of logic to handle the logical and of different qualifiers. As I said, I
} don't think the rule of applying them `as if they appeared in a single
} list' is rational --- treating (#q/,*)(#qW) as (#q/,*W) doesn't seem to
} make sense to me.
I agree with that, too. It should be treated as (#q/W,*W), I think. Just
distribute the ANDs over the ORs when combining them.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2002-01-14 19:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 12:02 Oliver Kiddle
2002-01-10 10:46 ` Sven Wischnowsky
2002-01-14 13:01 ` Oliver Kiddle
2002-01-14 13:57 ` Peter Stephenson
2002-01-14 16:36 ` Bart Schaefer
2002-01-14 17:01 ` Peter Stephenson
2002-01-14 18:06 ` Bart Schaefer
2002-01-14 18:43 ` Peter Stephenson
2002-01-14 19:03 ` Bart Schaefer [this message]
2002-01-14 19:09 ` Peter Stephenson
2002-01-22 12:28 ` PATCH: (#q) Peter Stephenson
2002-01-22 13:50 ` 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=1020114190307.ZM18938@candle.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).