From: binary cat <dogedoge61@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Shared env in child scripts
Date: Mon, 31 May 2021 14:23:46 -0400 [thread overview]
Message-ID: <CAHtSCH+TsKE80OU1Wz+WC738n0tAPo-z-L0iPDLUtSmqayvVeg@mail.gmail.com> (raw)
In-Reply-To: <14875E53238A4C869B47B23B95272195@gmail.com>
> I understand that it allows a child script to change env
> values for its parent, but is that desirable?
It doesn't even do that well.
Environment variables are cached in rc, and this cache is never updated.
I think a good change would be that, by default,
rc performs `rfork(RFENVG);` at startup, then continues as it does now.
Then, there would be a flag that skips this rfork, and also disables caching
of environment variables.
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
2021-05-31 18:23 ` binary cat [this message]
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=CAHtSCH+TsKE80OU1Wz+WC738n0tAPo-z-L0iPDLUtSmqayvVeg@mail.gmail.com \
--to=dogedoge61@gmail.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).