From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: org-narrow-to-subtree and blocking call to accept-process-output with quit inhibited Date: Mon, 18 Apr 2011 16:28:10 +0200 Message-ID: References: <4DABE6DE.5090502@gmail.com> <878vv7u5u2.fsf@fastmail.fm> <4DAC3AC3.7090400@gmail.com> Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([140.186.70.92]:54162) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QBpR5-00013n-VN for emacs-orgmode@gnu.org; Mon, 18 Apr 2011 10:28:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QBpR1-00035D-BV for emacs-orgmode@gnu.org; Mon, 18 Apr 2011 10:28:19 -0400 Received: from mail-ew0-f41.google.com ([209.85.215.41]:58381) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QBpR1-000352-6k for emacs-orgmode@gnu.org; Mon, 18 Apr 2011 10:28:15 -0400 Received: by ewy9 with SMTP id 9so1517001ewy.0 for ; Mon, 18 Apr 2011 07:28:14 -0700 (PDT) In-Reply-To: <4DAC3AC3.7090400@gmail.com> 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: Santi Villalba Cc: Matt Lundin , emacs-orgmode@gnu.org On Apr 18, 2011, at 3:21 PM, Santi Villalba wrote: >=20 >>> Hi, >>>=20 >>> Whenever I invoke org-narrow-to-subtree, I receive a "blocking call = to >>> accept-process-output with quit inhibited" error, the buffer does = not >>> get narrowed down and I cannot edit or move anymore. I'm using a >>> bleeding-edge emacs 24.0.50.1 and org 7.4. >> Could you please upgrade to org-mode 7.5 and see if the problem = persists. > Done, no change. However, if I open emacs without reading the init = files, the problem disappears. So it is about the interaction of org = with something in my setup. >>> Does anybody know if the problem is it my setup or in a bug in org? >> Please provide a backtrace. >>=20 >> M-x toggle-debug-on-error > That should open a *Backtrace* buffer, right? It does not happen. >=20 > I will bisect my .emacs later on and let you know if I find the = incompatibility. >=20 > Santi >=20 I am willing to bet that this is something funny with bleeding edge = emacs. Narrowing to a subtree has no reason to call out to a process..... - Carsten - Carsten