From: Eli Zaretskii <eliz@gnu.org>
To: juri@linkov.net, acm@muc.de
Cc: emacs-devel@gnu.org
Subject: Re: Unhelpful text in C-h v search-default-mode
Date: Fri, 29 Dec 2023 09:54:54 +0200 [thread overview]
Message-ID: <83y1dd5tpt.fsf@gnu.org> (raw)
In-Reply-To: <83zfxt5twt.fsf@gnu.org> (message from Eli Zaretskii on Fri, 29 Dec 2023 09:50:42 +0200)
> Date: Fri, 29 Dec 2023 09:50:42 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: acm@muc.de, emacs-devel@gnu.org
>
> > From: Juri Linkov <juri@linkov.net>
> > Cc: emacs-devel@gnu.org
> > Date: Fri, 29 Dec 2023 09:12:49 +0200
> >
> > 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)))))
> >
>
> 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.
next prev parent reply other threads:[~2023-12-29 7:54 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
2023-12-29 7:50 ` Eli Zaretskii
2023-12-29 7:54 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y1dd5tpt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
/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.