From: Chong Yidong <cyd@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Recent keyboard changes breaks quitting
Date: Sun, 23 Sep 2012 14:05:40 +0800 [thread overview]
Message-ID: <87sja91dfv.fsf@gnu.org> (raw)
In-Reply-To: <83mx0hjsl5.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 23 Sep 2012 06:01:10 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Nope. Turning off font-lock mode does, but I think this is only because
>> font-lock is is the only thing in my Emacs running an idle timer, in
>> this case jit-lock-context-fontify. If I add any idle timer manually
>> (unrelated to font-lock), the same quitting problem appears.
>
> Hmm... so what idle timer runs when blink-cursor-mode is disabled?
I just told you: jit-lock-context-fontify.
But it's not a misbehaving idle timer, if that's what you're wondering
about. It is possible to reproduce the bug when *any* idle timer is
around, e.g. putting this in the init file
(global-font-lock-mode 0)
(defun foo-timer-fun (&rest ignored)
(message "%d" foo))
and running
M-: (run-with-idle-timer 2 nil #'foo-timer-fun) RET
M-x C-g
My attempts at tracing indicate that your timer_check change causes
significant changes in wait_reading_process_output's order of execution
when there is an idle timer present. I think the problem occurs in the
call in process.c:110145, with
wait_reading_process_output
-> detect_input_pending_run_timers
-> get_input_pending
-> readable_events
-> timer_check
This timer_check does not call process_pending_signals. Now, the same
call to timer_check does call process_pending_signals, apparently via
the QUIT macro. Not sure if this helps.
next prev parent reply other threads:[~2012-09-23 6:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 14:51 Recent keyboard changes breaks quitting Chong Yidong
2012-09-22 16:11 ` Eli Zaretskii
2012-09-22 17:20 ` Chong Yidong
2012-09-22 17:29 ` Jan Djärv
2012-09-22 17:35 ` Chong Yidong
2012-09-22 18:56 ` Eli Zaretskii
2012-09-22 19:06 ` Eli Zaretskii
2012-09-23 2:53 ` Chong Yidong
2012-09-23 4:01 ` Eli Zaretskii
2012-09-23 6:05 ` Chong Yidong [this message]
2012-09-23 8:33 ` Chong Yidong
2012-09-23 16:50 ` Eli Zaretskii
2012-09-22 19:27 ` Eli Zaretskii
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=87sja91dfv.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=eliz@gnu.org \
--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.