From: Santi Villalba <sdvillal@gmail.com>
To: Richard Riley <rileyrg@googlemail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-narrow-to-subtree and blocking call to accept-process-output with quit inhibited
Date: Mon, 18 Apr 2011 17:35:02 +0200 [thread overview]
Message-ID: <4DAC5A26.7010300@gmail.com> (raw)
In-Reply-To: <qbr58za9q7.fsf@news.eternal-september.org>
[-- Attachment #1: Type: text/plain, Size: 2504 bytes --]
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
<http://adamspiers.org/computing/elisp/smooth-scrolling.el> 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 both cases I find difficult to send you a test case without sending
my whole init files. Instructing emacs to start without loading the init
files and just enabling the scrolling policy or enabling flyspell by
hand are not enough to reproduce the problems. There must be some more
faulty interplay in my setup, if I find out I will let you know.
[-- Attachment #2: Type: text/html, Size: 3697 bytes --]
next prev parent reply other threads:[~2011-04-18 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 7:23 org-narrow-to-subtree and blocking call to accept-process-output with quit inhibited Santi Villalba
2011-04-18 12:00 ` Matt Lundin
2011-04-18 13:21 ` Santi Villalba
2011-04-18 14:28 ` Carsten Dominik
2011-04-18 14:57 ` Richard Riley
2011-04-18 15:35 ` Santi Villalba [this message]
2011-04-18 15:57 ` Santi Villalba
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=4DAC5A26.7010300@gmail.com \
--to=sdvillal@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rileyrg@googlemail.com \
/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).