From: Andreas Seltenreich <seltenreich@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: Did something change with respect to Emacs idle loop:
Date: Wed, 27 Sep 2006 19:53:43 +0200 [thread overview]
Message-ID: <87u02tyz4o.fsf@gate450.dyndns.org> (raw)
In-Reply-To: <17690.30733.861253.884984@gargle.gargle.HOWL> (T. V. Raman's message of "Wed\, 27 Sep 2006 06\:09\:33 -0700")
[fontification loop vs. subprocesses]
"T. V. Raman" <raman@users.sf.net> writes:
> This does sound like it could be the culprit ---
> I'd be happy to test if it were possible to do a cvs update, and
> then undo just this patch and build.
An easy way to confirm it might be toggling global-font-lock-mode. If
my guess was right, the symptoms should correlate with that setting.
The last version of jit-lock.el that has the problem is 1.56. So,
cvs up -r 1.56 lisp/jit-lock.el
should show the symptoms, while
cvs up -A lisp/jit-lock.el
doesn't. Note that the file is dumped into Emacs, so besides
byte-compiling it, you'd have to either dump a new emacs or explicitly
load the file for the changes to take effect.
regards,
andreas
next prev parent reply other threads:[~2006-09-27 17:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 3:20 Did something change with respect to Emacs idle loop: T. V. Raman
2006-09-21 3:47 ` T. V. Raman
2006-09-21 13:58 ` Romain Francoise
2006-09-22 1:11 ` T. V. Raman
2006-09-22 18:08 ` Romain Francoise
2006-09-22 4:11 ` Richard Stallman
2006-09-22 19:21 ` Chong Yidong
2006-09-23 17:55 ` T. V. Raman
2006-09-24 2:10 ` Richard Stallman
2006-09-24 15:49 ` joakim
2006-09-24 18:00 ` T. V. Raman
2006-09-25 3:17 ` Richard Stallman
2006-09-24 17:58 ` T. V. Raman
2006-09-25 20:48 ` Richard Stallman
2006-09-27 13:08 ` T. V. Raman
2006-09-28 2:14 ` Richard Stallman
2006-09-23 18:01 ` Richard Stallman
2006-09-26 17:49 ` Andreas Seltenreich
2006-09-27 13:09 ` T. V. Raman
2006-09-27 17:53 ` Andreas Seltenreich [this message]
2006-09-28 3:46 ` T. V. Raman
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=87u02tyz4o.fsf@gate450.dyndns.org \
--to=seltenreich@gmx.de \
--cc=emacs-devel@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.