From: Emanuel Berg <incal@dataswamp.org>
To: emacs-devel@gnu.org
Subject: Re: Unhelpful text in C-h v search-default-mode
Date: Fri, 29 Dec 2023 08:21:51 +0100 [thread overview]
Message-ID: <87il4hpj74.fsf@dataswamp.org> (raw)
In-Reply-To: 86frzlv6fy.fsf@mail.linkov.net
Juri Linkov wrote:
>> In a recent master branch Emacs, (not with -Q), from an info buffer, I
>> did C-h v search-default-mode. The text printed in *Help* included this:
>>
>> Its value is
>> #<subr F616e6f6e796d6f75732d6c616d626461_anonymous_lambda_109>
>> Original value was nil
>> Local in buffer *info*<3>; global value is nil
>>
>> .. This is quite frankly entirely unhelpful; it gives no way to find out
>> what the lambda is, in particular, no way to get to its source code. It
>> isn't even possible to disassemble the function.
>
> Another example:
>
> 0. emacs -Q
> 1. M-x list-timers
>
> * 0.1s t show-paren-function
> * 0.5s t #<subr F616e6f6e796d6f75732d6c616d626461_anonymous_lambda_13>
>
> I wonder how users are supposed to know what function it is?
> Searching by the delay number 0.5 reveals this lambda comes
> from
>
> (setq jit-lock-context-timer
> (run-with-idle-timer jit-lock-context-time t
> (lambda ()
> (unless jit-lock--antiblink-grace-timer
> (jit-lock-context-fontify)))))
One will know it by not using an anonymous function (a lambda)
but making a proper function and giving it a descriptive name,
as you see with `show-paren-function' in your own example :)
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2023-12-29 7:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 9:45 Unhelpful text in C-h v search-default-mode Alan Mackenzie
2023-10-25 6:43 ` Juri Linkov
2023-12-29 7:12 ` Juri Linkov
2023-12-29 7:21 ` Emanuel Berg [this message]
2023-12-29 7:50 ` Eli Zaretskii
2023-12-29 7:54 ` Eli Zaretskii
2023-12-30 17:40 ` Juri Linkov
2023-12-29 10:01 ` Alan Mackenzie
2023-12-29 10:58 ` Emanuel Berg
2023-12-30 17:43 ` Juri Linkov
2023-12-31 3:23 ` Emanuel Berg
2023-12-29 11:45 ` Eli Zaretskii
2023-12-29 20:19 ` Andrea Corallo
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=87il4hpj74.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=emacs-devel@gnu.org \
/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).