From: "T.V Raman" <raman@google.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: package-quickstart and info:
Date: Thu, 07 Jan 2021 15:40:57 -0800 [thread overview]
Message-ID: <p917dooco3a.fsf@google.com> (raw)
In-Reply-To: <jwvh7nsmjj4.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 07 Jan 2021 18:16:15 -0500")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 1146 bytes --]
Stefan Monnier <monnier@iro.umontreal.ca> writes:
Given that this is all happening from early-init.el, I suspect info
always gets loaded.
>> While debugging something else with force-load-messages set to t, I
>> noticed that loading package-quickstart.el loads info -- is there a
>> good reason for this?
>
> IIRC when a package includes an Info manual, we load `info` before
> modifying the `Info-directory-list`. This could be improved to avoid
> loading `info`.
>
> The place where this happens in the non-quickstart case is
> `package-activate-1` and in `package-quickstart-refresh` you can see
> similar code being added to the quickstart file.
>
> IIRC the problem is that depending on whether
> `info-initialize` has already been called or not, we need to add the
> directory either to `Info-directory-list` or to
> `Info-default-directory-list`.
>
> Patches welcome (and if you need more info about the precise
> relationship between those two Info*directory-list vars, I think Eli is
> the one who knows all about it).
>
>
> Stefan
>
--
Thanks,
--Raman
7©4 Id: kg:/m/0285kf1 0Ü8
next prev parent reply other threads:[~2021-01-07 23:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 21:14 package-quickstart and info: T.V Raman
2021-01-07 23:16 ` Stefan Monnier
2021-01-07 23:40 ` T.V Raman [this message]
2021-01-08 2:12 ` Stefan Monnier
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=p917dooco3a.fsf@google.com \
--to=raman@google.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).