From: Felix Mueller <felix@enqueue.eu>
To: emacs-devel@gnu.org
Subject: Re: NS do not set INFOPATH
Date: Sat, 16 May 2009 13:06:02 +0200 [thread overview]
Message-ID: <m2pre9e291.fsf@enqueue.eu> (raw)
In-Reply-To: <loom.20090516T050236-566@post.gmane.org> (Adrian Robert's message of "Sat, 16 May 2009 05:08:45 +0000 (UTC)")
Hi,
* Adrian Robert -- [2009-05-16] writes:
> Felix Mueller <felix <at> enqueue.eu> writes:
>> I would find it less intrusive, if Emacs.app did not set INFOPATH upon
>> start up if it was not set before. This would enable users to make
>> changes to Info-default-directory-list in their initialization
>> files.
>
> Thanks for this patch. It looks like it improves the behavior from
> before, even if it's not perfect. I will look at incorporating it.
I think, setting an environment variable on startup is not a good idea,
but an easier alternative would be to simply add a colon to resourcePath
in nsterm.m (~ line 418). This way, contents of INFOPATH and
Info-default-directory-list are merged when invoking info.
>> It might be prudent to change that if Emacs is built non
>> self-contained.
>
> Does the new method cause a failure to find the right info directory in
> this case?
I only tested it using the default prefix (/usr/local). This works fine.
>> If you decide against changing the behavior, I would find it helpful
>> if you included a hint in the documentation.
>
> Do I take it the macos.texi portion of your patch should ONLY be applied
> if the other parts are NOT applied
Yes.
* Leo -- [2009-05-16] writes:
> Actually from the documentation, it looks like
> Info-default-directory-list is not for users to customise,
> Info-additional-directory-list is.
OK, but would you not find it more useful if this variable /could/ be
changed to effectively add info directories (e.g. in the system wide
initialization file to include fink info directories)?
I would typically not expect most of the programs I use to set an
environment variable by themselves, and I spent a couple of minutes
figuring out what was happening and checking for other places that might
be responsible for the INFOPATH environment variable. That's why I wrote
the email :-)
Thanks!
--
Felix Mueller
felix@enqueue.eu
next prev parent reply other threads:[~2009-05-16 11:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 13:47 NS do not set INFOPATH Felix Mueller
2009-05-16 5:08 ` Adrian Robert
2009-05-16 8:15 ` Leo
2009-05-16 11:06 ` Felix Mueller [this message]
2009-05-16 23:26 ` Adrian Robert
2009-05-31 8:49 ` Felix Mueller
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=m2pre9e291.fsf@enqueue.eu \
--to=felix@enqueue.eu \
--cc=emacs-devel@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/emacs.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).