From: martin rudalics <rudalics@gmx.at>
Cc: Chong Yidong <cyd@stupidchicken.com>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Nested sit-for's
Date: Sun, 20 Aug 2006 23:52:54 +0200 [thread overview]
Message-ID: <44E8D9B6.6040700@gmx.at> (raw)
In-Reply-To: <m3odufjeyg.fsf@kfs-l.imdomain.dk>
> IIUC, the recent addition of current-idle-time by RMS was supposed to
> fix the sit-for in jit-lock problem in a different way. But so far,
> RMS' changes to jit-lock have not been installed... What's up???
IIUC, `current-idle-time' would permit to replace the ugliness of my
`run-at-time' with yet another `run-with-idle-timer'. Hopefully.
next prev parent reply other threads:[~2006-08-20 21:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1GD2sr-0005PH-UP@savannah.gnu.org>
[not found] ` <m3bqqlka7e.fsf@kfs-l.imdomain.dk>
[not found] ` <87y7tp90i1.fsf@stupidchicken.com>
2006-08-16 8:14 ` Nested sit-for's Kim F. Storm
2006-08-16 19:08 ` Chong Yidong
2006-08-17 6:02 ` Richard Stallman
2006-08-17 11:15 ` Kim F. Storm
2006-08-17 14:02 ` David Kastrup
2006-08-18 15:47 ` Richard Stallman
2006-08-17 14:14 ` Chong Yidong
2006-08-17 15:09 ` Kim F. Storm
2006-08-17 17:21 ` Chong Yidong
2006-08-17 21:28 ` Kim F. Storm
2006-08-17 22:42 ` Chong Yidong
2006-08-17 16:05 ` martin rudalics
2006-08-17 21:33 ` Kim F. Storm
2006-08-18 9:03 ` martin rudalics
2006-08-18 9:26 ` Kim F. Storm
2006-08-20 13:54 ` Chong Yidong
2006-08-20 21:05 ` Kim F. Storm
2006-08-20 21:52 ` martin rudalics [this message]
2006-08-20 22:05 ` Kim F. Storm
2006-08-21 11:13 ` Richard Stallman
2006-08-21 11:45 ` Kim F. Storm
2006-08-21 16:14 ` Stefan Monnier
2006-08-21 17:18 ` martin rudalics
2006-08-22 1:40 ` Stefan Monnier
2006-08-22 7:42 ` Richard Stallman
2006-08-17 14:21 ` Chong Yidong
2006-08-18 15:47 ` Richard Stallman
2007-10-17 14:41 ` Juanma Barranquero
2007-10-18 5:02 ` Richard Stallman
2007-10-18 7:40 ` Juanma Barranquero
2007-10-23 7:13 ` Richard Stallman
2006-08-17 15:33 ` 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
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=44E8D9B6.6040700@gmx.at \
--to=rudalics@gmx.at \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=rms@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).