From: Filipp Gunbin <fgunbin@fastmail.fm>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 32950@debbugs.gnu.org
Subject: bug#32950: 27.0.50; Strange display bug in *Help* buffer
Date: Tue, 09 Oct 2018 02:11:06 +0300 [thread overview]
Message-ID: <m2efd011bp.fsf@fastmail.fm> (raw)
In-Reply-To: <83r2h0yzrf.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 08 Oct 2018 23:00:52 +0300")
Hi,
On 08/10/2018 23:00 +0300, Eli Zaretskii wrote:
>> From: Filipp Gunbin <fgunbin@fastmail.fm>
>> Cc: 32950@debbugs.gnu.org
>> Date: Mon, 08 Oct 2018 18:28:55 +0300
>>
>> > Yes. This is the intended behavior. Go to that black line and type
>> > "M-x describe-text-properties RET": you will see what it tries to do.
>> > Also try the same on a GUI frame.
>>
>> I see these text props there:
>>
>> face (:height 0.1 :inverse-video t)
>>
>> Yes, it's inverse-video, but it does not provide an explanation.
>
> I'm not sure I follow: explanation for what? The ":height 0.1" part
> is supposed to explain that the intent is to display a thin horizontal
> line, except that TTY frames don't support variable-height lines, so
> you see a normal-height line there in inverse video.
Explanation for why it's there, in the first place. Ok, it's thin in
GUI, but it's very prominent on TTY.
>> Anyway, it looks somewhat scary for an unprepared user. Why don't we
>> just show usual help for variable/function separately, and make this
>> "list"?
>
> I'm sure that whoever coded this thought it to be a very coll feature,
> so all I can advise is to get used to it.
>
>> I doubt that even experienced users know about this feature.
>
> Well, I, for one, do.
>
> Not every surprising feature should be an immediate candidate for
> removal.
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.
Well, now I know about it too, so it's not a problem for me. I was
thinking of others, who may as well file a bug about it, and maintainers
will spend time responding to it. Yes, this seems to be a rare case -
for example, the reverse reference (from variable proced-sort to
function) is not there, but still.
Thanks.
next prev parent reply other threads:[~2018-10-08 23:11 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 [this message]
2018-10-09 7:44 ` martin rudalics
2018-10-09 14:59 ` Eli Zaretskii
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=m2efd011bp.fsf@fastmail.fm \
--to=fgunbin@fastmail.fm \
--cc=32950@debbugs.gnu.org \
--cc=eliz@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).