From: Chong Yidong <cyd@stupidchicken.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Nested sit-for's
Date: Thu, 17 Aug 2006 10:14:53 -0400 [thread overview]
Message-ID: <87hd0bjvoi.fsf@furball.mit.edu> (raw)
In-Reply-To: <m3y7tnfw9o.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Thu, 17 Aug 2006 13:15:47 +0200")
storm@cua.dk (Kim F. Storm) writes:
>> It would work to have ONE timer that does sit-for if we make a rule
>> that no others can do so. We could define jit-lock as this one
>> exception. (This has the advantage of not involving any change in the
>> code, just comments and the Lisp Manual.)
>
> I agree with your analysis.
>
> But, IMO, if we make it a rule that timers should generally not use
> sit-for, then a central function like jit-lock should definitely not
> use sit-for!
If we simply document that "timers (and process filters) should avoid
using sit-for", it should be clear to the reader that rare exceptions
may exist (especially if we add a comment to jit-lock-stealth-fontify
stating this). After the release, we can probably rework
jit-lock-stealth-fontify to avoid using sit-for, but I don't think the
current situation is bad enough to block the release.
OTOH, I don't remember any other timers or process filters in the
Emacs tree that use a long sit-for or loop waiting for input. Anyone
know of any?
next prev parent reply other threads:[~2006-08-17 14:14 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hd0bjvoi.fsf@furball.mit.edu \
--to=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 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.