From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
Subject: bug#17484: 24.3.91; Emacs Pretest (emacs-24.3.91.tar.xz) freeze
Date: Tue, 13 May 2014 13:59:45 -0400
Message-ID: <jwv1tvxy357.fsf-monnier+emacsbugs@gnu.org>
References: <87d2fiaxjw.fsf@tanger.home>
	<jwvzjilygsq.fsf-monnier+emacsbugs@gnu.org>
	<87tx8tajs5.fsf@tanger.home>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:51815)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1WkGzw-0007Rj-4l
	for emacs-orgmode@gnu.org; Tue, 13 May 2014 14:00:23 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1WkGzo-0005iw-G9
	for emacs-orgmode@gnu.org; Tue, 13 May 2014 14:00:16 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.17484.B17484.140000399119378@debbugs.gnu.org>
In-Reply-To: <87tx8tajs5.fsf@tanger.home> (daimrod@gmail.com's message of
	"Tue, 13 May 2014 22:30:02 +0900")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Daimrod <daimrod@gmail.com>
Cc: Carsten Dominik <carsten@orgmode.org>, 17484@debbugs.gnu.org

> So, that's an org-mode bug, I'll try to see if I can reproduce it

Right: org-adaptive-fill-function should finish fairly promptly.

> (though I wonder why it uses `inhibit-quit' in the first place).

It's not org-mode which binds inhibit-quit but the C code that runs
jit-lock.  The C code binds inhibit-quit basically any time we run
"asynchronous code" (i.e. code run from redisplay, timers,
process-filters, ...) since the user usually doesn't really know that
such is running, so if she hits C-g she doesn't mean for it to interrupt
that code, but instead to do something else (e.g. get out of the
minibuffer).

The flip side is that all code run from jit/font-lock, process filters
and timers should be super extra careful to finish promptly and never
ever get into an inf-loop.


        Stefan