From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 50881@debbugs.gnu.org, stefan@marxist.se
Subject: bug#50881: C-h C-s leads to empty " *Metahelp*" buffer
Date: Wed, 29 Sep 2021 14:51:56 +0300 [thread overview]
Message-ID: <83pmsriopv.fsf@gnu.org> (raw)
In-Reply-To: <87y27fc31m.fsf@mail.linkov.net> (message from Juri Linkov on Wed, 29 Sep 2021 09:54:20 +0300)
> From: Juri Linkov <juri@linkov.net>
> Date: Wed, 29 Sep 2021 09:54:20 +0300
> Cc: 50881@debbugs.gnu.org
>
> I tried to reproduce this, then typed 'C-h C-h', and it highlights
> matching parens on the first line. This not only makes no sense,
Please elaborate why it makes no sense.
> but also distracting for users seeking help.
> 'show-paren-mode' should be disabled in all read-only buffers.
If the problem is with *Help* and other documentation buffers, why
turn it off in _all_ read-only buffers? The latter is a much broader
category. For example, debugging Lisp with Edebug makes the source
buffer read-only.
next prev parent reply other threads:[~2021-09-29 11:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 23:10 bug#50881: C-h C-s leads to empty " *Metahelp*" buffer Stefan Kangas
2021-09-29 6:54 ` Juri Linkov
2021-09-29 7:29 ` Lars Ingebrigtsen
2021-09-29 10:45 ` Stefan Kangas
2021-09-29 15:36 ` Lars Ingebrigtsen
2021-09-29 17:08 ` bug#50881: [External] : " Drew Adams
2021-09-29 11:51 ` Eli Zaretskii [this message]
2021-09-29 16:58 ` Juri Linkov
2021-09-29 17:53 ` Eli Zaretskii
2021-09-29 17:57 ` bug#50881: [External] : " Drew Adams
2021-09-29 19:20 ` Juri Linkov
2021-09-29 19:52 ` bug#50881: [External] : " Drew Adams
2021-09-30 7:03 ` Eli Zaretskii
2021-09-29 7:09 ` Lars Ingebrigtsen
2021-09-29 15:43 ` Lars Ingebrigtsen
2021-09-29 16:06 ` Stefan Kangas
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=83pmsriopv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=50881@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=stefan@marxist.se \
/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).