Re: Unhelpful text in C-h v search-default-mode

[Juri Linkov <juri@linkov.net>]

>> > 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)))))
>> >
>>
>> What happens with that in a build without native-compilation? does
>> what list-timers shows in that case look more friendly?
>
> Answering my own question:
>
>   0.2s    0.5s blink-cursor-timer-function
> * 0.1s       t show-paren-function
> * 0.5s :repeat blink-cursor-start
> * 0.5s       t #f(compiled-function () #<bytecode 0x12cdf98f4135684a>
>                [jit-lock--antiblink-grace-timer jit-lock-context-fontify])
>
> So are you saying that #<bytecode 0x12cdf98f4135684a> is friendlier
> than #<subr F616e6f6e796d6f75732d6c616d626461_anonymous_lambda_13>?
> If so, please explain how is it friendlier.

At least it contains symbols like 'jit-lock-context-fontify'
that provide a hint what is this function about, and
it's possible to grep these symbols.  Hopefully Alan could
improve the readability of these cryptic names.