unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: josh.randall@genomicsplc.com
To: jcrandall@alum.mit.edu, 35004@debbugs.gnu.org
Subject: [bug#35004] [PATCH] DRY manual reference to HOME/.guix-profile
Date: Tue, 26 Mar 2019 16:31:29 +0000	[thread overview]
Message-ID: <20190326163129.32264-1-josh.randall@genomicsplc.com> (raw)
In-Reply-To: <CAFBLGSPVJWTyCqpoq1REM827VXJHTeZVwC2tvfP+vY8QZBO_Gg@mail.gmail.com>

From: "Joshua C. Randall" <jcrandall@alum.mit.edu>

---
 doc/guix.de.texi | 2 +-
 doc/guix.fr.texi | 2 +-
 doc/guix.texi    | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/guix.de.texi b/doc/guix.de.texi
index 83dae0d3ec..faa9880fe6 100644
--- a/doc/guix.de.texi
+++ b/doc/guix.de.texi
@@ -2775,7 +2775,7 @@ definiert werden:
 
 @example
 GUIX_PROFILE="$HOME/.guix-profile" ; \
-source "$HOME/.guix-profile/etc/profile"
+source "$GUIX_PROFILE/etc/profile"
 @end example
 
 Ist Ihr System für mehrere Nutzer eingerichtet, werden Nutzerprofile an
diff --git a/doc/guix.fr.texi b/doc/guix.fr.texi
index 541fd6f0d0..407dd02375 100644
--- a/doc/guix.fr.texi
+++ b/doc/guix.fr.texi
@@ -2714,7 +2714,7 @@ ensuite aient les bonnes définitions des variables d'environnement :
 
 @example
 GUIX_PROFILE="$HOME/.guix-profile" ; \
-source "$HOME/.guix-profile/etc/profile"
+source "$GUIX_PROFILE/etc/profile"
 @end example
 
 Dans un environnement multi-utilisateur, les profils utilisateurs sont
diff --git a/doc/guix.texi b/doc/guix.texi
index 7d80c00530..c4675a5b95 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -2650,7 +2650,7 @@ shells get all the right environment variable definitions:
 
 @example
 GUIX_PROFILE="$HOME/.guix-profile" ; \
-source "$HOME/.guix-profile/etc/profile"
+source "$GUIX_PROFILE/etc/profile"
 @end example
 
 In a multi-user setup, user profiles are stored in a place registered as
-- 
2.19.2


-- 
This email is sent on behalf of Genomics plc, a public limited company 
registered in England and Wales with registered number 8839972, VAT 
registered number 189 2635 65 and registered office at King Charles House, 
Park End Street, Oxford, OX1 1JD, United Kingdom.



The contents of this 
e-mail and any attachments are confidential
 to the intended recipient. If 
you are not the intended recipient please
 do not use or publish its 
contents, contact Genomics plc immediately at info@genomicsplc.com 
<mailto:info@genomicsplc.com> then delete. You may not copy, 
forward, use 
or disclose the contents of this email to anybody else if 
you are not the 
intended recipient. Emails are not secure and may contain viruses.

  reply	other threads:[~2019-03-26 22:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-26 15:28 [bug#35004] Docs refer to $HOME/.guix-profile instead of $GUIX_PROFILE Joshua Randall
2019-03-26 16:31 ` josh.randall [this message]
2021-01-11 14:21 ` [bug#35004] [PATCH] doc: Fix typo zimoun
2021-01-19 10:57   ` bug#35004: " Mathieu Othacehe

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=20190326163129.32264-1-josh.randall@genomicsplc.com \
    --to=josh.randall@genomicsplc.com \
    --cc=35004@debbugs.gnu.org \
    --cc=jcrandall@alum.mit.edu \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).