From: "Jorge" <jorge+list@disroot.org>
To: Adonay Felipe Nogueira <adfeno@hyperbola.info>, help-guix@gnu.org
Subject: Re: Best practices for Guix environment variables on foreign distro
Date: Tue, 13 Mar 2018 17:32:07 +0000 [thread overview]
Message-ID: <6f9c5d3dcd94c6207c43c72acb891f1b@disroot.org> (raw)
In-Reply-To: <87efko178r.fsf@hyperbola.info>
March 13, 2018 9:38 AM, "Adonay Felipe Nogueira" <adfeno@hyperbola.info> wrote:
>> 16.04LTS) and it works fine. Sourcing ~/.guix-profile/etc/profile from
>> $HOME/.profile, on the other hand, prevents logins to GNOME or Unity
>> sessions.
>
> I don't know if Unity respects ${XDG_DATA_DIRS}, but I hope so. If it does:
> then perhaps because you have to treat ${XDG_DATA_DIRS} specially, as I
> explained in other posts.
I forgot to mention that I run Ubuntu GNOME.
When I arrive home (I am at work) I will look at the suggestions in
this thread.
Thank you in advance.
- 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?]]
next prev parent reply other threads:[~2018-03-13 17: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 [this message]
2018-03-14 11:54 ` Adonay Felipe Nogueira
2018-03-12 22:32 ` Jorge
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=6f9c5d3dcd94c6207c43c72acb891f1b@disroot.org \
--to=jorge+list@disroot.org \
--cc=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).