From: umbraticus@prosimetrum.com
To: 9fans@9fans.net
Subject: Re: [9fans] Sam: Is This a Bug?
Date: Fri, 04 Oct 2024 10:55:05 +1300 [thread overview]
Message-ID: <3A0EC63FDF5985E576F1200CAD72C03B@prosimetrum.com> (raw)
In-Reply-To: <17279914340.924A1d.733851@composer.9fans.topicbox.com>
try this and it should make sense:
x/.+\n.*/ x/\n/ d
with .* to the left of the \n you get the following:
match foo\nbar and delete the \n
match \nbaz and delete the \n
match \nqux and delete the \n
match \nquux and delete the \n
match \n and delete it
umbraticus
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tabb641f45805a1fc-M08971bc7fde7e72e022b08e3
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2024-10-03 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 21:37 kalterdev
2024-10-03 21:55 ` umbraticus [this message]
2024-10-03 22:01 ` kalterdev
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=3A0EC63FDF5985E576F1200CAD72C03B@prosimetrum.com \
--to=umbraticus@prosimetrum.com \
--cc=9fans@9fans.net \
/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).