unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Alex V. Koval <alex@ua2web.com>
Cc: 11724@debbugs.gnu.org
Subject: bug#11724: 24.1; emacs freeze (full hang, ctrl+G or kill -15 do not help) on rope lucky assist
Date: Mon, 25 Jun 2012 03:21:06 -0400	[thread overview]
Message-ID: <20456.4450.155179.302614@gnu.org> (raw)
In-Reply-To: <20120625071537.2d6804df@avk-v131.local>


Alex V. Koval wrote (on Mon, 25 Jun 2012 at 07:15 +0300):

> Yes, I pretty well understand that point. 
> 
> But why emacs 24 hangs completely without reacting
> to C-g and other keys? I consider *this* to be emacs bug because it
> makes it impossible for me to debug the problem on Lisp level to
> properly report it to package maintainers as you suggest. 

I don't know, but I could imagine it being unavoidable in some cases
(like the perennial hanging NFS mount scenario, although that's not
the same thing I guess). We should keep the bug-list cc'd since
someone there may have an answer...

The doc of accept-process-output does say that it does not return
until there is some output. It doesn't mention quitting being
inhibited though. By experiment, it is not:

(setq proc (start-process "sleep" nil "sleep" "60"))

(accept-process-output proc)  ; C-g works fine


So I guess you may need to figure out exactly what the relevant
process is and what it is doing.






  parent reply	other threads:[~2012-06-25  7:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-16  6:36 bug#11724: 24.1; emacs freeze (full hang, ctrl+G or kill -15 do not help) on rope lucky assist Alex V. Koval
2012-06-25  0:59 ` Glenn Morris
     [not found]   ` <20120625071537.2d6804df@avk-v131.local>
2012-06-25  7:21     ` Glenn Morris [this message]
2012-06-25 14:51       ` Stefan Monnier
2015-12-25 23:16 ` Lars Ingebrigtsen
2016-02-29  5:31   ` Lars Ingebrigtsen

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=20456.4450.155179.302614@gnu.org \
    --to=rgm@gnu.org \
    --cc=11724@debbugs.gnu.org \
    --cc=alex@ua2web.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.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).