From: Steve McIntyre <steve@einval.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 27933@debbugs.gnu.org, 786707@bugs.debian.org,
Rob Browning <rlb@defaultvalue.org>,
786707-forwarded@bugs.debian.org
Subject: bug#27933: emacs25: default info dir initialization slow with remote filesystems
Date: Thu, 3 Aug 2017 17:49:13 +0100 [thread overview]
Message-ID: <20170803164913.wkuvwws3ry4l4ofy__18591.1285378554$1501779080$gmane$org@tack.einval.com> (raw)
In-Reply-To: <ii37984n8z.fsf@fencepost.gnu.org>
On Thu, Aug 03, 2017 at 12:41:48PM -0400, Glenn Morris wrote:
>Steve McIntyre wrote:
>
>> I've checked yesterday using emacs25 (version 25.1+1-4 in Debian
>> stretch). I guess those changes didn't make it in before that release
>
>Indeed not.
OK, cool - thanks for clarifying!
So, I am still curious about a couple of points from my initial bug
report. Maybe you can help with those too?
>2. Why on earth is emacs checking the info path at all on startup?
> Shouldn't it wait until info functions are actually called for?
>
>3. The documentation talks about setting INFOPATH in the environment
> to over-ride the use of this default directory list, but again
> using strace I can see no change to behaviour here at all if I set
> INFOPATH
--
Steve McIntyre, Cambridge, UK. steve@einval.com
"Arguing that you don't care about the right to privacy because you have
nothing to hide is no different than saying you don't care about free
speech because you have nothing to say."
-- Edward Snowden
next prev parent reply other threads:[~2017-08-03 16:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150524155316.28851.58585.reportbug@tack.local>
2017-08-03 13:59 ` bug#27933: emacs25: default info dir initialization slow with remote filesystems Rob Browning
2017-08-03 15:29 ` Glenn Morris
2017-08-03 16:39 ` Steve McIntyre
2017-08-03 16:41 ` Glenn Morris
2017-08-03 16:49 ` Steve McIntyre [this message]
[not found] ` <20170803164913.wkuvwws3ry4l4ofy@tack.einval.com>
2017-08-03 17:25 ` Eli Zaretskii
2017-08-03 17:35 ` Glenn Morris
2017-08-03 18:31 ` Eli Zaretskii
2017-08-03 21:37 ` Glenn Morris
2022-02-03 20:04 ` Lars Ingebrigtsen
2022-03-04 16:36 ` Lars Ingebrigtsen
2022-03-14 0:57 ` Steve McIntyre
[not found] ` <E1neaLG-0000XL-2e@fencepost.gnu.org>
[not found] ` <87h76xp50o.fsf@gnus.org>
[not found] ` <E1neco7-0006BJ-8F@fencepost.gnu.org>
[not found] ` <875yndp086.fsf@gnus.org>
2022-04-14 6:51 ` Alfred M. Szmidt
2022-04-14 13:41 ` Lars Ingebrigtsen
2022-04-14 14:58 ` Drew Adams
2022-04-14 15:43 ` Glenn Morris
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='20170803164913.wkuvwws3ry4l4ofy__18591.1285378554$1501779080$gmane$org@tack.einval.com' \
--to=steve@einval.com \
--cc=27933@debbugs.gnu.org \
--cc=786707-forwarded@bugs.debian.org \
--cc=786707@bugs.debian.org \
--cc=rgm@gnu.org \
--cc=rlb@defaultvalue.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).