unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: kzeitler@lucent.com, emacs-devel@gnu.org, klaus.berndl@sdm.de
Subject: Re: AW: AW: AW: Can't interrupt directory_files_internalrunfromtimer-event-handler
Date: Sun, 14 Aug 2005 02:47:09 -0400	[thread overview]
Message-ID: <m1slxdowcs.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1E3ffn-0007jK-Sv@fencepost.gnu.org> (Richard M. Stallman's message of "Fri, 12 Aug 2005 15:58:35 -0400")

> I looked at the code for directory-files, and it seems you cannot quit
> out of it while it is waiting in a system call.

Why is that?

> It is probably possible to implement quitting out of the system call
> in directory-files.  Doing this requires setting immediate_quit to 1,
> at least while that system call is running.

Looking at this code made me notice that the filename completion doesn't
handle the EAGAIN case like directory-files does.  And also that
directory-files doesn't check QUIT if it had been interrupted, which can
fail to react to C-g in cases such as SYNC_INPUT.
So I've installed the patch below.

> Which system call takes the long time?  Is it opendir, or readdir?

If the NFS server is down, I suspect that either call can stall.


        Stefan


--- dired.c	11 aoû 2005 05:27:35 -0400	1.117
+++ dired.c	14 aoû 2005 02:44:01 -0400	
@@ -224,7 +224,7 @@
 
 #ifdef EAGAIN
       if (dp == NULL && errno == EAGAIN)
-	continue;
+	{ QUIT; continue; }
 #endif
 
       if (dp == NULL)
@@ -533,6 +533,10 @@
 	  dp = (*readfunc) (d);
 #else
 	  dp = readdir (d);
+#endif
+#ifdef EAGAIN
+	  if (dp == NULL && errno == EAGAIN)
+	    { QUIT; continue; }
 #endif
 	  if (!dp) break;
 

      reply	other threads:[~2005-08-14  6:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-12  8:16 AW: AW: AW: Can't interrupt directory_files_internalrunfromtimer-event-handler klaus.berndl
2005-08-12 19:58 ` Richard M. Stallman
2005-08-14  6:47   ` 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=m1slxdowcs.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=klaus.berndl@sdm.de \
    --cc=kzeitler@lucent.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).