From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] sed: fix moving '^' match
Date: Sun, 24 Sep 2023 11:35:58 -0400 [thread overview]
Message-ID: <2E181B2094584DF177A684650BA401D6@eigenstate.org> (raw)
In-Reply-To: <3FKR5VP2SJO53.2A3DBPURZ63YT@wilsonb.com>
Quoth ieliedonge@wilsonb.com:
> Any update on this?
>
> I believe we confirmed that the patch brings us back into line with V7 and V8,
> not to mention every other regex library in common usage. IMHO, merging makes
> eminent sense.
I'd probably prefer to do a new revision without the hack; generating into
an output buffer would fix the bug, but would also improve performance on
long lines and make the code easier to read (at the cost of some increased
memory use).
Either way, it's not urgent.
prev parent reply other threads:[~2023-09-24 15:42 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
2023-09-24 15:35 ` ori [this message]
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=2E181B2094584DF177A684650BA401D6@eigenstate.org \
--to=ori@eigenstate.org \
--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).