From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] [PATCH 4/6] walk: quote name and path using N and P; use quotefmt and free()
Date: Thu, 28 Sep 2023 12:13:34 -0400 [thread overview]
Message-ID: <7013B5AE5BFE88BDC863FC7B977C8CFC@eigenstate.org> (raw)
In-Reply-To: <7D2134B76398FE01FD5C6C8F5313565F@smtp.pobox.com>
Quoth unobe@cpan.org:
> I had sent an earlier version of this around August 10. Moody helped
> me on gridchat with some finer points, and figured I'd send it out
> again along with the other patches I've been accumulating.
I think the last time this was brought up, I wasn't convinced
of the need for a change here; the motivating example didn't
actualy work. `{} doesn't evaluate quotes.
How do you plan to use this?
next prev parent reply other threads:[~2023-09-28 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 5:15 Romano
2023-09-28 7:02 ` unobe
2023-09-28 16:13 ` ori [this message]
2023-09-28 16:53 ` unobe
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=7013B5AE5BFE88BDC863FC7B977C8CFC@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).