From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Re: sed: fix moving '^' match
Date: Sat, 26 Aug 2023 11:14:09 +0200 [thread overview]
Message-ID: <CAFSF3XP1BuT4K5DT+weKpXm9kLdT5t==q+K77i+Yqbh8DQr9FQ@mail.gmail.com> (raw)
In-Reply-To: <ZOlBnqcGtlMRHsRD@alice>
> It looks like a reasonable change but I'd be hesitant to
> make it. Ed(1) produces the same output and the behavior
> appears to be unchanged since at least the 8th edition.
thanks for checking the 8th edition also. i was wondering about this.
> It's clearly a rare edge case and easily avoided by not using
> the g flag when it's not necessary. I doubt it would break
> anything, though.
it's not just that it's not necessary.
in ori's example it's conflicting commands opposing what ori is trying
to achieve.
but he's trying to achieve something that is trivial to achieve in
regular ways without conflicts.
meanwhile now you're trying to ADD CODE to remove a behavior that
needn't HURT any valid usecase.
the following stops working, which is WRONG. i.e. bsd is wrong, and
GNU is wrong. while Plan9 ed and sed is right as usual.
echo abababacab | sed 's/^ab//g'
PLEASE stop with this move fast and break things
next prev parent reply other threads:[~2023-08-26 9:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 21:46 [9front] " ori
2023-08-26 0:04 ` [9front] " Anthony Martin
2023-08-26 9:14 ` hiro [this message]
2023-08-26 17:58 ` ori
2023-08-26 18:02 ` ori
2023-08-26 9:05 ` [9front] " hiro
2023-08-26 9:41 ` ieliedonge
2023-08-26 16:48 ` hiro
2023-08-26 18:00 ` ori
2023-08-26 23:23 ` ieliedonge
2023-08-27 8:33 ` hiro
2023-08-27 9:54 ` tlaronde
2023-08-27 11:19 ` ieliedonge
2023-09-23 1:35 ` ieliedonge
2023-09-23 10:30 ` hiro
2023-09-24 15:35 ` ori
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='CAFSF3XP1BuT4K5DT+weKpXm9kLdT5t==q+K77i+Yqbh8DQr9FQ@mail.gmail.com' \
--to=23hiro@gmail.com \
--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).