From: Eli Zaretskii <eliz@gnu.org>
To: Hugo Nobrega <hugonobrega@dcc.ufrj.br>,
Lars Ingebrigtsen <larsi@gnus.org>
Cc: 50955@debbugs.gnu.org
Subject: bug#50955: 28.0.50; info-look loads slowly due to python info lookup
Date: Sat, 02 Oct 2021 16:19:51 +0300 [thread overview]
Message-ID: <83lf3bbm2w.fsf@gnu.org> (raw)
In-Reply-To: <87tuhzfud6.fsf@gmail.com> (message from Hugo Nobrega on Sat, 02 Oct 2021 10:07:17 -0300)
> From: Hugo Nobrega <hugonobrega@dcc.ufrj.br>
> Cc: 50955@debbugs.gnu.org
> Date: Sat, 02 Oct 2021 10:07:17 -0300
>
> Eli Zaretskii <eliz@gnu.org> writes:
> > OK, thanks. Can you show the value of Info-directory-list, after
> > invoking info-look for the first time? That should tell us in how
> > many directories does Emacs look for these missing Python manuals.
>
> `Info-directory-list' is a list of length 208, almost entirely (like 99%)
> populated with paths from the package manager `straight'.
Ouch! Now I understand why that search takes so long for you.
Not sure what to do about that. Perhaps we should disable that
python*.info search if Info-directory-list is longer than some
threshold.
Or maybe we could remove the directories where packages are installed
from Info-directory-list, when doing that search? With package.el, we
could record in some variable the list of directories we add to
Info-directory-list; maybe something similar is possible with
'straight' as well?
Lars, any other ideas?
next prev parent reply other threads:[~2021-10-02 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 1:07 bug#50955: 28.0.50; info-look loads slowly due to python info lookup Hugo Nobrega
2021-10-02 5:37 ` bug#50955: (no subject) Colin Woodbury
2021-10-02 6:55 ` bug#50955: 28.0.50; info-look loads slowly due to python info lookup Eli Zaretskii
2021-10-02 12:40 ` Hugo Nobrega
2021-10-02 12:55 ` Eli Zaretskii
2021-10-02 13:07 ` Hugo Nobrega
2021-10-02 13:19 ` Eli Zaretskii [this message]
2021-10-03 8:54 ` Lars Ingebrigtsen
2021-10-03 9:16 ` Eli Zaretskii
2021-10-04 8:53 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83lf3bbm2w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=50955@debbugs.gnu.org \
--cc=hugonobrega@dcc.ufrj.br \
--cc=larsi@gnus.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.