From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Eli Zaretskii" Newsgroups: gmane.emacs.devel Subject: Re: info Date: Wed, 29 Jan 2003 19:33:29 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <2110-Wed29Jan2003193328+0200-eliz@is.elta.co.il> References: <200301290133.TAA05169@eel.dms.auburn.edu> Reply-To: Eli Zaretskii NNTP-Posting-Host: main.gmane.org X-Trace: main.gmane.org 1043861822 7902 80.91.224.249 (29 Jan 2003 17:37:02 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 29 Jan 2003 17:37:02 +0000 (UTC) Cc: emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18dw8x-00022b-00 for ; Wed, 29 Jan 2003 18:36:59 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 18dwEE-00007J-00 for ; Wed, 29 Jan 2003 18:42:26 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18dw9c-0003N8-08 for emacs-devel@quimby.gnus.org; Wed, 29 Jan 2003 12:37:40 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13) id 18dw9H-00035b-00 for emacs-devel@gnu.org; Wed, 29 Jan 2003 12:37:19 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 18dw8z-0002WV-00 for emacs-devel@gnu.org; Wed, 29 Jan 2003 12:37:03 -0500 Original-Received: from bilbo.inter.net.il ([192.114.186.18]) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18dw8i-00027p-00 for emacs-devel@gnu.org; Wed, 29 Jan 2003 12:36:45 -0500 Original-Received: from zaretsky ([80.230.235.10]) by bilbo.inter.net.il (Mirapoint Messaging Server MOS 3.2.2-GA) with ESMTP id AEI03712; Wed, 29 Jan 2003 19:35:48 +0200 (IST) Original-To: teirllm@dms.auburn.edu X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9 In-reply-to: <200301290133.TAA05169@eel.dms.auburn.edu> (message from Luc Teirlinck on Tue, 28 Jan 2003 19:33:18 -0600 (CST)) Original-cc: karl@freefriends.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Emacs development discussions. List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:11194 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:11194 > Date: Tue, 28 Jan 2003 19:33:18 -0600 (CST) > From: Luc Teirlinck > > * CC Mode: (ccmode). Emacs mode for editing C, C++, Objective-C, > Java, Pike, and IDL code. > * CL: (cl). Partial Common Lisp support for Emacs Lisp. [...] > If point is on say: Java in the above and I click return I visit the > CL node. FWIW, the stand-alone Info reader doesn't move point in such cases and either says nothing or prints "No cross references in this node." It only follows a menu item if point is on the same line as the leading "* " sequence after a newline, a sequence which starts every menu item. > Would it not be more logical to look at previous (rather than > following) lines for which node to visit, since that is usually the > node the text we are looking at refers to? I like the behavior of the stand-alone Info better than what Emacs does now and better than what you propose. (But then I'm not objective about this: I worked on these aspects of the stand-alone reader.) Please also keep in mind that some menus have free text in between menu items, which doesn't belong to any menu item at all. Here's an example from the Emacs manual: * Acknowledgments:: Major contributors to GNU Emacs. Indexes (nodes containing large menus) * Key Index:: An item for each standard Emacs key sequence. Which menu item would you like Info to select if point is on "Indexes", and how should Info tell this case from the one that started this thread? Again, I'm not arguing that the current behavior is the best we could do, or that it should not be changed under any circumstances. I'm just trying to point out potential pitfalls, and given that, get to some agreement about what we would like to see in each situation.