From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>
Cc: 'Eli Zaretskii' <eliz@gnu.org>, emacs-devel@gnu.org
Subject: RE: Why doesn't Info `T' cache node tree for current file?
Date: Tue, 10 Jun 2008 20:17:51 -0700 [thread overview]
Message-ID: <00ad01c8cb71$bb7d1960$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <877icwn8l0.fsf@jurta.org>
> > My thought was that if someone uses `T', s?he is likely
> > to do so again, and likely with the same file. Since we
> > have gone to the trouble of building the node tree
> > (graph), why not save it for possible reuse? That's all.
>
> It is not very quick, since the code has to reread all Info subfiles
> (its slowest part).
That was my thinking - it really does seem to do quite a lot of work.
On the other hand, at least with the manuals I use (Emacs and Elisp), it seems
pretty snappy to me. Do you really see a performance problem, or is this just
hypothetical?
> When the delay after typing `T' is more than 1 sec, this is
> unbearable for many users.
Whoa! That certainly would be unbearable. I don't see anything like that. It
seems instantaneous, to me (which surprises me, since it does all of the
`Info-goto-node' stuff).
Can you give a recipe (e.g. which manual)?
> So we could cache the TOC buffer per Info file, if this costs
> us nothing.
Either the TOC buffer or the node list, depending on performance needs etc.
> I see one problem: how to refresh the cached TOC buffer when
> the Info file changes
Do you mean when you go to a different manual (different file), or do you mean
when someone changes the file on disk?
I think we can ignore the latter (no?).
And I think the former would be easy to take care of. As I see it (and I think I
said this), the file name would be associated with the cached node list (or
buffer). When the current file is different and you hit `T', a new TOC is built.
Should we keep caches already built for previously visted files or just toss
them? Could be a user option - users with lots of resources might opt for
multiple caches; others not.
> - the usual key `g' for buffer refreshing is already
> allocated to `Info-goto-node'.
No - it should be automatic - see above.
next prev parent reply other threads:[~2008-06-11 3:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 16:59 Why doesn't Info `T' cache node tree for current file? Drew Adams
2008-06-10 17:52 ` Eli Zaretskii
2008-06-10 18:09 ` Drew Adams
2008-06-10 20:25 ` Eli Zaretskii
2008-06-10 20:57 ` Drew Adams
2008-06-11 0:02 ` Juri Linkov
2008-06-11 0:55 ` Miles Bader
2008-06-11 3:18 ` Drew Adams
2008-06-11 1:16 ` Stefan Monnier
2008-06-11 3:18 ` Drew Adams
2008-06-11 3:17 ` Drew Adams [this message]
2008-06-11 9:27 ` Juri Linkov
2008-06-11 13:46 ` Drew Adams
2008-06-11 19:02 ` Eli Zaretskii
2008-06-11 3:20 ` Eli Zaretskii
2008-06-11 3:24 ` 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
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='00ad01c8cb71$bb7d1960$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.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).