unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tirifto <tirifto@posteo.cz>
To: help-guix@gnu.org
Subject: Possible sources of environment variables
Date: Fri, 30 Dec 2022 17:12:32 +0000	[thread overview]
Message-ID: <4596407.dJFNsrkgCC@localhost.localdomain> (raw)

Hello! I have a small problem that’s a bit odd, perhaps. I have some 
environment variables defined to include Guix-related paths, but I have no 
idea where they’re being defined.

I was sourcing the ‘~/.guix-profile/etc/profile’ file from my ‘~/.profile’, 
but after I commented that part of my ‘~/.profile’ out, I’m still getting the 
Guix-related paths in $GDK_PIXBUF_MODULE_FILE, $PATH, and $XDG_DATA_DIRS (all 
of which are defined in the Guix profile file), but also in $INFOPATH (which 
is not in the Guix profile file). I don’t remember ever defining these 
variables anywhere; sourcing the Guix profile from my shell profile is all 
that I recall ever doing.

I do define some other Guix-related variables manually, but all of those 
concern locales or certificates for various programs. I wish to undo the other 
paths being set by/for Guix, to make my environment temporarily unaware of 
Guix even being installed, for troubleshooting purposes, but I can’t find out 
how.

I’m running Guix as a supplementary package manager on OpenSUSE 15.4, with KDE 
as my desktop environment. I suppose this might not be Guix at fault, but just 
me overlooking something while setting it up, or the host system doing 
something I’m not familiar with, but perhaps someone has had a similar 
experience? Any clues would be much appreciated!

Best of wishes
// Tirifto




             reply	other threads:[~2023-01-02  7:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30 17:12 Tirifto [this message]
2023-01-02  7:42 ` Possible sources of environment variables Julien Lepiller

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=4596407.dJFNsrkgCC@localhost.localdomain \
    --to=tirifto@posteo.cz \
    --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).