From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Cc: k0ga@shike2.com
Subject: Re: [9front] sed: fix moving '^' match
Date: Sun, 27 Aug 2023 10:33:50 +0200 [thread overview]
Message-ID: <CAFSF3XO3+m3etPH1G+Cw97Qw+1+eSZbuu9Y3stcUGydWHuptrQ@mail.gmail.com> (raw)
In-Reply-To: <3OWTA7C36ZVYA.3C6IMNK32OWEU@wilsonb.com>
> You are way more creative than most then.
no. this is about parsing the man page carefully.
>I tend to think that lines only have
> a single beginning and that `echo "blah"` writes a single line.
i wouldn't disagree at all.
we must be disagreeing about some fundamental understanding instead.
it's hard for me to see still where *exactly* we differ.
just to make sure. you are aware of the other basic symmetrically
asymmetric problems that one encounters in everyday life with sed,
right? the asymmetry between input and output...
cpu% echo aa | sed 's/aa/a/g'
a
cpu% echo aaaa | sed 's/aa/a/g'
aa
cpu% echo aaaaaa | sed 's/aa/a/g'
aaa
cpu% echo aaaaaaaa | sed 's/aa/a/g'
aaaa
cpu% echo aaaaaaaaaa | sed 's/aa/a/g'
aaaaa
is this a basic known fact here?!
next prev parent reply other threads:[~2023-08-27 8:36 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 [this message]
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=CAFSF3XO3+m3etPH1G+Cw97Qw+1+eSZbuu9Y3stcUGydWHuptrQ@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).