From: Phil Pennock <comet@fysh.org>
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 19:59:42 +0000 [thread overview]
Message-ID: <19990310195942.A13158@fysh.org> (raw)
In-Reply-To: <19990309225721.D19692@rom.oit.gatech.edu>; from "Will Day" on Tue 9 Mar 1999 (22:57 -0500)
Typing away merrily, Will Day produced the immortal words:
> The signames2.awk script wasn't finding any signals, due to the extra
> space generated by sun's cc -E (solaris 2.6, Sun WorkShop Compiler C
> 4.2), so I added a "*" to match extra spaces.
> --- zsh-3.1.5-pws-11/Src/signames2.awk.orig Tue Feb 9 08:28:41 1999
> +++ zsh-3.1.5-pws-11/Src/signames2.awk Tue Mar 9 19:55:52 1999
> @@ -6,7 +6,7 @@
> # NB: On SunOS 4.1.3 - user-functions don't work properly, also \" problems
> # Without 0 + hacks some nawks compare numbers as strings
> #
> -/^XXNAMES XXSIG[A-Z][A-Z0-9]* [1-9][0-9]*/ {
> +/^XXNAMES XXSIG[A-Z][A-Z0-9]* *[1-9][0-9]*/ {
> sigindex = index($0, "SIG")
> sigtail = substr($0, sigindex, 80)
> split(sigtail, tmp)
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]*/ {
Could the pattern matched theoretically contain horizontal tabs there
too?
--
--> Phil Pennock ; GAT d- s+:+ a23 C++(++++) UL++++/I+++/S+++/B++/H+$ P++@$
L+++ E-@ W(+) N>++ o !K w--- O>+ M V !PS PE Y+ PGP+ t-- 5++ X+ R !tv b++>+++
DI+ D+ G+ e+ h* r y?
next prev parent reply other threads:[~1999-03-10 20:01 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 [this message]
1999-03-10 22:12 ` Will Day
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=19990310195942.A13158@fysh.org \
--to=comet@fysh.org \
--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).