unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Jorge" <jorge+list@disroot.org>
To: ludo@gnu.org
Cc: help-guix@gnu.org
Subject: Re: Best practices for Guix environment variables on foreign distro
Date: Mon, 12 Mar 2018 22:32:02 +0000	[thread overview]
Message-ID: <9ddb4d85bc942b4de03d92b309be3998@disroot.org> (raw)
In-Reply-To: <873715siwu.fsf@gnu.org>

March 12, 2018 7:18 AM, ludo@gnu.org wrote:

> The suggestion is to source ~/.guix-profile/etc/profile from
> ~/.bash_profile (or similar).
I have just tried your suggestion.  I verified that it does not pollute
GNOME’s environment and it does set up Guix environment variables in
Emacs.  However, it does not set up the Guix environment on
gnome-terminal, as I suspected.  According to Bash’s info manual[1],
interactive non-login Bash shells (such as those spawned by
gnome-terminal) only read `~/.bashrc' or the file specified by the
`--rcfile' option, but *not* (by default) `/.bash_profile'.

Footnotes
─────────

[1] [info:bash#Bash Startup Files]

- I am Brazilian.  I hope my English is correct and I welcome feedback
- Please adopt free formats like PDF, ODF, Org, LaTeX, Opus, WebM and 7z
- Free/libre software for Android: https://f-droid.org/
- [[https://www.gnu.org/philosophy/free-sw.html][What is free software?]]

  parent reply	other threads:[~2018-03-12 22:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-10 22:32 Best practices for Guix environment variables on foreign distro Jorge
2018-03-12 10:11 ` Ludovic Courtès
2018-03-13  6:48   ` Konrad Hinsen
2018-03-13 12:37     ` Adonay Felipe Nogueira
2018-03-13 17:32     ` Jorge
2018-03-14 11:54       ` Adonay Felipe Nogueira
2018-03-12 22:32 ` Jorge [this message]
2018-03-13 12:24   ` Adonay Felipe Nogueira

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=9ddb4d85bc942b4de03d92b309be3998@disroot.org \
    --to=jorge+list@disroot.org \
    --cc=help-guix@gnu.org \
    --cc=ludo@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).