From: Miles Bader <miles@lsi.nec.co.jp>
Cc: keichwa@gmx.net, storm@cua.dk, romain@orebokech.com, emacs-devel@gnu.org
Subject: Re: Patch to disable links line in *info* buffer
Date: 11 Jun 2002 16:05:58 +0900 [thread overview]
Message-ID: <buoofeii9bd.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <87vg8qisfw.fsf@tc-1-100.kawasaki.gol.ne.jp>
Miles Bader <miles@gnu.org> 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'
next prev parent reply other threads:[~2002-06-11 7:05 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 18:32 Patch to disable links line in *info* buffer Romain FRANCOISE
2002-06-06 23:24 ` Kim F. Storm
2002-06-07 23:22 ` Richard Stallman
2002-06-08 0:52 ` Kim F. Storm
2002-06-08 21:39 ` Romain FRANCOISE
2002-06-08 22:08 ` Alex Schroeder
2002-06-08 22:30 ` Robert J. Chassell
2002-06-09 4:11 ` Miles Bader
2002-06-09 10:56 ` Robert J. Chassell
2002-06-09 5:16 ` Eli Zaretskii
2002-06-10 13:59 ` Stefan Monnier
2002-06-10 16:46 ` Robert J. Chassell
2002-06-10 17:28 ` Stefan Monnier
2002-06-10 20:50 ` Robert J. Chassell
2002-06-10 22:18 ` Thien-Thi Nguyen
2002-06-10 22:24 ` Stefan Monnier
2002-06-11 11:15 ` Robert J. Chassell
2002-06-11 21:00 ` Thien-Thi Nguyen
2002-06-11 5:26 ` Eli Zaretskii
2002-06-10 20:58 ` Robert J. Chassell
2002-06-10 21:52 ` Stefan Monnier
2002-06-11 9:36 ` Andreas Schwab
2002-06-10 19:57 ` Kim F. Storm
2002-06-11 19:25 ` Richard Stallman
2002-06-11 20:01 ` Jason Rumney
2002-06-11 23:45 ` Kim F. Storm
2002-06-12 12:14 ` Richard Stallman
2002-06-12 22:15 ` Kim F. Storm
2002-06-13 21:46 ` Richard Stallman
2002-06-13 23:22 ` Kim F. Storm
2002-06-19 13:10 ` Kim F. Storm
2002-06-19 15:02 ` Stefan Monnier
2002-06-21 21:40 ` Kim F. Storm
2002-06-21 23:56 ` Kim F. Storm
2002-06-21 9:40 ` Richard Stallman
2002-06-13 15:34 ` Robert J. Chassell
2002-06-13 17:17 ` Andreas Schwab
[not found] ` <200206130905.g5D95ie06537@aztec.santafe.edu>
2002-06-13 11:36 ` Robert J. Chassell
2002-06-13 23:18 ` Kim F. Storm
2002-06-14 15:47 ` Richard Stallman
2002-06-17 19:28 ` Patch for emacs-lisp-intro.texi Christian Egli
2002-06-11 19:25 ` Patch to disable links line in *info* buffer Richard Stallman
2002-06-09 23:04 ` Kim F. Storm
2002-06-10 10:15 ` Richard Stallman
2002-06-10 10:25 ` Eli Zaretskii
2002-06-09 15:18 ` Richard Stallman
2002-06-09 15:58 ` Kai Großjohann
2002-06-09 23:38 ` Kim F. Storm
2002-06-10 23:43 ` Richard Stallman
2002-06-10 5:14 ` Karl Eichwalder
2002-06-10 5:24 ` Miles Bader
2002-06-10 23:43 ` Richard Stallman
2002-06-11 0:12 ` Miles Bader
2002-06-11 5:27 ` Eli Zaretskii
2002-06-11 7:05 ` Miles Bader [this message]
2002-06-11 13:20 ` Robert J. Chassell
2002-06-12 2:34 ` Richard Stallman
2002-06-12 10:33 ` Robert J. Chassell
2002-06-12 23:47 ` Richard Stallman
2002-06-13 13:20 ` Robert J. Chassell
2002-06-14 15:47 ` Richard Stallman
2002-06-14 19:00 ` Karl Eichwalder
2002-06-12 2:32 ` Richard Stallman
2002-06-12 2:53 ` Miles Bader
2002-06-12 18:21 ` Karl Eichwalder
2002-06-12 21:36 ` Alex Schroeder
2002-06-11 4:17 ` Karl Eichwalder
2002-06-11 5:29 ` Eli Zaretskii
2002-06-11 15:26 ` Karl Eichwalder
2002-06-09 5:13 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2002-06-07 13:35 David Ponce
2002-06-07 13:56 David Ponce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=buoofeii9bd.fsf@mcspd15.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=emacs-devel@gnu.org \
--cc=keichwa@gmx.net \
--cc=miles@gnu.org \
--cc=romain@orebokech.com \
--cc=storm@cua.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).