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: Patch to disable links line in *info* buffer Date: Sun, 9 Jun 2002 10:56:11 +0000 (UTC) Sender: emacs-devel-admin@gnu.org Message-ID: References: <87bsaos1fl.fsf@orebokech.com> <200206072322.g57NMtK27277@aztec.santafe.edu> <5xbsam1tje.fsf@kfs2.cua.dk> <87wut9tppe.fsf@orebokech.com> <87elfhnlas.fsf@tc-1-100.kawasaki.gol.ne.jp> Reply-To: bob@rattlesnake.com NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1023620273 30058 127.0.0.1 (9 Jun 2002 10:57:53 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 9 Jun 2002 10:57:53 +0000 (UTC) Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17H0OO-0007oh-00 for ; Sun, 09 Jun 2002 12:57:52 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 17H0ki-00070v-00 for ; Sun, 09 Jun 2002 13:20:56 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17H0Nu-00079O-00; Sun, 09 Jun 2002 06:57:22 -0400 Original-Received: from megalith.rattlesnake.com ([140.186.114.245] helo=localhost) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17H0Mn-000721-00 for ; Sun, 09 Jun 2002 06:56:13 -0400 Original-Received: by rattlesnake.com via sendmail from stdin id (Debian Smail3.2.0.114) Sun, 9 Jun 2002 10:56:11 +0000 (UTC) Original-To: emacs-devel@gnu.org In-Reply-To: <87elfhnlas.fsf@tc-1-100.kawasaki.gol.ne.jp> (message from Miles Bader on 09 Jun 2002 13:11:23 +0900) Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.9 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:4660 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:4660 I think the Consensus on this mailing list seems to be that the old-new-style -- node-names in header-line only, not copyable -- is better. It is better than duplicating lines, which as Eli says, looks like a display bug. At this stage, the best temporary solution may be to revert. The ultimate solution may be more along the lines that Eli mentioned: ... a way to copy mode- and header-lines. although the design of the current node header does not list the Info filename, only the next, previous, and up nodes. I am not sure that the current header format is wrong; I am only saying that it is not useful to me as designed. Considering what you [Miles] said: That leaves the question of what people like who _do_ want easy copyability should do. 1) Just tell them `set Info-use-header-line to nil' This is the way it has been for a while, and works fine for knowledgeable people. This feature should certainly continue. 2) Keep reminding them of the `Info-copy-current-node-name' function (bound to `c' in info-mode, and also in the Info menu) We don't need to say more than this. 3) Perhaps add a more intuitive binding for Info-copy-current-node-name. I think both the mouse and keyboard bindings for `Info-copy-current-node-name' are fine as they are. The `Info-copy-current-node-name' function produces output that is very convenient if you know Info, since it creates a reference in a form that `Info-goto-node' understands. Unfortunately, I often communicate with people who don't know about Info, or who know very little, whom I am trying to inspire. For example, yesterday morning, a correspondent asked whether Texinfo files are directed graphs? After distinguishing between the organization of a document and the @section and similar commands, which format headers, I quoted from Texinfo manual, saying As the Texinfo manual says with respect to Info: File: texinfo, Node: Info Files For this person, such a long-winded reference is more informative and inspiring than the output of the `Info-copy-current-node-name' function, (texinfo)Info Files even though the latter is more efficient for those who already know Info. (I doubt this correspondent knows much about Info yet. I hope she will start using Texinfo to document her work, which is writing programs for biological researchers, as well as make the software free.) -- Robert J. Chassell bob@rattlesnake.com Rattlesnake Enterprises http://www.rattlesnake.com