From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Thierry Volpiatto <thievol@posteo.net>,
70163@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#70163: 29.3; hexl-mode incorrect docstring
Date: Thu, 04 Apr 2024 14:45:14 +0200 [thread overview]
Message-ID: <mvmplv5cn51.fsf@linux-m68k.org> (raw)
In-Reply-To: <86r0fl723w.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 04 Apr 2024 15:18:27 +0300")
On Apr 04 2024, Eli Zaretskii wrote:
> Does the patch below gives any better results? It doesn't look better
> to me: the "Uses keymap..." blurb gets in the way and makes the
> documentation text wrong.
C-h f hexl-mode triggers the autoload and uses the substituted doc
string (thus no blurb). M-x apropos hexl-mode does not trigger the
autoload and uses the substituted first line of the doc string
(including the blurb if present). C-h a hexl-mode uses the first line
of the raw doc string.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2024-04-04 12:45 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 15:02 bug#70163: 29.3; hexl-mode incorrect docstring Thierry Volpiatto
2024-04-03 15:50 ` Eli Zaretskii
2024-04-03 16:37 ` Andreas Schwab
2024-04-03 17:04 ` Thierry Volpiatto
2024-04-03 18:14 ` Eli Zaretskii
2024-04-04 5:47 ` Thierry Volpiatto
2024-04-04 12:18 ` Eli Zaretskii
2024-04-04 12:45 ` Andreas Schwab [this message]
2024-04-04 13:07 ` Eli Zaretskii
2024-04-04 13:20 ` Andreas Schwab
2024-04-04 12:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-04 13:16 ` Andreas Schwab
2024-04-04 13:23 ` Eli Zaretskii
2024-04-04 13:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-04 18:41 ` Thierry Volpiatto
2024-04-05 5:46 ` Eli Zaretskii
2024-04-05 6:29 ` Thierry Volpiatto
2024-04-06 10:46 ` Eli Zaretskii
2024-04-06 11:27 ` Thierry Volpiatto
2024-04-06 12:52 ` Ihor Radchenko
2024-04-06 14:05 ` Andreas Schwab
2024-04-06 14:15 ` Eli Zaretskii
2024-04-06 15:05 ` Andreas Schwab
2024-04-06 15:27 ` Eli Zaretskii
2024-04-06 15:49 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-06 16:16 ` Eli Zaretskii
2024-04-06 20:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-06 20:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-07 5:29 ` Eli Zaretskii
2024-04-07 14:48 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-07 14:57 ` Eli Zaretskii
2024-04-07 16:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-07 16:11 ` Eli Zaretskii
2024-04-03 17:04 ` Thierry Volpiatto
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=mvmplv5cn51.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=70163@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=thievol@posteo.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).