From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Robert J. Chassell" Newsgroups: gmane.emacs.devel Subject: Re: Info enhancements Date: Thu, 4 Dec 2003 20:13:35 +0000 (UTC) Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <200312041644.hB4GiMi16974@f7.net> Reply-To: bob@rattlesnake.com NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1070569026 6610 80.91.224.253 (4 Dec 2003 20:17:06 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 4 Dec 2003 20:17:06 +0000 (UTC) Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Thu Dec 04 21:16:59 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1ARzuE-0004Mn-00 for ; Thu, 04 Dec 2003 21:16:58 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1ARzuE-0004OM-00 for ; Thu, 04 Dec 2003 21:16:58 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AS0qe-0001jZ-Nt for emacs-devel@quimby.gnus.org; Thu, 04 Dec 2003 16:17:20 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AS0op-0001Kf-5Y for emacs-devel@gnu.org; Thu, 04 Dec 2003 16:15:27 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AS0oH-0001AU-3H for emacs-devel@gnu.org; Thu, 04 Dec 2003 16:15:24 -0500 Original-Received: from [140.186.114.245] (helo=rattlesnake.com) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AS0oF-0001A8-Iw for emacs-devel@gnu.org; Thu, 04 Dec 2003 16:14:52 -0500 Original-Received: by rattlesnake.com via sendmail from stdin id (Debian Smail3.2.0.115) Thu, 4 Dec 2003 20:13:35 +0000 (UTC) Original-To: karl@freefriends.org (Karl Berry), emacs-devel@gnu.org In-reply-to: <200312041644.hB4GiMi16974@f7.net> (karl@freefriends.org) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 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:18394 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:18394 In this case, I like Stefan's idea of explicitly stating "line". Yes, this helps a great deal. Bob, I don't believe we can put the line numbers in front of the node names. That would break existing readers. .... If you use `(line 999)' or `Line 999.' then the menu looks better when the line numbers go after the node names. The parenthetical format looks better to me. Will it look better if `(line 999)' is always on one line, rather than broken over two lines? Thus we might see * electric-future-map: A Sample Variable Description. (line 999) unless we make sure that the formatting produces: * electric-future-map: A Sample Variable Description. (line 999) As far as I can see, using parenthetical line numbers, the node name must end on column 65 (66 being the period), or else the line expression should all go to the next line. This puts the closing parenthesis on column 78. I don't see the line indications have to align, .... I think they will look better if aligned. Many manuals, such as the Calc manual, have lots of short node names. The line numbers will look better if also in a nice column -- maybe even with the numbers themselves padded (invisibly) to four columns, so the right hand parentheses line up. Menu entries with longer node names push the line numbers to the right, and that is that. Thus a menu might look like this (which I indented to make the filling more obvious): * histogram: Manipulating Vectors. (line 78) * hms: Conversions. (line 63) * holiday: Business Days. (line 114) * hour: Date Functions. (line 27) * hypot: Basic Arithmetic. (line 174) * idiv: Basic Arithmetic. (line 121) * idn: Building Vectors. (line 44) * ierf: Other Features of Rewrite Rules. (line 246) * if: Logical Operations. (line 89) * ilog: Logarithmic Functions. (line 27) rather than: * histogram: Manipulating Vectors. (line 78) * hms: Conversions. (line 63) * holiday: Business Days. (line 114) * hour: Date Functions. (line 27) * hypot: Basic Arithmetic. (line 174) * idiv: Basic Arithmetic. (line 121) * idn: Building Vectors. (line 44) * ierf: Other Features of Rewrite Rules. (line 246) * if: Logical Operations. (line 89) * ilog: Logarithmic Functions. (line 27) With an alternative format a menu looks like this: * histogram: Manipulating Vectors. Line 78. * hms: Conversions. Line 63. * holiday: Business Days. Line 114. * hour: Date Functions. Line 27. * hypot: Basic Arithmetic. Line 174. * idiv: Basic Arithmetic. Line 121. * idn: Building Vectors. Line 44. * ierf: Other Features of Rewrite Rules. Line 246. * if: Logical Operations. Line 89. * ilog: Logarithmic Functions. Line 27. or even * histogram: Manipulating Vectors. Line 78 * hms: Conversions. Line 63 * holiday: Business Days. Line 114 * hour: Date Functions. Line 27 * hypot: Basic Arithmetic. Line 174 * idiv: Basic Arithmetic. Line 121 * idn: Building Vectors. Line 44 * ierf: Other Features of Rewrite Rules. Line 246 * if: Logical Operations. Line 89 * ilog: Logarithmic Functions. Line 27 rather than * histogram: Manipulating Vectors. Line 78. * hms: Conversions. Line 63. * holiday: Business Days. Line 114. * hour: Date Functions. Line 27. * hypot: Basic Arithmetic. Line 174. * idiv: Basic Arithmetic. Line 121. * idn: Building Vectors. Line 44. * ierf: Other Features of Rewrite Rules. Line 246. * if: Logical Operations. Line 89. * ilog: Logarithmic Functions. Line 27. -- Robert J. Chassell Rattlesnake Enterprises http://www.rattlesnake.com GnuPG Key ID: 004B4AC8 http://www.teak.cc bob@rattlesnake.com