From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: michael_heerdegen@web.de, larsi@gnus.org, 13841@debbugs.gnu.org
Subject: bug#13841: 24.3.50; Regression - unreadable `C-h k' help
Date: Sat, 30 Apr 2016 10:14:22 -0800 (GMT-08:00) [thread overview]
Message-ID: <057bdf6b-fa05-4dba-a129-841c96cddbdf@default> (raw)
In-Reply-To: <<83inyzngx7.fsf@gnu.org>>
I agree that user help should show documentation, not just
Lisp code. But certainly - far more important - not byte code.
The fix for this bug (and any that are similar) is to
use a named function with a doc string. I think (hope)
we agree about that.
(We can disagree that if a user can read Lisp source code
then s?he should be able to also read byte code, or she
is just as likely to be able to do that.)
prev parent reply other threads:[~2016-04-30 18:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 17:01 bug#13841: 24.3.50; Regression - unreadable `C-h k' help Drew Adams
2014-02-10 7:31 ` Lars Ingebrigtsen
2016-04-28 22:37 ` Lars Ingebrigtsen
2016-04-29 16:22 ` Drew Adams
2016-04-30 11:46 ` Michael Heerdegen
2016-04-30 15:37 ` Drew Adams
2016-04-30 15:52 ` Eli Zaretskii
2016-05-01 13:50 ` Michael Heerdegen
2016-05-01 15:09 ` Eli Zaretskii
2016-05-01 15:13 ` Lars Ingebrigtsen
2016-05-01 15:43 ` Eli Zaretskii
2019-10-09 3:28 ` bug#20157: " Lars Ingebrigtsen
2019-10-09 10:57 ` Michael Heerdegen
2019-10-09 18:57 ` Lars Ingebrigtsen
[not found] ` <<87inyze2tq.fsf@web.de>
[not found] ` <<4e02c2a0-6e68-4091-a64d-131bcfc2fc49@default>
[not found] ` <<83wpnfnlf1.fsf@gnu.org>
2016-04-30 17:20 ` Drew Adams
2016-04-30 17:29 ` Eli Zaretskii
[not found] ` <<<87inyze2tq.fsf@web.de>
[not found] ` <<<4e02c2a0-6e68-4091-a64d-131bcfc2fc49@default>
[not found] ` <<<83wpnfnlf1.fsf@gnu.org>
[not found] ` <<f6490f90-dac1-4e7f-bb98-34877820dcb6@default>
[not found] ` <<83inyzngx7.fsf@gnu.org>
2016-04-30 18:14 ` Drew Adams [this message]
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=057bdf6b-fa05-4dba-a129-841c96cddbdf@default \
--to=drew.adams@oracle.com \
--cc=13841@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
/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.