From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] this history(1) is scratched
Date: Sat, 12 Nov 2022 16:26:56 -0500 [thread overview]
Message-ID: <E9692FD03BF9BF57D7AF6C7BA908F641@eigenstate.org> (raw)
In-Reply-To: <20221112213250.747c9574@gmx.de>
Quoth Eckard Brauer <eckard.brauer@gmx.de>:
>
>
> but just noticed that p9 awk doesn't take RS as a regex, as gnu-awk
> does. So i'd maybe translate one of them using tr before (also noticed
> that escape sequences don't work with tr, however, this works somehow),
> e.g.
I think I explained poorly:
The problem is that I want to separate only *some* fields
or records based on the separator.
foo bar baz quux
should have 'bar baz quux' extractable as a single
record.
next prev parent reply other threads:[~2022-11-12 21:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 8:15 qwx
2022-11-12 11:03 ` Eckard Brauer
2022-11-12 12:16 ` Eckard Brauer
2022-11-12 18:07 ` Eckard Brauer
2022-11-12 19:13 ` ori
2022-11-12 20:32 ` Eckard Brauer
2022-11-12 20:44 ` Eckard Brauer
2022-11-12 20:53 ` Eckard Brauer
2022-11-12 21:26 ` ori [this message]
2022-11-12 22:43 ` umbraticus
2022-11-13 3:35 ` Anthony Martin
2022-11-13 23:20 ` qwx
2022-11-15 11:49 ` qwx
2022-11-15 21:59 ` qwx
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=E9692FD03BF9BF57D7AF6C7BA908F641@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).