From: Eli Zaretskii <eliz@gnu.org>
To: Peter Dean <laszlomail@protonmail.com>
Cc: larsi@gnus.org, 46702@debbugs.gnu.org
Subject: bug#46702: Link symbol name in Help
Date: Tue, 23 Feb 2021 17:31:54 +0200 [thread overview]
Message-ID: <83blcavlzp.fsf@gnu.org> (raw)
In-Reply-To: <ODvFXmZ32xUQGvPVFjZKYXq16GZQYxulTm1rgDgBpVB3cqVPlzqbuONXS9wtEoGfPf7USaN18fx1wSdrvko53pzzMlUWVQKzAimRZm7hjWs=@protonmail.com> (message from Peter Dean on Tue, 23 Feb 2021 07:09:26 +0000)
> Date: Tue, 23 Feb 2021 07:09:26 +0000
> From: Peter Dean <laszlomail@protonmail.com>
> Cc: "larsi@gnus.org" <larsi@gnus.org>, "46702@debbugs.gnu.org" <46702@debbugs.gnu.org>
>
> On Tuesday, February 23, 2021 4:28 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> >
> > I'm not sure that's a good idea: "Documentation:" ends in a colon, so
> > the text should follow it. Otherwise it might look unrelated.
>
> What do you think of Lars' idea of removing that line altogether, since
> it's obvious the user is looking at the documentation (the user invoked
> the command)?
That would work in simple cases, such as this one, but we also have
variables whose value takes a lot of space when printed, and in those
cases we have
Documentation:
<the doc string>
Value:
<representation of the value>
E.g., try "C-h v char-script-table RET".
next prev parent reply other threads:[~2021-02-23 15:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 6:05 bug#46702: Link symbol name in Help Peter Dean via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-22 8:21 ` Andreas Schwab
2021-02-22 8:26 ` Peter Dean via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-22 8:38 ` Peter Dean via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-22 15:01 ` Lars Ingebrigtsen
2021-02-22 15:55 ` Eli Zaretskii
2021-02-22 21:34 ` Lars Ingebrigtsen
2021-02-22 21:52 ` Peter Dean via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-22 21:58 ` Lars Ingebrigtsen
2021-02-22 22:08 ` Peter Dean via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-23 3:28 ` Eli Zaretskii
2021-02-23 7:09 ` Peter Dean via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-23 15:31 ` Eli Zaretskii [this message]
2021-02-24 16:09 ` Lars Ingebrigtsen
2021-02-24 16:29 ` Peter Dean via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-24 16:38 ` Eli Zaretskii
2021-02-24 16:59 ` Lars Ingebrigtsen
2021-02-24 17:05 ` Eli Zaretskii
2021-02-25 15:15 ` Lars Ingebrigtsen
2021-02-25 15:29 ` 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=83blcavlzp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46702@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=laszlomail@protonmail.com \
/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.