From: Will Day <willday@rom.oit.gatech.edu>
To: zsh workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: Re: PATCH: zsh-3.1.5-pws-11: signames2.awk
Date: Wed, 10 Mar 1999 17:12:47 -0500 [thread overview]
Message-ID: <19990310171247.A21112@rom.oit.gatech.edu> (raw)
In-Reply-To: <19990310195942.A13158@fysh.org>; from Phil Pennock on Wed, Mar 10, 1999 at 07:59:42PM +0000
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
A short time ago, at a computer terminal far, far away, Phil Pennock wrote:
>> -/^XXNAMES XXSIG[A-Z][A-Z0-9]* [1-9][0-9]*/ {
>> +/^XXNAMES XXSIG[A-Z][A-Z0-9]* *[1-9][0-9]*/ {
>
>Is that 'correct'? Shouldn't it be " *" rather than " *" to force at
>least one space?
>
>Thus:
>/^XXNAMES XXSIG[A-Z][A-Z0-9]* *[1-9][0-9]*/ {
Hmm, yeah, that's really what you want.
>Could the pattern matched theoretically contain horizontal tabs there
>too?
I've no idea what kind of output different variants of cpp produce, or
what's considered correct, but it probably wouldn't be a bad idea to
match one or more tabs/spaces. Perhaps:
/XXNAMES XXSIG[A-Z][A-Z0-9]*[ \t]+[1-9][0-9]*/
--
Will Day <PGP mail preferred> OIT / O&E / Technical Support
willday@rom.oit.gatech.edu Georgia Tech, Atlanta 30332-0715
-> Opinions expressed are mine alone and do not reflect OIT policy <-
Those who would give up essential Liberty, to purchase a little temporary
Safety, deserve neither Liberty nor Safety.
Benjamin Franklin, Pennsylvania Assembly, Nov. 11, 1755
[-- Attachment #2: Type: application/pgp-signature, Size: 344 bytes --]
next prev parent reply other threads:[~1999-03-10 22:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-10 3:57 Will Day
1999-03-10 19:59 ` Phil Pennock
1999-03-10 22:12 ` Will Day [this message]
1999-03-10 22:26 ` Phil Pennock
1999-03-10 22:58 ` Will Day
1999-03-10 23:05 ` Phil Pennock
1999-03-11 0:08 ` PATCH: " Will Day
1999-03-11 8: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=19990310171247.A21112@rom.oit.gatech.edu \
--to=willday@rom.oit.gatech.edu \
--cc=zsh-workers@sunsite.auc.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).