From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: swedebugia <swedebugia@riseup.net>
Cc: 36311@debbugs.gnu.org
Subject: [bug#36311] doc: Add subsection and note about environment variables.
Date: Mon, 15 Jul 2019 13:32:09 +0200 [thread overview]
Message-ID: <87wogjmt3a.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <46ddf909-ff9f-4d40-b229-e594bf06eeaf@riseup.net> (swedebugia@riseup.net's message of "Mon, 15 Jul 2019 13:01:56 +0200")
Hello,
swedebugia <swedebugia@riseup.net> writes:
>> +Following the installation we recommend putting all environment variables into
>> + @file{~.bash_profile} to make sure they are only executed when your login to
>> + a shell (ie. open up a virtual terminal).
I think @file{~/.bash_profile} is clearer.
Also "ie. open up…" -> "i.e., open up…" or "i.e.@: open up…"
>> +If you use bash and put them into @file{.bashrc} you will end up with errors
>> +because this file is executed by bash EVERY time a new environment is entered
Maybe @emph{every}, since emphasizing with capitals is typographically
suboptimal.
>> +(e.g. when entering a pure environment with @command{guix environment guix
>> +--pure} and contaminate the environment).
"e.g. when" -> "e.g., when" or "e.g.@: when".
See (info "Not Ending a Sentence") for more information.
Also, according to (info "@command"), it shoud be either @samp or @code.
After a cursory look, "guix.texi" seems to use "@code" for entire shell
command invocations.
HTH,
--
Nicolas Goaziou
next prev parent reply other threads:[~2019-07-15 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 16:13 [bug#36311] doc: Add subsection and note about environment variables swedebugia
2019-07-15 11:01 ` swedebugia
2019-07-15 11:32 ` Nicolas Goaziou [this message]
2019-07-15 14:22 ` Nicolas Goaziou
2023-09-02 3:02 ` Maxim Cournoyer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wogjmt3a.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=36311@debbugs.gnu.org \
--cc=swedebugia@riseup.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.