From: Juri Linkov <juri@jurta.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: Re: breadcrumbs for Info . . . . . .
Date: Thu, 12 Jun 2008 01:40:34 +0300 [thread overview]
Message-ID: <87tzfzk331.fsf@jurta.org> (raw)
In-Reply-To: <00d901c8cbc9$7df36fb0$0200a8c0@us.oracle.com> (Drew Adams's message of "Wed, 11 Jun 2008 06:46:03 -0700")
>> When nodes are in different files, visiting all ancestor nodes means
>> visiting several files that is slow on slow machines/connections.
>> For instance, the first node in the file info/emacs-4 is:
>>
>> File: emacs, Node: Fortran Indent, Next: Fortran
>> Comments, Prev: Fortran Motion, Up: Fortran
>>
>> 31.13.2 Fortran Indentation
>>
>> So to display this node, it needs to open the file info/emacs-3 that
>> contains its parent node Fortran, and the top file info/emacs-1.
>
> Yes, I know that. But can you point to a particular node in a particular manual
> that you find is too slow?
>
> I checked (using `T') all of the manuals that come by default with Emacs on
> Windows - I found no nodes deeper than 4. I didn't check each level 4 node in
> each manual, but I checked several, and I see no performance problem. Perhaps
> you can find a level 4 node whose levels 1-3 are in different subfiles, and you
> can check whether it is too slow?
>
> IOW, is this a real problem in practice or just a hypothetical problem?
There were reports about Info taking substantial time to read
Info subfiles on slow connections. You can search for e.g.
"Info slow connection" keywords and find posts like
http://thread.gmane.org/gmane.emacs.devel/17436/focus=18058
I don't know how often such situations happen nowadays.
Anyway, Info already scans the whole manual on the first visit
to find the index nodes, so it could build an internal node tree
as well on the same pass.
There is also another visual problem: when Info-hide-note-references
is nil, the displayed breadcrumbs line is not nice looking:
*Note Top:: > *Note Files:: > *Note Saving:: > *Note Backup::
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2008-06-11 22:40 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 23:52 breadcrumbs for Info . . . . . Drew Adams
2008-06-11 0:04 ` Juri Linkov
2008-06-11 3:18 ` Drew Adams
2008-06-11 9:34 ` Juri Linkov
2008-06-11 13:46 ` Drew Adams
2008-06-11 18:59 ` Eli Zaretskii
2008-06-11 22:40 ` Juri Linkov [this message]
2008-06-12 2:01 ` Miles Bader
2008-06-12 22:42 ` Drew Adams
2008-06-13 3:27 ` Stefan Monnier
2008-06-13 6:34 ` Drew Adams
2008-06-13 8:43 ` Thien-Thi Nguyen
2008-06-13 13:55 ` Drew Adams
2008-06-13 17:17 ` Thien-Thi Nguyen
2008-06-13 17:52 ` Drew Adams
2008-06-13 19:55 ` Thien-Thi Nguyen
2008-06-13 20:10 ` Drew Adams
2008-06-15 18:19 ` Juri Linkov
2008-06-13 14:05 ` Stefan Monnier
2008-06-13 15:12 ` Drew Adams
2008-06-13 17:16 ` Stefan Monnier
2008-06-13 18:32 ` Thien-Thi Nguyen
2008-06-14 9:47 ` Eli Zaretskii
2008-06-14 10:01 ` Thien-Thi Nguyen
2008-06-13 13:58 ` Stefan Monnier
2008-06-13 15:11 ` Drew Adams
2008-06-13 20:34 ` Stefan Monnier
2008-06-13 22:11 ` Drew Adams
2008-06-13 22:44 ` Stefan Monnier
2008-06-14 9:45 ` Drew Adams
2008-06-14 16:16 ` Stefan Monnier
2008-06-14 17:24 ` Drew Adams
2008-06-14 18:04 ` Stefan Monnier
2008-06-15 0:27 ` Juri Linkov
2008-06-15 7:33 ` Drew Adams
2008-06-15 18:23 ` Juri Linkov
2008-06-15 19:46 ` Drew Adams
2008-06-15 0:28 ` Juri Linkov
2008-06-15 2:04 ` Stefan Monnier
2008-06-15 18:18 ` Juri Linkov
2008-06-15 7:55 ` Drew Adams
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=87tzfzk331.fsf@jurta.org \
--to=juri@jurta.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@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 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.