From: Eli Zaretskii <eliz@gnu.org>
To: Tassilo Horn <tsdh@gnu.org>
Cc: 20404@debbugs.gnu.org
Subject: bug#20404: 25.0.50; Sometimes no fontification with jit-lock-defer-time
Date: Thu, 23 Apr 2015 09:14:10 +0300 [thread overview]
Message-ID: <83a8xz2wy5.fsf@gnu.org> (raw)
In-Reply-To: <87oamfwfkc.fsf@gnu.org>
> From: Tassilo Horn <tsdh@gnu.org>
> Cc: 20404@debbugs.gnu.org
> Date: Thu, 23 Apr 2015 07:59:15 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > So you are saying that something prevents the timer to run at the
> > prescribed time?
>
> That seems to be the case.
It can also be that Emacs doesn't become idle for some reason.
> > I suggest to add trace printf's in the code that traverses the
> > idle-timers' list, and see why this timer doesn't run on time.
>
> That would be
>
> static struct timespec
> timer_check_2 (Lisp_Object timers, Lisp_Object idle_timers)
>
> right?
Yes.
> + if (ripe)
> + {
> + printf("Idle timer calling %s is ripe.", AREF (5, chosen_timer));
> + }
> }
>
> /* If timer is ripe, run it if it hasn't been run. */
> --8<---------------cut here---------------end--------------->8---
>
> I think the problem is that the AREF returns the timer's function or
> maybe the symbol whose function definition is the timer's function.
Yes, you cannon printf a Lisp object with %s.
> How do I get the function's name in order to print that?
Try SDATA (SYMBOL_NAME (AREF (5, chosen_timer))).
next prev parent reply other threads:[~2015-04-23 6:14 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 9:45 bug#20404: 25.0.50; Sometimes no fontification with jit-lock-defer-time Tassilo Horn
2015-04-22 10:32 ` Eli Zaretskii
2015-04-22 20:32 ` Tassilo Horn
2015-04-22 21:39 ` Eli Zaretskii
2015-04-23 5:59 ` Tassilo Horn
2015-04-23 6:14 ` Eli Zaretskii [this message]
2015-04-23 8:36 ` Tassilo Horn
[not found] ` <mailman.1344.1429696032.904.bug-gnu-emacs@gnu.org>
2015-04-22 16:31 ` Alan Mackenzie
2015-04-22 17:37 ` Stefan Monnier
2015-04-22 19:32 ` Alan Mackenzie
2015-04-22 20:52 ` Stefan Monnier
2015-04-22 20:10 ` Tassilo Horn
2015-04-22 21:33 ` Eli Zaretskii
2015-04-23 4:15 ` Tassilo Horn
2015-04-23 6:35 ` Eli Zaretskii
2015-04-23 13:40 ` Stefan Monnier
2015-04-23 15:11 ` Eli Zaretskii
2015-04-23 16:23 ` Stefan Monnier
2015-04-23 17:03 ` Eli Zaretskii
2015-04-23 17:27 ` Stefan Monnier
2015-04-23 17:34 ` Eli Zaretskii
2015-04-23 19:35 ` Stefan Monnier
2015-04-24 9:41 ` Eli Zaretskii
2015-04-24 14:03 ` Stefan Monnier
2015-04-24 14:36 ` Eli Zaretskii
2015-04-24 18:03 ` Stefan Monnier
2015-04-23 19:53 ` Tassilo Horn
2015-04-23 17:25 ` Eli Zaretskii
2015-04-23 19:31 ` Stefan Monnier
2015-04-23 19:52 ` Eli Zaretskii
2015-04-23 19:56 ` Tassilo Horn
2015-04-23 7:54 ` Eli Zaretskii
2015-04-23 8:38 ` Eli Zaretskii
2015-04-23 9:04 ` Tassilo Horn
2015-04-23 9:16 ` Eli Zaretskii
2015-04-23 13:40 ` Stefan Monnier
2019-10-31 14:23 ` Lars Ingebrigtsen
2019-10-31 14:51 ` Eli Zaretskii
2015-04-23 8:38 ` Tassilo Horn
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=83a8xz2wy5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20404@debbugs.gnu.org \
--cc=tsdh@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).