From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 64575@debbugs.gnu.org
Subject: bug#64575: 29.0.92; Help buffers are unnecessarily under Outline mode
Date: Wed, 12 Jul 2023 09:35:03 +0300 [thread overview]
Message-ID: <86a5w17hn4.fsf@mail.linkov.net> (raw)
In-Reply-To: <83a5w26yum.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 11 Jul 2023 22:18:41 +0300")
> The *Help* buffer is still under Outline minor mode, although it now
> makes no sense, since there are no heading lines in the buffer.
But it has no adverse effect. OTOH, when some Help command
will insert a heading line, then it will be handled automatically.
For example, 'C-h m' (describe-mode) could take advantage of
outline-minor-mode with heading lines for every displayed minor mode.
> The actual functions you use in "C-h f" don't matter; the point is
> that the Outline minor mode, once set by "C-h b", stays turned on in
> the *Help* buffers, instead of being reset when not needed.
If you still think it should be disabled everywhere outside of 'C-h b',
this could be fixed by such patch:
diff --git a/lisp/help-mode.el b/lisp/help-mode.el
index bf64d032b65..baf924ac8b4 100644
--- a/lisp/help-mode.el
+++ b/lisp/help-mode.el
@@ -498,6 +498,8 @@ help-setup-xref
because we want to record the \"previous\" position of point so we can
restore it properly when going back."
(with-current-buffer (help-buffer)
+ (when (bound-and-true-p outline-minor-mode)
+ (outline-minor-mode -1))
(when help-xref-stack-item
(push (cons (point) help-xref-stack-item) help-xref-stack)
(setq help-xref-forward-stack nil))
next prev parent reply other threads:[~2023-07-12 6:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 19:18 bug#64575: 29.0.92; Help buffers are unnecessarily under Outline mode Eli Zaretskii
2023-07-12 6:35 ` Juri Linkov [this message]
2023-07-12 12:36 ` Eli Zaretskii
2023-07-13 16:39 ` Juri Linkov
2023-07-15 8:21 ` Eli Zaretskii
2023-07-17 17:51 ` Juri Linkov
2023-07-23 13:16 ` Visuwesh
2023-07-23 13:35 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86a5w17hn4.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=64575@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.