From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] sed: fix moving '^' match
Date: Sat, 23 Sep 2023 12:30:47 +0200 [thread overview]
Message-ID: <CAFSF3XMqix3ECr1j5uXefpdxotvFrid5jOX-qTNtPC_Mw11i8Q@mail.gmail.com> (raw)
In-Reply-To: <3FKR5VP2SJO53.2A3DBPURZ63YT@wilsonb.com>
> I believe we confirmed that the patch brings us back into line with V7 and
> V8,
did we? either way, there's no value in that.
> not to mention every other regex library in common usage.
there's even less value in that.
> IMHO, merging
> makes
> eminent sense.
explain why it's eminent please.
>
> Maybe the documentation for ^ should also be updated? I completely agree
> that
> hiro's interpretation is a valid reading.
>
some rhetorical questions (sad that i have to put a disclaimer about it):
1) will any of these changes increase real-world compatibility? can
you link to the code that would become executable on plan9 as a
result?
2) if not, will this improve any other real world program running on plan9?
3) if 1) or 2) is true, what is the cost of this change?
1)
no
2)
no
3)
it's a non-zero cost
and the benefit: zero.
next prev parent reply other threads:[~2023-09-23 10:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 21:46 ori
2023-08-26 0:04 ` [9front] " Anthony Martin
2023-08-26 9:14 ` hiro
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 [this message]
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=CAFSF3XMqix3ECr1j5uXefpdxotvFrid5jOX-qTNtPC_Mw11i8Q@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).