From: Anthony Martin <ality@pbrane.org>
To: 9front@9front.org
Subject: [9front] Re: rc: value component separators
Date: Fri, 12 Jul 2024 16:15:23 -0700 [thread overview]
Message-ID: <ZpG5C4eRhkJb8Sz_@alice> (raw)
In-Reply-To: <CBC4B0030D56B5086251AEB5BAF513AA@smtp.pobox.com>
Romano <me+unobe@fallglow.com> once said:
> In the Plan9 rc(1) manual and in p9p's rc(1) manual,
> SOH/ctrl-a/\001 is used to separate component values. In
> the 9front rc(1) manual \000 is used. I briefly grepped
> the git log to see if I could find the commit which explained
> the reason for the change (e.g., 'cd /sys/src/cmd/rc;
> git/log . | grep separator', 'git/log . | grep component')
> but didn't find anything. I also searched the mailing list
> for 'rc SOH'/'rc 000'/'rc separator', but didn't find
> any thread discussing it.
>
> Does anyone remember the reasoning?
It's not a code change in 9front. Only the manual was corrected.
Rc has always used '\0' to separate list values on Plan 9. On Unix,
it uses '\1' because the environment is a pointer to an array of
NUL-terminated strings.
Cheers,
Anthony
next prev parent reply other threads:[~2024-07-12 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 21:58 [9front] " Romano
2024-07-12 23:15 ` Anthony Martin [this message]
2024-07-13 6:04 ` [9front] " Romano
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=ZpG5C4eRhkJb8Sz_@alice \
--to=ality@pbrane.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).