From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 32950@debbugs.gnu.org, fgunbin@fastmail.fm
Subject: bug#32950: 27.0.50; Strange display bug in *Help* buffer
Date: Tue, 09 Oct 2018 17:59:13 +0300 [thread overview]
Message-ID: <83efczyxmm.fsf@gnu.org> (raw)
In-Reply-To: <5BBC5C67.3060508@gmx.at> (message from martin rudalics on Tue, 09 Oct 2018 09:44:39 +0200)
> Date: Tue, 09 Oct 2018 09:44:39 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: 32950@debbugs.gnu.org
>
> > I'm sure on GUI it serves its purpose well, when it's really thin line.
> > But on TTY, as I already wrote, nothing except "what happened?" comes to
> > (my) mind. When you are accustomed to the usual behavior of Help
> > buffers to replace contents when following a link, this special-case
> > adding is really confusing.
>
> Would it be difficult to replace it with a line of dashes on TTYs?
You mean, apart of adding some code to make that happen? No, I don't
think so. But don't be surprised if someone then comes up crying that
their favorite feature was removed.
next prev parent reply other threads:[~2018-10-09 14:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 18:52 bug#32950: 27.0.50; Strange display bug in *Help* buffer Filipp Gunbin
2018-10-05 19:54 ` Eli Zaretskii
2018-10-08 15:28 ` Filipp Gunbin
2018-10-08 20:00 ` Eli Zaretskii
2018-10-08 23:11 ` Filipp Gunbin
2018-10-09 7:44 ` martin rudalics
2018-10-09 14:59 ` Eli Zaretskii [this message]
2021-11-06 0:28 ` Stefan Kangas
2021-11-06 0:34 ` Lars Ingebrigtsen
2021-11-06 0:37 ` Lars Ingebrigtsen
2021-11-06 1:05 ` Stefan Kangas
2021-11-06 1:13 ` Lars Ingebrigtsen
2021-11-06 1:05 ` Stefan Kangas
2021-11-06 1:16 ` Lars Ingebrigtsen
2021-11-06 1:36 ` Stefan Kangas
2021-11-06 1:48 ` Lars Ingebrigtsen
2021-11-06 2:24 ` Stefan Kangas
2021-11-06 2:31 ` Lars Ingebrigtsen
2021-11-06 3:11 ` Stefan Kangas
2021-11-06 4:01 ` Lars Ingebrigtsen
2021-11-06 6:12 ` Stefan Kangas
2021-11-06 18:00 ` Lars Ingebrigtsen
2021-11-06 8:00 ` Eli Zaretskii
2021-11-06 9:34 ` Eli Zaretskii
2021-11-06 11:09 ` Stefan Kangas
2021-11-06 11:39 ` Eli Zaretskii
2021-11-06 17:57 ` Lars Ingebrigtsen
2021-11-06 18:27 ` Eli Zaretskii
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=83efczyxmm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32950@debbugs.gnu.org \
--cc=fgunbin@fastmail.fm \
--cc=rudalics@gmx.at \
/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).