From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Yagnesh Raghava Yakkala <hi@yagnesh.org>
Cc: 11868@debbugs.gnu.org
Subject: bug#11868: 24.1.50; [python-mode] Blocking call to accept-process-output with quit inhibited!! (message buffer)
Date: Thu, 12 Jul 2012 20:17:42 -0400 [thread overview]
Message-ID: <jwva9z4ldqw.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87vchs27gd.fsf@yagnesh.org> (Yagnesh Raghava Yakkala's message of "Fri, 13 Jul 2012 02:52:02 +0900")
>>> with some trail and error, the following patch is suppressing the warning.
>>
>> Thank you for your attempt at finding a patch that works. The problem
>> is that the warning is there to indicate that there is a "fundamental"
>> problem, and your patch mostly hides the problem. Maybe it actually
>> solves it, but maybe not.
>> It depends on whether the surrounding code is prepared to deal with
>> accept-process-output being interrupted by quit.
>> IOW, we have to either find or create a place where the code is prepared
>> to handle an interruption by quit.
> I could understand what you are saying, but have no clue what to do
> further. It would be great if you can guide me to the next step to
> resolve the issue.
Maybe python.el's maintainer will be better placed for that.
But basically, what is needed is to think first about what should happen
if the user hits C-g in the middle of this accept-process-output: what
can the user mean by that (there might be various cases), what should
the resulting behavior be, and then how to change the code to get
that result.
E.g. a typical problematic issues is the state of the process: the
process will presumably keep running, so what will happen next time
python.el wants to send it more commands?
I don't know enough about python.el's code to be able to answer.
Stefan
prev parent reply other threads:[~2012-07-13 0:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 17:12 bug#11868: 24.1.50; [python-mode] Blocking call to accept-process-output with quit inhibited!! (message buffer) Yagnesh Raghava Yakkala
2012-07-06 17:39 ` Glenn Morris
2012-07-10 17:08 ` Yagnesh Raghava Yakkala
2012-07-10 18:18 ` Yagnesh Raghava Yakkala
2012-07-10 22:58 ` Stefan Monnier
2012-07-12 17:52 ` Yagnesh Raghava Yakkala
2012-07-13 0:17 ` Stefan Monnier [this message]
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwva9z4ldqw.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=11868@debbugs.gnu.org \
--cc=hi@yagnesh.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.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).