From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <9front-bounces@9front.inri.net>
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED,
	HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI autolearn=ham
	autolearn_force=no version=3.4.4
Received: from 9front.inri.net (9front.inri.net [168.235.81.73])
	by inbox.vuxu.org (Postfix) with ESMTP id 058CE28E7C
	for <ml@inbox.vuxu.org>; Sat, 13 Jul 2024 01:18:31 +0200 (CEST)
Received: from sendmail.purelymail.com ([34.202.193.197]) by 9front; Fri Jul 12 19:15:31 -0400 2024
DKIM-Signature: a=rsa-sha256; b=VjGRL7qtsE5SMlrbSu43Kx3xgvTXp4iAfMCH74A9uC+1hLXA5CC9D2X6Wib/pej89g1i1nphD1ZNy5eG61d7j0pFx4eFxHum7zROQraOAEYTiEYoaJD7JMzOzc4GBGoGDW6JpFw2xOEqvWwX10+zm2wyCJq6O33avDBiusTvMePy8hOs67Bv0SyUEVwvKBG1jrXDs8yjP1BsncIXmyeomys9EeA3AbWoKmOvYGO2y+z63wWt1N+NtdflkCA4AndlTIRnFVPcinTM+JSGmpGoCgn77pijRqIT2Ss02soleMEcq44ui+S2+loMHiJE7wGOZcXl4xk/v4uxhFoWL06JSQ==; s=purelymail2; d=pbrane.org; v=1; bh=VKYi+5t5DkWRb7fWk7TEgTDzqXTib/y3ygqvNwYxjXQ=; h=Received:Date:From:To:Subject;
DKIM-Signature: a=rsa-sha256; b=gDvWOQIiY9ldTGPGSj+n61t5tlCdaazV1LAiT4uc+onyuZad0OGa0UnTmGN2Nhbg9qtlowRfPUMVSHq25ThJLpufpdi2RuyLwhJsHJLyL9WEyOEro9+VT9eSKrN3weZS5j+q4uMxbeDAURIZRszwfmVs0izYEF9SD/4SuAlRYWIAZJsxhHh/T4r4Tt+XT+hLvdEpG9JdE2UMyQdjFtEZW4ksR+fLrQLNc3czY01CHOCOmzWZXC2bapIA1zqIRBxUP6ZKSqDigRW53lHCveeIf9JUJ+8lK5Tw6bbLlxlQvRJbE46GpraGTr0q1qoAJ/vJZxhCHauxDa5HFyrWZtpBrg==; s=purelymail2; d=purelymail.com; v=1; bh=VKYi+5t5DkWRb7fWk7TEgTDzqXTib/y3ygqvNwYxjXQ=; h=Feedback-ID:Received:Date:From:To:Subject;
Feedback-ID: 10987:2443:null:purelymail
X-Pm-Original-To: 9front@9front.org
Received: by smtp.purelymail.com (Purelymail SMTP) with ESMTPSA id -1252752242
          for <9front@9front.org>
          (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384);
          Fri, 12 Jul 2024 23:15:30 +0000 (UTC)
Date: Fri, 12 Jul 2024 16:15:23 -0700
From: Anthony Martin <ality@pbrane.org>
To: 9front@9front.org
Message-ID: <ZpG5C4eRhkJb8Sz_@alice>
References: <CBC4B0030D56B5086251AEB5BAF513AA@smtp.pobox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CBC4B0030D56B5086251AEB5BAF513AA@smtp.pobox.com>
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: optimized rails engine 
Subject: [9front] Re: rc: value component separators
Reply-To: 9front@9front.org
Precedence: bulk

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