From: Yuri Khan <yurivkhan@gmail.com>
To: emacs@alexander.shukaev.name
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Emacs Hangs on Filesystem Operations on Stale NFS
Date: Wed, 13 Jun 2018 19:35:23 +0700 [thread overview]
Message-ID: <CAP_d_8UDQzubBzE2zmzX-W+DDqPuaLv0AWWpGSgbE35WwMTQ+g@mail.gmail.com> (raw)
In-Reply-To: <1250e91f-c46a-68f8-d5f9-0c4f7e40a5a9@Alexander.Shukaev.name>
On Wed, Jun 13, 2018 at 5:46 PM Alexander Shukaev
<emacs@alexander.shukaev.name> wrote:
> […] the only
> way to time this case out reliably is to spawn a child which attempts to
> perform 'stat' and is then killed by the parent if timed out (similar to
> how 'lsof' does it). I'm sure such a complex technique would be
> unacceptable for Emacs.
Isn’t that what TRAMP does behind the scene, though?
next prev parent reply other threads:[~2018-06-13 12:35 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP_d_8UDQzubBzE2zmzX-W+DDqPuaLv0AWWpGSgbE35WwMTQ+g@mail.gmail.com \
--to=yurivkhan@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=emacs@alexander.shukaev.name \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.