From: raingloom <raingloom@riseup.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: Black magic to pass around environment variables?
Date: Sun, 14 Mar 2021 00:49:35 +0100 [thread overview]
Message-ID: <20210314004935.55ebca24@riseup.net> (raw)
In-Reply-To: <87lfaro23b.fsf@elephly.net>
On Sat, 13 Mar 2021 10:05:44 +0100
Ricardo Wurmus <rekado@elephly.net> wrote:
> raingloom <raingloom@riseup.net> writes:
>
> > Motivation:
> > xfce4-terminal runs as a terminal and doesn't propagate environment
> > variables, which makes it a bit cumbersome to use it with complex
> > `guix environment` setups. While an upstream fix would be nice,
> > this is a general problem and one that shouldn't require special
> > handling in every application.
>
> I’m sorry, I don’t understand the problem. Could you perhaps provide
> an example to illustrate the issue?
Sorry, I wrote that in a rather tired state. What I meant to write was:
xfce4-terminal runs as a **server** and when it opens a new window,
that inherits its environment from the server, not from the calling
environment.
What I want to do is open a new terminal from a guix environment shell
that has the exact same environment variables.
> What environment variables should be propagated from where to where?
All of them, that's the point.
prev parent reply other threads:[~2021-03-14 1:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 3:34 Black magic to pass around environment variables? raingloom
2021-03-13 9:05 ` Ricardo Wurmus
2021-03-13 23:49 ` raingloom [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210314004935.55ebca24@riseup.net \
--to=raingloom@riseup.net \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).