From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daimrod Subject: bug#17484: 24.3.91; Emacs Pretest (emacs-24.3.91.tar.xz) freeze Date: Wed, 14 May 2014 12:34:32 +0900 Message-ID: <8761l958zb.fsf__38794.0779947259$1400038564$gmane$org@tanger.home> References: <87d2fiaxjw.fsf@tanger.home> <87tx8tajs5.fsf@tanger.home> <87r43x5fmm.fsf@tanger.home> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56716) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WkPyH-0000SV-Ew for emacs-orgmode@gnu.org; Tue, 13 May 2014 23:35:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WkPyB-0001pN-Ig for emacs-orgmode@gnu.org; Tue, 13 May 2014 23:35:09 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87r43x5fmm.fsf@tanger.home> (daimrod@gmail.com's message of "Wed, 14 May 2014 10:12:45 +0900") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: Stefan Monnier Cc: Carsten Dominik , 17484@debbugs.gnu.org Daimrod writes: > Stefan Monnier writes: > >>> 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). > > Well, `org-mks' (in `org-capture.el') sets `inhibit-quit' to T and is > called by `org-capture'. You were right, it's not a problem with `org-capture', I had a another freeze without using it. Here is the xbacktraces: gdb) xbacktrace "avl-tree-delete" (0xffff54b0) "byte-code" (0xffff55a0) "byte-code" (0xffff5760) "org-element--cache-process-request" (0xffff5990) "byte-code" (0xffff5aa0) "org-element--cache-sync" (0xffff5ce0) "org-element-at-point" (0xffff5e00) "byte-code" (0xffff60d0) "org-adaptive-fill-function" (0xffff6300) "fill-match-adaptive-prefix" (0xffff6480) "fill-context-prefix" (0xffff6620) "adaptive-wrap-fill-context-prefix" (0xffff67d0) "adaptive-wrap-prefix-function" (0xffff6a18) "run-hook-with-args" (0xffff6a10) 0x4d89f80 PVEC_COMPILED "funcall" (0xffff6b30) "jit-lock-fontify-now" (0xffff6e38) "jit-lock-function" (0xffff6fc8) "vertical-motion" (0xffffdca8) "end-of-visual-line" (0xffffde08) "call-interactively" (0xffffdfc0) "org-end-of-line" (0xffffe198) "call-interactively" (0xffffe350) "command-execute" (0xffffe478) I wonder if it is because `org-adaptive-fill-function' doesn't mix well with `adaptive-wrap-prefix-mode'... -- Daimrod/Greg