unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Jonas Bernoulli <jonas@bernoul.li>
To: 41666@debbugs.gnu.org
Subject: bug#41666: $INFOPATH should end with a colon
Date: Tue, 02 Jun 2020 19:44:17 +0200	[thread overview]
Message-ID: <87eeqxxszy.fsf@bernoul.li> (raw)

On a foreign distro Guix installs /etc/profile.d/guix.sh, which among
other things adds the directory where it installs info pages to the
INFOPATH variable.

It takes care to not accidentally cause the value to end with a colon.
Unfortunately it should do the opposite because a trailing colon means
"... and also the default locations", which is highly desirable.

This is documented in (info "(texinfo)Other Info Directories"):

>    However you set 'INFOPATH', if its last character is a colon (on
> MS-DOS/MS-Windows systems, use a semicolon instead), this is replaced by
> the default (compiled-in) path.  This gives you a way to augment the
> default path with new directories without having to list all the
> standard places.  For example (using 'sh' syntax):
>
>      INFOPATH=/home/bob/info:
>      export INFOPATH
>
> will search '/home/bob/info' first, then the standard directories.
> Leading or doubled colons are not treated specially.

I recommend you just make this simple change:

-  export INFOPATH="$_GUIX_PROFILE/share/info${INFOPATH:+:}$INFOPATH"
+  export INFOPATH="$_GUIX_PROFILE/share/info$:$INFOPATH"

If INFOPATH is already set and does not end with a colon, then that
should be left as-is; it might be intentional.




             reply	other threads:[~2020-06-02 17:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02 17:44 Jonas Bernoulli [this message]
2020-06-02 18:15 ` bug#41666: $INFOPATH should end with a colon Tobias Geerinckx-Rice via Bug reports for GNU Guix

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=87eeqxxszy.fsf@bernoul.li \
    --to=jonas@bernoul.li \
    --cc=41666@debbugs.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.
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).