unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sean Devlin <spd@toadstyle.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 60762@debbugs.gnu.org
Subject: bug#60762: 28.2; info--manual-names ignores Info-additional-directory-list
Date: Fri, 13 Jan 2023 12:45:20 -0500	[thread overview]
Message-ID: <9F250ED0-4C93-487D-942A-ADBE2421F56E@toadstyle.org> (raw)
In-Reply-To: <83edrya7y5.fsf@gnu.org>

> On Jan 13, 2023, at 8:18 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> From: Sean Devlin <spd@toadstyle.org>
>> Date: Fri, 13 Jan 2023 07:04:53 -0500
>> Cc: 60762@debbugs.gnu.org
>> 
>>>> The variable Info-additional-directory-list is intended as the main
>>>> Lisp-level customization point for users.
>>> 
>>> That is inaccurate.  The main Lisp-level customization variable for
>>> users is Info-default-directory-list.  So the question I'd like to ask
>>> before discussing the situations you describe is why don't you
>>> customize Info-default-directory-list instead?
>> 
>> The documentation string for Info-default-directory says:
>> 
>> “Although this is a customizable variable, that is mainly for technical
>> reasons.  Normally, you should either set INFOPATH or customize
>> `Info-additional-directory-list', rather than changing this variable.”
> 
> This text is no longer in the doc string in Emacs 29.
> 
>> To me, this suggests that users should prefer
>> Info-additional-directory-list. I guess that will change in Emacs 29,
>> but that is not released yet.
> 
> Yes, the main customization option is Info-default-directory-list.
> 
>> To be clear, I have already worked around this issue in my own
>> configuration.
> 
> Can you tell whether customizing Info-default-directory-list solves
> the problems in your case?  I'd like to know if there's still a
> problem we need to consider for Emacs 29.

In my view, the problem is that the documentation string for
Info-additional-directory-list is not correct. It seems that this
customization option is still supported in the Emacs 29 branch, so I
think it is still a problem regardless of whether this is the
recommended customization option.

That said, I don't think it is an urgent issue.

To answer your question, customizing Info-default-directory-list is
one valid workaround. It does require some care to keep the default
set of directories it generates, but this snippet seems to work:

(custom-set-variables
 '(Info-default-directory-list
   (append Info-default-directory-list
	   '("/path/to/my/info/files/"))))

Thanks.

> 
> Thanks.






  reply	other threads:[~2023-01-13 17:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 23:44 bug#60762: 28.2; info--manual-names ignores Info-additional-directory-list Sean Devlin
2023-01-13  8:15 ` Eli Zaretskii
2023-01-13 12:04   ` Sean Devlin
2023-01-13 13:18     ` Eli Zaretskii
2023-01-13 17:45       ` Sean Devlin [this message]
2023-01-13 18:25         ` Eli Zaretskii

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=9F250ED0-4C93-487D-942A-ADBE2421F56E@toadstyle.org \
    --to=spd@toadstyle.org \
    --cc=60762@debbugs.gnu.org \
    --cc=eliz@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).