From: Daimrod <daimrod@gmail.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Carsten Dominik <carsten@orgmode.org>, 17484@debbugs.gnu.org
Subject: bug#17484: 24.3.91; Emacs Pretest (emacs-24.3.91.tar.xz) freeze
Date: Wed, 14 May 2014 10:12:45 +0900 [thread overview]
Message-ID: <87r43x5fmm.fsf@tanger.home> (raw)
In-Reply-To: <jwv1tvxy357.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Tue, 13 May 2014 13:59:45 -0400")
Stefan Monnier <monnier@IRO.UMontreal.CA> 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'.
I have found 7 places were `inhibit-quit' was set to T in org-mode.
> 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.
I can see why. :)
--
Daimrod/Greg
next prev parent reply other threads:[~2014-05-14 1:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87d2fiaxjw.fsf@tanger.home>
[not found] ` <jwvzjilygsq.fsf-monnier+emacsbugs@gnu.org>
[not found] ` <87tx8tajs5.fsf@tanger.home>
2014-05-13 17:59 ` bug#17484: 24.3.91; Emacs Pretest (emacs-24.3.91.tar.xz) freeze Stefan Monnier
2014-05-14 1:12 ` Daimrod [this message]
2014-05-14 3:34 ` Daimrod
2014-05-15 9:58 ` Bastien
[not found] ` <8738gbtlce.fsf@bzg.ath.cx>
2014-05-15 10:11 ` Daimrod
[not found] ` <87d2ff1hcw.fsf__9581.27144626833$1400148801$gmane$org@tanger.home>
2014-05-15 10:23 ` Bastien
[not found] ` <878uq3s5lf.fsf@bzg.ath.cx>
2014-05-15 12:30 ` Daimrod
[not found] ` <8761l958zb.fsf@tanger.home>
2014-05-14 13:37 ` Stefan Monnier
[not found] ` <jwvk39owkip.fsf-monnier+emacsbugs@gnu.org>
2014-05-14 14:47 ` Daimrod
2014-05-14 16:52 ` Stefan Monnier
2014-05-29 2:52 ` Daimrod
2014-05-29 4:07 ` Stefan Monnier
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r43x5fmm.fsf@tanger.home \
--to=daimrod@gmail.com \
--cc=17484@debbugs.gnu.org \
--cc=carsten@orgmode.org \
--cc=monnier@IRO.UMontreal.CA \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).