From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juri Linkov <juri@linkov.net>
Cc: 49587@debbugs.gnu.org
Subject: bug#49587: Where are links in describe-symbol minor-mode?
Date: Sat, 16 Jul 2022 14:59:59 +0200 [thread overview]
Message-ID: <87fsj1p60g.fsf@gnus.org> (raw)
In-Reply-To: <87a6mngs5m.fsf@mail.linkov.net> (Juri Linkov's message of "Fri, 16 Jul 2021 01:17:57 +0300")
Juri Linkov <juri@linkov.net> writes:
> Try to use 'C-h o' on the symbol of a minor mode defined by 'define-minor-mode'.
>
> There are many such symbols, for example:
>
> C-h o dired-hide-details-mode
>
> displays the Help buffer where text:
>
> See options: ‘dired-hide-details-hide-symlink-targets’ and
> ‘dired-hide-details-hide-information-lines’.
>
> has no links in the first part of the buffer that describes the function,
> but there are links only in the second part that describes the variable.
I've now fixed this in Emacs 29.
> Also such text in the output of 'C-h o' looks clumsy:
>
> This is a minor mode. If called interactively, toggle the
> ‘Dired-Hide-Details mode’ mode.
Well, it looks pretty clumsy `C-h f', too.
> Another problem is that with 'C-h o' the same Help buffer is displayed twice
> that breaks some window-displaying commands.
I'm not sure what can be done about that -- the `C-h o' function
basically just calls `C-h f' and `C-h v'. But what setups do they break
in practice?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-07-16 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 22:17 bug#49587: Where are links in describe-symbol minor-mode? Juri Linkov
2021-07-16 9:20 ` Lars Ingebrigtsen
2022-07-16 12:59 ` Lars Ingebrigtsen [this message]
2022-07-17 18:30 ` Juri Linkov
2022-07-22 15:04 ` Lars Ingebrigtsen
2022-07-22 20:47 ` Lars Ingebrigtsen
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=87fsj1p60g.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=49587@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).