From: Mark H Weaver <mhw@netris.org>
To: Zelphir Kaltstahl <zelphirkaltstahl@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: IceCat from Guix all monospaced font – Summary
Date: Sun, 05 May 2019 17:46:07 -0400 [thread overview]
Message-ID: <87zho0shfp.fsf@netris.org> (raw)
In-Reply-To: <09558546-6873-1659-808c-70817d6ce4e3@gmail.com> (Zelphir Kaltstahl's message of "Sun, 5 May 2019 23:29:07 +0200")
Zelphir Kaltstahl <zelphirkaltstahl@gmail.com> writes:
> Ah it could be, that a package changed something in `~/.profile`. I will
> check … No it still looks the same as before.
Guix never modifies your ~/.profile. The relevant file is:
~/.guix-profile/etc/profile, which is generated each time you update
your user profile. On a Guix system, it is sourced from /etc/profile.
On other systems, you should arrange to source that file in your login
shell with GUIX_PROFILE set appropriately, e.g. with the following code
in your ~/.bash_profile or equivalent:
GUIX_PROFILE="$HOME/.guix-profile" ; \
source "$HOME/.guix-profile/etc/profile"
This is recommended in section 4.2 of the Guix manual, here:
https://www.gnu.org/software/guix/manual/en/html_node/Invoking-guix-package.html
> Also I think any installation adding something to my `~/.profile`
> should tell the user about such a change.
Again, Guix will never do this. However, 'guix package' should tell you
if you're missing environment variable settings that are needed by the
newly installed packages.
> No package I installed yesterday did so.
Hmm. Are you confident about this? If so, that casts doubt on my
hypothesis that this was about missing environment variable settings.
Unfortunately, I currently have no other hypothesis to explain why a
reboot was required to fix your IceCat.
Mark
next prev parent reply other threads:[~2019-05-05 21:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 12:25 IceCat from Guix all monospaced font – Summary HWRoitzsch
2019-05-05 16:15 ` Tanguy Le Carrour
2019-05-05 16:33 ` Tobias Geerinckx-Rice
2019-05-05 17:43 ` Giovanni Biscuolo
2019-05-05 20:21 ` Mark H Weaver
2019-05-05 21:29 ` Zelphir Kaltstahl
2019-05-05 21:46 ` Mark H Weaver [this message]
2019-05-05 23:22 ` Zelphir Kaltstahl
2019-05-05 21:26 ` Zelphir Kaltstahl
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=87zho0shfp.fsf@netris.org \
--to=mhw@netris.org \
--cc=help-guix@gnu.org \
--cc=zelphirkaltstahl@gmail.com \
/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).