From: Antons Suspans <antox@ml.lv>
To: 9front@9front.org
Subject: Re: [9front] sed bug?
Date: Tue, 13 Nov 2018 22:43:54 +0200 [thread overview]
Message-ID: <20181113204354.GA25631@ax.s16> (raw)
In-Reply-To: <20181113212806.523d19f7@gmx.de>
On Tue, Nov 13, 2018 at 09:28:06PM +0100, Eckard Brauer wrote:
> BTW, GNU sed (Linux) seems to behave similar.
The man page of GNU sed describes this behavior explicitly:
"if addr2 is a regexp, it will not be tested against the line that addr1 matched"
(Man pages of Plan 9 are typically less tormenting.)
next prev parent reply other threads:[~2018-11-13 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 19:32 umbraticus
2018-11-13 20:04 ` Joe M
2018-11-13 20:28 ` Eckard Brauer
2018-11-13 20:32 ` Dave MacFarlane
2018-11-13 20:55 ` Eckard Brauer
2018-11-13 20:43 ` Antons Suspans [this message]
2018-11-13 21:07 ` Eckard Brauer
2018-11-13 21:09 ` Eckard Brauer
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=20181113204354.GA25631@ax.s16 \
--to=antox@ml.lv \
--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).