From: umbraticus@prosimetrum.com
To: 9front@9front.org
Subject: Re: [9front] plumbing with spaces
Date: Thu, 07 Nov 2024 21:46:41 +1300 [thread overview]
Message-ID: <8DF479DCD404E657DA8A64B2232A9BF7@prosimetrum.com> (raw)
In-Reply-To: <CAFSF3XNvnQ5_QOS_mb4V90hnUXH-Y2pMM7m9zDOnD83iC6fLKg@mail.gmail.com>
> "sadly the newline messes things up"
> which step actually messes it up? i realize only now that i never
> understood how this works.
Same. Thinking about it a bit, I'd say it probably has to do with
the regexps used in plumb rules: \n does not match a newline,
nor can you embed a literal one due to how the rules file is parsed.
e.g. sam & sed both mention something along these lines in their
respective manpages; here's sam(1):
Regular expressions are as in regexp(6) with the addition of
\n to represent newlines.
So to allow newlines in plumb "matches" rules those programs could
be a place to look. (or else make this a standard feature of regexp??)
umbraticus
next prev parent reply other threads:[~2024-11-07 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 1:15 népéta mew
2024-11-06 4:57 ` umbraticus
2024-11-06 12:40 ` hiro
2024-11-07 8:46 ` umbraticus [this message]
2024-11-07 8:52 ` umbraticus
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=8DF479DCD404E657DA8A64B2232A9BF7@prosimetrum.com \
--to=umbraticus@prosimetrum.com \
--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).