From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Why doesn't Info `T' cache node tree for current file? Date: Tue, 10 Jun 2008 20:52:38 +0300 Message-ID: References: <004001c8cb1b$69006c10$0200a8c0@us.oracle.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1213120410 23221 80.91.229.12 (10 Jun 2008 17:53:30 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 10 Jun 2008 17:53:30 +0000 (UTC) Cc: emacs-devel@gnu.org To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 10 19:54:13 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 1K682t-0006Ca-QA for ged-emacs-devel@m.gmane.org; Tue, 10 Jun 2008 19:54:12 +0200 Original-Received: from localhost ([127.0.0.1]:49693 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K6826-0005DG-Ey for ged-emacs-devel@m.gmane.org; Tue, 10 Jun 2008 13:53:22 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K6821-0005Cq-Fu for emacs-devel@gnu.org; Tue, 10 Jun 2008 13:53:17 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K681y-0005Ce-Ng for emacs-devel@gnu.org; Tue, 10 Jun 2008 13:53:16 -0400 Original-Received: from [199.232.76.173] (port=41749 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K681y-0005Cb-KX for emacs-devel@gnu.org; Tue, 10 Jun 2008 13:53:14 -0400 Original-Received: from mtaout4.012.net.il ([84.95.2.10]:15936) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K681y-0007F3-8v for emacs-devel@gnu.org; Tue, 10 Jun 2008 13:53:14 -0400 Original-Received: from HOME-C4E4A596F7 ([80.230.28.131]) by i_mtaout4.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0K2900GI9ECRG2G0@i_mtaout4.012.net.il> for emacs-devel@gnu.org; Tue, 10 Jun 2008 21:07:40 +0300 (IDT) In-reply-to: <004001c8cb1b$69006c10$0200a8c0@us.oracle.com> X-012-Sender: halo1@inter.net.il X-detected-kernel: by monty-python.gnu.org: Solaris 9.1 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:98876 Archived-At: > From: "Drew Adams" > Date: Tue, 10 Jun 2008 09:59:56 -0700 > > I understand that the TOC built depends on the current Info file, but I'm > wondering why the node list (tree) for a given Info file isn't kept around, to > avoid rebuilding it each time a user hits `T'. AFAIK, Info doesn't maintain the node structure (it doesn't need to be a tree, btw, it could be a graph) in memory at all. It doesn't need to, except for Info-toc. So if you are suggesting that the results of Info-toc should be stashed away waiting for the user to invoke Info-toc again for the same Info file, then maybe we should do it; otherwise, generating the node graph just so TOC would be created faster is IMO not a good idea. Btw, I can understand why whoever wrote Info-toc didn't save the resulting buffer: Info always throws away the (sub-)file when it switches to another, and *toc* is treated the same way. So it fits better into the overall code structure, whereby a file is visited (in this case, generated out of thin air), displayed, then its buffer discarded.