unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: 60032@debbugs.gnu.org
Subject: bug#60032: 30.0.50; [WISH] Customizing Info directories
Date: Tue, 13 Dec 2022 13:19:37 +0000	[thread overview]
Message-ID: <87zgbrbfva.fsf@localhost> (raw)

Hi,

I find the current customization of Info search path slightly awkward.

Emacs Info info page suggests to set INFOPATH environment variable.
Yet, it is not something I feel comfortable doing (it is outside the
nice warm Elisp VM).

There is also `Info-default-directory-list', but it only works for
special non-default value of INFOPATH.

Currently, the only way I found to force adding directories as Info
sources is the following:

(require 'info)
(info-initialize)
(add-to-list 'Info-directory-list "~/Git/org-mode/doc/")

which is awkward.

Would it be possible to introduce something like
`Info-overriding-directory-list' to be added in front of Info path in
Emacs? This will complement `Info-additional-directory-list'.

In GNU Emacs 30.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version
 3.24.35, cairo version 1.17.6) of 2022-12-07 built on localhost
Repository revision: f0e118d3f676afe39df29663399d4bbe8f53f208
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12101004
System Description: Gentoo Linux

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>





             reply	other threads:[~2022-12-13 13:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 13:19 Ihor Radchenko [this message]
2022-12-13 13:31 ` bug#60032: 30.0.50; [WISH] Customizing Info directories Eli Zaretskii
2022-12-13 13:43   ` Ihor Radchenko
2022-12-13 14:39     ` Eli Zaretskii
2022-12-14 10:27       ` Ihor Radchenko
2022-12-17 12:55         ` Eli Zaretskii
2022-12-15  0:23 ` Michael Heerdegen

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=87zgbrbfva.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=60032@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/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).