From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Miles Bader Newsgroups: gmane.emacs.devel Subject: Re: Patch to disable links line in *info* buffer Date: 11 Jun 2002 16:05:58 +0900 Sender: emacs-devel-admin@gnu.org Message-ID: References: <87bsaos1fl.fsf@orebokech.com> <200206072322.g57NMtK27277@aztec.santafe.edu> <5xbsam1tje.fsf@kfs2.cua.dk> <200206091518.g59FIuL00222@aztec.santafe.edu> <200206102343.g5ANhlv02332@aztec.santafe.edu> <87vg8qisfw.fsf@tc-1-100.kawasaki.gol.ne.jp> Reply-To: Miles Bader NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1023779369 4474 127.0.0.1 (11 Jun 2002 07:09:29 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Tue, 11 Jun 2002 07:09:29 +0000 (UTC) Cc: keichwa@gmx.net, storm@cua.dk, romain@orebokech.com, emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17HfmT-0001A3-00 for ; Tue, 11 Jun 2002 09:09:29 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 17Hg9f-0007Vo-00 for ; Tue, 11 Jun 2002 09:33:27 +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 17Hfm6-0002Cs-00; Tue, 11 Jun 2002 03:09:06 -0400 Original-Received: from tyo202.gate.nec.co.jp ([210.143.35.52]) by fencepost.gnu.org with smtp (Exim 3.34 #1 (Debian)) id 17HfjE-000217-00; Tue, 11 Jun 2002 03:06:08 -0400 Original-Received: from mailgate4.nec.co.jp ([10.7.69.195]) by TYO202.gate.nec.co.jp (8.11.6/3.7W01080315) with ESMTP id g5B762e12361; Tue, 11 Jun 2002 16:06:02 +0900 (JST) Original-Received: from mailsv4.nec.co.jp (mailgate51.nec.co.jp [10.7.69.196]) by mailgate4.nec.co.jp (8.11.6/3.7W-MAILGATE-NEC) with ESMTP id g5B761L02931; Tue, 11 Jun 2002 16:06:01 +0900 (JST) Original-Received: from mcsss2.ucom.lsi.nec.co.jp ([10.30.114.133]) by mailsv4.nec.co.jp (8.11.6/3.7W-MAILSV4-NEC) with ESMTP id g5B760221150; Tue, 11 Jun 2002 16:06:00 +0900 (JST) Original-Received: from mcspd15.ucom.lsi.nec.co.jp (mcspd15 [10.30.114.174]) by mcsss2.ucom.lsi.nec.co.jp (8.10.2+Sun/3.7Wlsi_mx_6.0) with ESMTP id g5B75xK01958; Tue, 11 Jun 2002 16:05:59 +0900 (JST) Original-Received: by mcspd15.ucom.lsi.nec.co.jp (Postfix, from userid 31295) id 8D84F3722; Tue, 11 Jun 2002 16:05:58 +0900 (JST) Original-To: rms@gnu.org System-Type: i686-pc-linux-gnu Blat: Foop In-Reply-To: <87vg8qisfw.fsf@tc-1-100.kawasaki.gol.ne.jp> Original-Lines: 44 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:4743 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:4743 Miles Bader writes: > Now, perhaps your solution of duplicate header lines _is_ the best > compromise -- it avoids screwing up the nice interface, and it makes > Bob happy (I guess), even if it slightly confuses users and makes the > info buffer uglier. > > Perhaps it would be possible to add some sort of header-line hackery so > that the header-line is only displayed when the buffer-resident > nodes-line has scrolled out of view. Here are two possibilities that come to mind for an improved (less confusing or `bug like') display: (1) I tried some experiments, and it's possible to do something like this: (setq header-line-format '(:eval (and (> (window-start) (point-min)) 'Info-header-line))) which has the effect of making the header-line blank (I couldn't find any way to make it actually disappear) if the `in file' nodes-line is visible. As soon as the screen scrolls so that the first line of the node isn't visible anymore, the header-line becomes non-blank (so it looks a bit like the in-file version "shifts" into the header-line). (2) The header-line contains only the `Next:', `Prev:' and `Up:' tags (to save space) whereas the the in-file nodes-line contains `File:' and `Node:' tags as well. If the general point of copying is to identify the current node, we could keep the `Next:' &c tags in the header-line, and put _only_ the `File:' and `Node:' tags in the (displayed) buffer -- that way, there wouldn't be any redundancy, and the string that people most commonly might want to copy is available in the buffer for copying. This would also have the advantage that the first line usually wouldn't wrap, as it often does currently. Personally I think (2) is a good compromise. Thoughts? -Miles -- `Life is a boundless sea of bitterness'