From: Eli Zaretskii <eliz@gnu.org>
To: 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 18:52:50 +0300 [thread overview]
Message-ID: <83wpnfnlf1.fsf@gnu.org> (raw)
In-Reply-To: <4e02c2a0-6e68-4091-a64d-131bcfc2fc49@default> (message from Drew Adams on Sat, 30 Apr 2016 07:37:50 -0800 (GMT-08:00))
> Date: Sat, 30 Apr 2016 07:37:50 -0800 (GMT-08:00)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, 13841@debbugs.gnu.org
>
> > > This is a REGRESSION. With Emacs 23.4, emacs -Q C-h k, same
> > > recipe, you see this:
> >
> > The difference to newer Emacsen is that this menu command had been a
> > quoted lambda in Emacs 23 (that didn't get compiled), and has been
> > unquoted since then (good!). So I guess it's not a regression since
> > 23.4.
>
> Not sure what you're saying about when or whether a regression
> was introduced.
>
> In fact, this is a regression that was introduced in Emacs 24.3
> (probably you meant that, not 23.4). In 24.2 and prior there
> was no such problem.
Of course, there was a problem! Showing users a bunch of convoluted
Lisp when they ask what a key does is plain usability bug! It doesn't
matter whether that Lisp is compiled or not, it's no way of _helping_
the user understand what the function does.
If you don't mind the Lisp form, you shouldn't mind the byte-compiled
form, either. And if you cannot read bytecode, you can disassemble
it, then it should be as crystal-clear to you as the Emacs 23 vintage
result.
> And in this particular case, at least, a simple fix should
> be to use a named function and not an anonymous one (in
> `menu-bar-line-wrapping-menu').
Indeed. And in any other case like this.
So let's stop talking about "regressions", and start talking about the
real problem here. Which also suggests an easy solution.
> But a more general solution should be sought to the various
> problems introduced by the aggressive/eager byte-compiling
> that is the underlying cause of this regression.
A more general solution is not to have lambda functions hang on keys
and mouse clicks.
next prev parent reply other threads:[~2016-04-30 15:52 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 [this message]
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
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=83wpnfnlf1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13841@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--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.