From: Reuben Thomas <rrt@sc3d.org>
To: bug-emacs@gnu.org
Subject: Making it possible to use INFOPATH with Emacs info files
Date: Thu, 1 May 2008 21:26:20 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0805012115440.10349@canta> (raw)
Because I sometimes install programs in my home directory, I use INFOPATH to
specify the system directories plus one in my home directory. However, this
gets me into trouble with Emacs, because it takes my INFOPATH for its
default info directory list:
This variable `Info-default-directory-list' is used as the default
for initializing `Info-directory-list' when Info is started, unless
the environment variable INFOPATH is set.
which means that if I set INFOPATH, then I don't get access to Emacs's own
info files (under /usr/share/info/emacs-22) unless I manually add this path
to Info-directory-list.
With info, this works, because info searches subdirectories of INFOPATH
directories for files. Emacs seems not to.
It seems to me that Emacs's info reader should always behave like that of
the standalone info reader. Hence, Emacs should be made to look in
subdirectories of Info-directory-list for info files.
(There's a separate issue that with the present semantics of INFOPATH it's
impossible for a user simply to extend the system path. I've written to
bug-texinfo@gnu.org about this. One solution would be to allow an empty path
segment to mean "insert system path here" as it does with some other path
variables. But any such solution should be adopted by the standalone info
reader first, I think, to give Emacs a behaviour to follow, rather than the
other way around.)
(This bug came up in Debian bug
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=446376
)
--
http://rrt.sc3d.org/ | poetry, n. platitude made obscure
next reply other threads:[~2008-05-01 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 20:26 Reuben Thomas [this message]
2008-05-02 7:08 ` Making it possible to use INFOPATH with Emacs info files Glenn Morris
2008-05-02 12:02 ` Reuben Thomas
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=alpine.DEB.1.00.0805012115440.10349@canta \
--to=rrt@sc3d.org \
--cc=bug-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.
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).