From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Chong Yidong <cyd@stupidchicken.com>,
Michael Olson <mwolson@gnu.org>,
Emacs Development Discussions <emacs-devel@gnu.org>
Subject: Re: Fixing dired hangs when NFS mount goes AWOL
Date: Fri, 07 Oct 2011 13:43:19 +0200 [thread overview]
Message-ID: <87sjn558o8.fsf@gmx.de> (raw)
In-Reply-To: <jwv7h4hbz9e.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 06 Oct 2011 17:18:30 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> Why would it break Tramp?
>> There was a very long discussion about, see
>> <http://thread.gmane.org/gmane.emacs.devel/87506/focus=87506>
>
> I know, I participated in that thread. I fail to see how it answers
> the question.
It was a more general discussion about changing the semantics of
file-remote-p. Caused by a similar problem (remote shares in MS Windows,
which are not responsive).
The discussion went into the direction, that maybe an opposite function,
file-local-p, might be useful. An interesting argument was given by
Andreas Schwab: what about mounted CD-ROMs, or USB devices? Are they
"local" or "remote".
>> Tramp uses file-remote-p internally. OK, this could be replaced by an
>> internal function.
>
> It depends on whether it uses it right or not.
Whatever is TRT. In this, we disagree.
>> Other packages use it as well, inside and outside core Emacs.
>
> What does it mean "use it as well"? In which way are those uses
> incompatible with a file-remote-p which returns non-nil for SSHFS and
> NFS mounts?
>
>> Not so important for basic file name operations, but needed for all
>> process related things.
>
> These are the uses which should use something like
> file-accessible-directory-p instead of file-remote-p, right?
A needed functionality is to translate between "local" file names (on
the remote host), and "remote" file names in the sense of Tramp. The
usual implementation is
local -> remote: (concat (file-remote-p default-directory) filename)
remote -> local: (file-remote-p filename 'localname)
> Stefan
Best regards, Michael.
next prev parent reply other threads:[~2011-10-07 11:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 18:50 Fixing dired hangs when NFS mount goes AWOL Michael Olson
2011-10-05 21:27 ` Chong Yidong
2011-10-05 21:59 ` Michael Olson
2011-10-05 22:14 ` Glenn Morris
2011-10-05 22:34 ` Michael Olson
2011-10-05 22:55 ` Glenn Morris
2011-10-05 23:14 ` Glenn Morris
2011-10-05 23:27 ` Michael Olson
2011-10-05 23:31 ` Michael Olson
2011-10-06 12:25 ` Stefan Monnier
2011-10-06 13:18 ` Michael Albinus
2011-10-06 13:25 ` Eli Zaretskii
2011-10-06 15:22 ` Stefan Monnier
2011-10-06 17:58 ` Michael Albinus
2011-10-06 21:18 ` Stefan Monnier
2011-10-07 11:43 ` Michael Albinus [this message]
2011-10-07 13:41 ` Stefan Monnier
2011-10-06 18:45 ` Michael Olson
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=87sjn558o8.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=mwolson@gnu.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).