From: Ethan Gardener <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] bug in sed
Date: Fri, 11 Jan 2019 10:55:16 +0000 [thread overview]
Message-ID: <1547204116.2619408.1631744520.03A21CEC@webmail.messagingengine.com> (raw)
In-Reply-To: <b294b71c-3ebc-efa4-1d05-80dc1e798aa3@gmail.com>
tried with same test text: 0, 3, 5, 0 initial spaces on consecutive lines. double-match found in 9front (updated yesterday), and p9p (master branch downloaded last week). also found in acme-sac 0.13 & 9pm because it's an easy test and i'm feeling energetic.
double-match not found with gnu sed 4.4.
while the test case itself is pointless, it could occur as part of a more complex regex where the g is reasonable. i haven't tested this, but i believe it could, for example, trip up the following expression changing all function names beginning with str; it would mess up strstr if strstr occurred at the beginning of a line.
s/(^|[^a-z_A-Z]+)str//g
next prev parent reply other threads:[~2019-01-11 10:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 5:07 Sean Hinchee
2019-01-11 8:42 ` 有澤健治
2019-01-11 10:20 ` hiro
2019-01-11 10:22 ` hiro
2019-01-11 10:28 ` hiro
2019-01-11 10:35 ` hiro
2019-01-11 13:04 ` 有澤健治
2019-01-11 10:32 ` 有澤健治
2019-01-11 17:49 ` Sean Hinchee
2019-01-11 19:03 ` hiro
2019-01-11 10:55 ` Ethan Gardener [this message]
2019-01-11 11:19 ` hiro
2019-01-11 11:21 ` hiro
2019-01-11 12:39 ` hiro
2019-01-11 13:10 ` Nick Owens
2019-01-11 15:01 ` Stanley Lieber
2019-01-11 15:19 ` Eckard Brauer
2019-01-11 18:30 ` Ethan Gardener
2019-01-11 19:01 ` hiro
2019-01-11 21:11 ` Xiao-Yong Jin
2019-01-11 23:06 umbraticus
2019-01-11 23:29 ` hiro
2019-01-11 23:46 umbraticus
2019-01-11 23:45 ` Kurt H Maier
2019-01-11 23:52 ` Eckard Brauer
2019-01-11 23:49 umbraticus
2019-01-12 0:52 umbraticus
2019-01-12 0:58 ` Kurt H Maier
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=1547204116.2619408.1631744520.03A21CEC@webmail.messagingengine.com \
--to=eekee57@fastmail.fm \
--cc=9front@9front.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.
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).