From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Patch to disable links line in *info* buffer
Date: 10 Jun 2002 01:38:50 +0200 [thread overview]
Message-ID: <5xelfg9g51.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <200206091518.g59FIuL00222@aztec.santafe.edu>
Richard Stallman <rms@gnu.org> writes:
> As I read the comments, the new behaviour with two
> almost identical header lines was a change to the worse.
>
> Why do you think so? A few people say they don't like it,
A few? The majority of those who commented on this dislike it:
David Ponce started by reporting the duplicate header line as a bug.
You responded that it was deliberate.
Stefan, Eli and Miles spoke against it (or at least suggested
various methods for hiding it or making it optional).
Francoise Romain send you a patch to implement Miles' suggestion.
I also spoke against it and sent a different proposal
(adding `+' to toggle the visibility of the extra header line).
Alex Schroeder said he doesn't need it either.
> but nobody has given any reasons.
I think Eli gives the reason very clearly:
It looks like a display bug.
.. and it has already been reported as such a few days after it was
change in CVS. So imagine the number of bug reports we'll get when
21.4 is released...
>
> It never occurred to me that copying part of the header would
> be useful
>
> People complained when it was not possible. In response, we made a
> special command for doing it, but hardly anyone knows about that
> command so it is not a very good solution.
That "hardly anyone knows about that command" is hardly a good
argument to introduce a "display bug"...
The command is right there on the Info menu.
Only Robert J. Chassell seems to really need to copy from the header
lines regularly -- and to be able to do that, he already knows that
setting Info-use-header-line to nil allows him to do that.
Can't we simply put that advice into NEWS or PROBLEMS or mention it
somewhere in info's doc string or its info file -- and remove the
extra header line.
In any case, I think it is a good idea to add a mouse-3 sub-menu/command
to header-lines and mode-lines to copy its contents to the kill-ring.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2002-06-09 23:38 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 [this message]
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
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=5xelfg9g51.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
/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).