From: kvik@a-b.xyz
To: 9front@9front.org
Subject: Re: [9front] Shared env in child scripts
Date: Mon, 31 May 2021 16:58:47 +0200 [thread overview]
Message-ID: <CBE3F566501F8C270593D9CC0C85F490@qak> (raw)
In-Reply-To: <14875E53238A4C869B47B23B95272195@gmail.com>
Quoth kjn@9project.net:
> I understand that it allows a child script to change env
> values for its parent, but is that desirable?
That's the idea but it's not how it works in practice due to rc
caching the environments variable as its own variables, writing back the
changes but never reloading after initial load.
If you want two-way communication via environment the procs must make
special arrangements, with env(3) being nothing more than a slightly
convenient (and shitty) ramfs(4).
In any case, making `rfork e` a default now is sure to break a lot of
scripts in horrible ways -- which doesn't seem worth it.
In theory the proposed default makes way more sense.
next prev parent reply other threads:[~2021-06-01 4:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 2:30 kjn
2021-05-31 12:32 ` sirjofri
2021-05-31 14:58 ` kvik [this message]
2021-05-31 18:23 ` binary cat
2021-05-31 22:10 ` Stanley Lieber
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=CBE3F566501F8C270593D9CC0C85F490@qak \
--to=kvik@a-b.xyz \
--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).