From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>,
Alexander Shukaev <emacs@alexander.shukaev.name>
Cc: schwab@suse.de,
emacs-devel-bounces+emacs=alexander.shukaev.name@gnu.org,
npostavs@gmail.com, emacs-devel@gnu.org
Subject: Re: Emacs Hangs on Filesystem Operations on Stale NFS
Date: Wed, 13 Jun 2018 08:40:45 -0700 [thread overview]
Message-ID: <0f636e2a-6ac7-221a-dbc5-d11b197e39f8@cs.ucla.edu> (raw)
In-Reply-To: <83efhdqq28.fsf@gnu.org>
Eli Zaretskii wrote:
> I'd be much happier if we could interrupt such hangs,
> e.g. by C-g, as Stefan points out (on a TTY frame, this should already
> be possible in many cases, since C-g there generates SIGINT). But I'm
> not sure this would be possible in general. Maybe Paul will have some
> ideas.
I agree with you. Luckily, it appears that there's nothing Emacs can practically
do to address this question for NFS mounts in general, so we needn't worry about
this for Emacs in particular.
next prev parent reply other threads:[~2018-06-13 15:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 10:27 Emacs Hangs on Filesystem Operations on Stale NFS Alexander Shukaev
2018-06-11 11:01 ` Andreas Schwab
2018-06-11 11:05 ` Alexander Shukaev
2018-06-11 11:50 ` Andreas Schwab
2018-06-11 12:03 ` Alexander Shukaev
2018-06-11 11:55 ` Alexander Shukaev
2018-06-11 11:59 ` Noam Postavsky
2018-06-11 12:11 ` Alexander Shukaev
2018-06-11 12:20 ` Noam Postavsky
2018-06-11 12:22 ` Alexander Shukaev
2018-06-11 12:34 ` Noam Postavsky
2018-06-11 12:41 ` Alexander Shukaev
2018-06-11 12:40 ` Andreas Schwab
2018-06-11 12:46 ` Alexander Shukaev
2018-06-11 15:51 ` Eli Zaretskii
2018-06-13 15:40 ` Paul Eggert [this message]
2018-06-12 17:26 ` Davis Herring
2018-06-12 18:26 ` Perry E. Metzger
2018-06-11 15:04 ` Stefan Monnier
2018-06-11 16:46 ` Mike Kupfer
2018-06-11 17:08 ` Stefan Monnier
2018-06-13 10:45 ` Alexander Shukaev
2018-06-13 12:35 ` Yuri Khan
2018-06-13 14:23 ` Stefan Monnier
2018-06-13 15:30 ` Yuri Khan
2018-06-13 18:09 ` Michael Albinus
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=0f636e2a-6ac7-221a-dbc5-d11b197e39f8@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel-bounces+emacs=alexander.shukaev.name@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=emacs@alexander.shukaev.name \
--cc=npostavs@gmail.com \
--cc=schwab@suse.de \
/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).