From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: Why doesn't Info `T' cache node tree for current file? Date: Tue, 10 Jun 2008 20:18:09 -0700 Message-ID: <00af01c8cb71$c68188a0$0200a8c0@us.oracle.com> 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" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1213154516 23064 80.91.229.12 (11 Jun 2008 03:21:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 11 Jun 2008 03:21:56 +0000 (UTC) Cc: 'Eli Zaretskii' , emacs-devel@gnu.org To: "'Stefan Monnier'" , "'Juri Linkov'" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 11 05:22:39 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 1K6Gv0-00039M-2U for ged-emacs-devel@m.gmane.org; Wed, 11 Jun 2008 05:22:38 +0200 Original-Received: from localhost ([127.0.0.1]:54477 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K6GuC-0004h2-ID for ged-emacs-devel@m.gmane.org; Tue, 10 Jun 2008 23:21:48 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K6GsE-0002Es-Ft for emacs-devel@gnu.org; Tue, 10 Jun 2008 23:19:46 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K6GsD-0002D0-1r for emacs-devel@gnu.org; Tue, 10 Jun 2008 23:19:45 -0400 Original-Received: from [199.232.76.173] (port=37157 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K6GsC-0002Cm-TA for emacs-devel@gnu.org; Tue, 10 Jun 2008 23:19:44 -0400 Original-Received: from rgminet01.oracle.com ([148.87.113.118]:51897) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1K6Gs6-00062X-Bs; Tue, 10 Jun 2008 23:19:39 -0400 Original-Received: from agmgw1.us.oracle.com (agmgw1.us.oracle.com [152.68.180.212]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id m5B3JYq9009080; Tue, 10 Jun 2008 21:19:35 -0600 Original-Received: from acsmt350.oracle.com (acsmt350.oracle.com [141.146.40.150]) by agmgw1.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id m5B3JXRg005051; Tue, 10 Jun 2008 21:19:34 -0600 Original-Received: from inet-141-146-46-1.oracle.com by acsmt351.oracle.com with ESMTP id 3690173851213154291; Tue, 10 Jun 2008 20:18:11 -0700 Original-Received: from dradamslap1 (/24.5.171.3) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 10 Jun 2008 20:18:10 -0700 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: Thread-Index: AcjLYMJ3HLkp4GTRR76+IxQMVpsAvAAD2EnA X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-detected-kernel: by monty-python.gnu.org: Linux 2.4-2.6 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:98918 Archived-At: > 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). I don't see any performance problem. Can you refer to a specific scenario, so we can talk concretely if there is really a performance problem? > > 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. See my replies to others. What kind of file changes are we talking about: (a) change of the file on disk or just (b) change by the user to visit a different file? Why would we worry about (a)? For (b), why wouldn't we just associate the file name with the cache?