From mboxrd@z Thu Jan 1 00:00:00 1970 From: Santi Villalba Subject: Re: org-narrow-to-subtree and blocking call to accept-process-output with quit inhibited Date: Mon, 18 Apr 2011 17:57:10 +0200 Message-ID: <4DAC5F56.2040009@gmail.com> References: <4DABE6DE.5090502@gmail.com> <878vv7u5u2.fsf@fastmail.fm> <4DAC3AC3.7090400@gmail.com> <4DAC5A26.7010300@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------040101010006080804090102" Return-path: Received: from eggs.gnu.org ([140.186.70.92]:55532) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QBqrw-0002Jr-KZ for emacs-orgmode@gnu.org; Mon, 18 Apr 2011 12:00:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QBqrr-0002Zq-7c for emacs-orgmode@gnu.org; Mon, 18 Apr 2011 12:00:08 -0400 Received: from mail-ew0-f41.google.com ([209.85.215.41]:51718) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QBqrq-0002Yd-WB for emacs-orgmode@gnu.org; Mon, 18 Apr 2011 12:00:03 -0400 Received: by ewy9 with SMTP id 9so1563795ewy.0 for ; Mon, 18 Apr 2011 09:00:02 -0700 (PDT) In-Reply-To: <4DAC5A26.7010300@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: Richard Riley Cc: emacs-orgmode@gnu.org This is a multi-part message in MIME format. --------------040101010006080804090102 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 04/18/2011 05:35 PM, Santi Villalba wrote: > On 04/18/2011 04:57 PM, Richard Riley wrote: >> Carsten Dominik writes: >> >>> On Apr 18, 2011, at 3:21 PM, Santi Villalba wrote: >>> >>>>>> Hi, >>>>>> >>>>>> 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. >>>>> >>>>> M-x toggle-debug-on-error >>>> That should open a *Backtrace* buffer, right? It does not happen. >>>> >>>> I will bisect my .emacs later on and let you know if I find the incompatibility. >>>> >>>> Santi >>>> >>> 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 >>> >> That prompt/message is indeed something in emacs 24. Its been like it >> for ages and no sign yet of it being suppressed. > I should have reported two different issues: > > 1- The narrowing error was due to org not playing well with a couple > of customisations of the scrolling behavior. I substituted these two > lines with loading smooth-scrolling > and the > problem vanished. > (setq scroll-conservatively 10) > (setq scroll-margin 7) > A better description of the problem I had is: when narrowing into a > subtree with those settings, the window was getting frozen until I > pressed tab. It has nothing to do with the error message and now it is > fixed for me. > > 2- The "blocking blah blah blah" error - that is only annoying but has > no other bad consequences - happens when moving the point to/from the > beginning and the end of the buffer in org-mode. It disappears when I > disable flyspell-mode. In fact, forget about issue 2), as it happens in non-org buffers as well (in fact, that annoying message appears each time flyspell is invoked after a moving the point). Sorry for the bad reporting! --------------040101010006080804090102 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 04/18/2011 05:35 PM, Santi Villalba wrote:
On 04/18/2011 04:57 PM, Richard Riley wrote: 
Carsten Dominik <carsten.dominik@gmail.com> writes:


On Apr 18, 2011, at 3:21 PM, Santi Villalba wrote:


Hi,

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.

M-x toggle-debug-on-error

That should open a *Backtrace* buffer, right? It does not happen.

I will bisect my .emacs later on and let you know if I find the incompatibility.

Santi


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


That prompt/message is indeed something in emacs 24. Its been like it
for ages and no sign yet of it being suppressed.
I should have reported two different issues:

1- The narrowing error was due to org not playing well with a couple of customisations of the scrolling behavior. I substituted these two lines with loading smooth-scrolling and the problem vanished.
    (setq scroll-conservatively 10)
   (setq scroll-margin 7)
A better description of the problem I had is: when narrowing into a subtree with those settings, the window was getting frozen until I pressed tab. It has nothing to do with the error message and now it is fixed for me.

2- The "blocking blah blah blah" error - that is only annoying but has no other bad consequences - happens when moving the point to/from the beginning and the end of the buffer in org-mode. It disappears when I disable flyspell-mode.
In fact, forget about issue 2), as it happens in non-org buffers as well (in fact, that annoying message appears each time flyspell is invoked after a moving the point). Sorry for the bad reporting!

--------------040101010006080804090102--