From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: karl@freefriends.org (Karl Berry) Newsgroups: gmane.emacs.devel Subject: Re: Info-index fails on node-name "~/.cvsrc" Date: Thu, 20 May 2004 12:30:18 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <200405201630.i4KGUIR24528@f7.net> References: <878yfnd5aa.fsf@mail.jurta.org> NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1085074674 8502 80.91.224.253 (20 May 2004 17:37:54 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 20 May 2004 17:37:54 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Thu May 20 19:37:45 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BQrUH-0007PO-00 for ; Thu, 20 May 2004 19:37:45 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BQrUG-00044i-00 for ; Thu, 20 May 2004 19:37:44 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BQqVG-0006iT-4g for emacs-devel@quimby.gnus.org; Thu, 20 May 2004 12:34:42 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BQqUv-0006eP-MY for emacs-devel@gnu.org; Thu, 20 May 2004 12:34:21 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BQqRz-0006HI-OC for emacs-devel@gnu.org; Thu, 20 May 2004 12:31:51 -0400 Original-Received: from [209.61.216.22] (helo=f7.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BQqR2-00064N-Oq for emacs-devel@gnu.org; Thu, 20 May 2004 12:30:21 -0400 Original-Received: (from karl@localhost) by f7.net (8.11.7-20030920/8.11.7) id i4KGUIR24528; Thu, 20 May 2004 12:30:18 -0400 Original-To: juri@jurta.org In-Reply-To: <878yfnd5aa.fsf@mail.jurta.org> X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:23788 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:23788 I don't know if it makes sense for menu items in non-index nodes as well. We don't need to support (line NNN) in non-index menus. If I understand correctly, a new index tag ^@^H[index^@^H] is for determining if an Info node is an index node, _additionally_ to current checking the node name for the "\\" regexp. It doesn't have to be additional. The index cookie is output whenever there's a printindex, so you can safely rely on it if it's there, whatever the name of the node is. Karl, could you confirm, is a new index tag supposed to work this way: 1. To determine if the current node is an index node, the Emacs Info reader should first try to match the node name for the "\\" regexp. If that fails, then to search for the "^@^H[index^@^H]" tag in the current node. In principle, I would say, if the cookie is present, it's an index node, and only look at the node name if the cookie is not present (for info files generated before 4.7). That way, a node whose name contains Index but isn't an index node won't be found. But in practice, I don't expect it really matters, since we've been living with the Index heuristic forever. 2. To find all index nodes in the current Info file, the Emacs Info I didn't realize/remember that's one of the jobs. Again, the algorithm you outline seems sensible, but you could also use the index cookie first if you like. (I imagine it's implemented as finding the first potential node, then apply the "is the current node an index node" test for that node and all subsequent nodes, so you'd get it for free, anyway.) Thanks, k