From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Why doesn't Info `T' cache node tree for current file? Date: Tue, 10 Jun 2008 21:16:01 -0400 Message-ID: References: <004001c8cb1b$69006c10$0200a8c0@us.oracle.com> <004201c8cb25$1b2be870$0200a8c0@us.oracle.com> <009501c8cb3c$9246d110$0200a8c0@us.oracle.com> <877icwn8l0.fsf@jurta.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1213146986 7370 80.91.229.12 (11 Jun 2008 01:16:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 11 Jun 2008 01:16:26 +0000 (UTC) Cc: Eli Zaretskii , Drew Adams , emacs-devel@gnu.org To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 11 03:17:08 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1K6ExT-0002xH-Kv for ged-emacs-devel@m.gmane.org; Wed, 11 Jun 2008 03:17:03 +0200 Original-Received: from localhost ([127.0.0.1]:46888 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K6Ewg-0002HF-6G for ged-emacs-devel@m.gmane.org; Tue, 10 Jun 2008 21:16:14 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K6Ewa-0002FR-Sr for emacs-devel@gnu.org; Tue, 10 Jun 2008 21:16:08 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K6EwY-0002D0-TT for emacs-devel@gnu.org; Tue, 10 Jun 2008 21:16:08 -0400 Original-Received: from [199.232.76.173] (port=38100 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K6EwY-0002Cx-Mw for emacs-devel@gnu.org; Tue, 10 Jun 2008 21:16:06 -0400 Original-Received: from ironport2-out.pppoe.ca ([206.248.154.182]:41802 helo=ironport2-out.teksavvy.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K6EwV-0006jZ-Dy; Tue, 10 Jun 2008 21:16:03 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsoEALjDTkhMCpcZ/2dsb2JhbACBW69V X-IronPort-AV: E=Sophos;i="4.27,620,1204520400"; d="scan'208";a="22387980" Original-Received: from smtp.pppoe.ca (HELO smtp.teksavvy.com) ([65.39.196.238]) by ironport2-out.teksavvy.com with ESMTP; 10 Jun 2008 21:16:02 -0400 Original-Received: from pastel.home ([76.10.151.25]) by smtp.teksavvy.com (Internet Mail Server v1.0) with ESMTP id RHB37502; Tue, 10 Jun 2008 21:16:02 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id DB2EB82F1; Tue, 10 Jun 2008 21:16:01 -0400 (EDT) In-Reply-To: <877icwn8l0.fsf@jurta.org> (Juri Linkov's message of "Wed, 11 Jun 2008 03:02:15 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:98911 Archived-At: >> Anyway, no _need_ to do anything. 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). When the delay after typing `T' is more than 1 sec, > this is unbearable for many users. I haven't heard any complaint about it, so it looks like those delays rarely if ever occur. And I believe machines are getting faster more quickly than manuals are getting larger, so I don't expect reports to become much more frequent in the future. OTOH, such caching might be necessary for Drew's breadcrumbs (a small delay is fine for `T' but is problematic if it occurs at every page). > So we could cache the TOC buffer per Info file, if this costs us > nothing. I see one problem: how to refresh the cached TOC buffer when > the Info file changes - the usual key `g' for buffer refreshing is > already allocated to `Info-goto-node'. The refresh should be 100% automatic by recording the timestamps of the files. Stefan