From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Cc: k0ga@shike2.com
Subject: Re: [9front] sed: fix moving '^' match
Date: Sat, 26 Aug 2023 18:48:20 +0200 [thread overview]
Message-ID: <CAFSF3XP-CZJP5cFac8o_+g_VVdiMJynqp=GVwc+NHvMVxUKMXQ@mail.gmail.com> (raw)
In-Reply-To: <2NS6A93Q4VONO.2LMPXO8M4I4GW@wilsonb.com>
i disagree, i can interprete sed(1) to allow exactly this feature
On Sat, Aug 26, 2023 at 4:11 PM <ieliedonge@wilsonb.com> wrote:
>
> > you deserve to be surprised. you should be thankful to be surprised.
> > think, before you use g.
>
> Thinking before acting is definitely good.
>
> Current behavior doesn't match what's implied by sed(1) and regexp(6), which
> smells like a bug to me. Fixing bugs is also good.
next prev parent reply other threads:[~2023-08-26 16:57 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 [this message]
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='CAFSF3XP-CZJP5cFac8o_+g_VVdiMJynqp=GVwc+NHvMVxUKMXQ@mail.gmail.com' \
--to=23hiro@gmail.com \
--cc=9front@9front.org \
--cc=k0ga@shike2.com \
/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).