From: Dmitry Gutov <dgutov@yandex.ru>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 27036@debbugs.gnu.org
Subject: bug#27036: 25.1; Blocking call to accept-process-output with quit inhibited!!
Date: Fri, 26 May 2017 03:38:09 +0300 [thread overview]
Message-ID: <96510a73-d838-31ce-04fa-c9d3ca4b970e@yandex.ru> (raw)
In-Reply-To: <CAM-tV-9r0a1r6DBgjkHszbO29-ZQDCzM1aVyBHTLwBeoAtKZ+A@mail.gmail.com>
On 5/25/17 3:51 PM, Noam Postavsky wrote:
> Looks like it's in timer-event-handler:
>
> (defun timer-event-handler (timer)
> ...
> (let ((inhibit-quit t))
Oh. Thanks! Somehow I skipped over this also being implemented in Lisp.
So apparently timer functions are not allowed to signal quit.
next prev parent reply other threads:[~2017-05-26 0:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 12:20 bug#27036: 25.1; Blocking call to accept-process-output with quit inhibited!! Francesco Potortì
2017-05-24 12:24 ` Dmitry Gutov
2017-05-24 18:01 ` Eli Zaretskii
2017-05-24 18:17 ` Dmitry Gutov
2017-05-24 19:05 ` Eli Zaretskii
2017-05-25 12:43 ` Dmitry Gutov
2017-05-25 12:51 ` Noam Postavsky
2017-05-25 16:14 ` Eli Zaretskii
2017-05-26 1:02 ` Dmitry Gutov
2017-05-26 6:07 ` Eli Zaretskii
2017-05-26 0:38 ` Dmitry Gutov [this message]
[not found] ` <handler.27036.B.1495542030639.ack@debbugs.gnu.org>
2017-05-24 11:21 ` bug#27036: Acknowledgement (25.1; Blocking call to accept-process-output with quit inhibited!!) Francesco Potortì
2017-05-24 14:27 ` Francesco Potortì
2017-05-24 17:57 ` Eli Zaretskii
2017-05-25 15:58 ` Francesco Potortì
2017-05-26 0:41 ` Dmitry Gutov
2017-05-26 13:17 ` Francesco Potortì
2017-05-27 0:22 ` Dmitry Gutov
2017-05-30 7:46 ` Francesco Potortì
2017-05-30 22:39 ` Dmitry Gutov
2017-09-28 21:06 ` Dmitry Gutov
2017-09-29 7:03 ` Francesco Potortì
2022-04-23 15:24 ` bug#27036: 25.1; Blocking call to accept-process-output with quit inhibited!! Lars Ingebrigtsen
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=96510a73-d838-31ce-04fa-c9d3ca4b970e@yandex.ru \
--to=dgutov@yandex.ru \
--cc=27036@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
/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.