From: Richard Riley <rileyrg@googlemail.com>
To: 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 16:57:04 +0200 [thread overview]
Message-ID: <qbr58za9q7.fsf@news.eternal-september.org> (raw)
In-Reply-To: BDE50083-C38A-485D-A4CD-7B1DE652E1FB@gmail.com
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.
next prev parent reply other threads:[~2011-04-18 14:58 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 [this message]
2011-04-18 15:35 ` Santi Villalba
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=qbr58za9q7.fsf@news.eternal-september.org \
--to=rileyrg@googlemail.com \
--cc=emacs-orgmode@gnu.org \
/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).