From: Adonay Felipe Nogueira <adfeno@hyperbola.info>
To: help-guix@gnu.org
Subject: Re: Best practices for Guix environment variables on foreign distro
Date: Tue, 13 Mar 2018 09:24:43 -0300 [thread overview]
Message-ID: <87ina017uc.fsf@hyperbola.info> (raw)
In-Reply-To: <9ddb4d85bc942b4de03d92b309be3998@disroot.org> (Jorge's message of "Mon, 12 Mar 2018 22:32:02 +0000")
I don't know if this is recommended, but I set all my variables inside
"${HOME}/.profile". Morever, the first thing I do in "${HOME}/.profile"
is to source my user's Guix profile --- `source
"${GUIX_PROFILE}/etc/profile"'.
The caveat is that every time GNU Guix changes my profile generation, I
have to log out and then back in --- no need to reboot --- for the
changes to take effect or for the variables to be re-instated, because
it seems that, after the changes made by GNU Guix, programs "forget"
some variables or other information.
--
- https://libreplanet.org/wiki/User:Adfeno
- Palestrante e consultor sobre /software/ livre (não confundir com
gratis).
- "WhatsApp"? Ele não é livre. Por favor, veja formas de se comunicar
instantaneamente comigo no endereço abaixo.
- Contato: https://libreplanet.org/wiki/User:Adfeno#vCard
- Arquivos comuns aceitos (apenas sem DRM): Corel Draw, Microsoft
Office, MP3, MP4, WMA, WMV.
- Arquivos comuns aceitos e enviados: CSV, GNU Dia, GNU Emacs Org, GNU
GIMP, Inkscape SVG, JPG, LibreOffice (padrão ODF), OGG, OPUS, PDF
(apenas sem DRM), PNG, TXT, WEBM.
prev parent reply other threads:[~2018-03-13 12:24 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
2018-03-13 12:24 ` Adonay Felipe Nogueira [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=87ina017uc.fsf@hyperbola.info \
--to=adfeno@hyperbola.info \
--cc=help-guix@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).