unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Pierre Téchoueyres" <pierre.techoueyres@free.fr>
To: help-gnu-emacs@gnu.org
Subject: Re: What's the right way to define a custom info path.
Date: Wed, 25 Nov 2015 20:54:25 +0100	[thread overview]
Message-ID: <E1a1g96-000844-7C@eggs.gnu.org> (raw)
In-Reply-To: 83wpt6vty5.fsf@gnu.org

First, thanks for the answer.
I note that the recommended way to setup info is to use INFOPATH.
But, just for my knowledge, I would ask you about one or two things below.

Eli Zaretskii wrote:

>> ...
>> ** My questions
>>    Have I do something wrong with my config ? Should I set an INFOPATH
>>    env var with absolutes paths ? If the answer of the previous questions
>>    is : No, should I open bugs ?
> 
> The way to set this up correctly is to define the INFOPATH environment
> variable (outside Emacs) which mentions the directories with Info
> files in the proper order.  The Emacs is supposed to automatically
> pick up the directories from INFOPATH, and you should be able to read
> your manuals without any further problems.
> 
> You are instead trying to futz with Emacs variables that are not
> supposed to do that well.  I suggest to save yourself a lot of trouble
> and go via INFOPATH.
> 
>> ** My questions
>>    Have I do something wrong with my config ? Should I set an INFOPATH
>>    env var with absolutes paths ?
> 
> Yes to INFOPATH.
> 
>>    If the answer of the previous questions is : No, should I open bugs ?
> 
> No, there's no bug here, AFAICT.  If you want to set up
> Info-directory-list or Info-additional-directory-list, you must load
> info.elc first.  (But again, I don't recommend going that way.)

But these two variables could be modified with the custom machinery, and so 
without requiring info[.elc] aren't they ? But I understand your advice that 
doing that is discouraged.

Second, the default value for Info-default-directory-list (as computed by 
the defcustom in info.el) is ("%emacs_dir/info") on my windows install. Is 
this the expected behaviour ? this value is obviously overridden by info-
initialize and become, in my install, ("c:/programmes/emacs/info").
Again is this the expected behaviour ?

Third, in the windows patform (substitute-env-vars "%emacs_dir%") doesn't 
produce "c:/programmes/emacs" as I expected. But (substitute-env-vars 
"$emacs_dir") do the expansion. Is this the expected behaviour ? Is it that 
we should not offer a version that performs primary processing ?

Thanks agin for your answers.



  parent reply	other threads:[~2015-11-25 19:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1139248550.294947690.1448466260727.JavaMail.root@spooler5n-g27.priv.proxad.net>
2015-11-25 15:45 ` What's the right way to define a custom info path pierre.techoueyres
2015-11-25 18:02   ` Eli Zaretskii
2015-11-25 19:54     ` Pierre Téchoueyres
2015-11-25 19:54     ` Pierre Téchoueyres [this message]
2015-11-25 20:24       ` Eli Zaretskii
2015-11-25 22:13         ` Pierre Téchoueyres

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1a1g96-000844-7C@eggs.gnu.org \
    --to=pierre.techoueyres@free.fr \
    --cc=help-gnu-emacs@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).