From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>, "'Juri Linkov'" <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: RE: Why doesn't Info `T' cache node tree for current file?
Date: Tue, 10 Jun 2008 20:24:31 -0700 [thread overview]
Message-ID: <00b201c8cb72$aa4c5a60$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <ubq28k688.fsf@gnu.org>
> > I see one problem: how to refresh the cached TOC buffer when the
> > Info file changes
>
> I can refresh it the first time the user invokes Info-toc and you
> discover that the Info file is different from what it was last time
> you created the TOC.
Yes, that's the way I see it. The file is associated with the TOC.
If, when the user hits `T', the current manual (file) is different from the one
associated with the cached TOC, then you build a new TOC.
The question is whether it's worth saving both caches. Memory/time trade-off.
prev parent reply other threads:[~2008-06-11 3:24 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
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 [this message]
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='00b201c8cb72$aa4c5a60$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).