[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: No longer accessible host paths
From: |
Michael Albinus |
Subject: |
Re: No longer accessible host paths |
Date: |
Thu, 14 Nov 2019 14:02:26 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
JD Smith <address@hidden> writes:
> Clarifying that: the culprit is the CONNECTED argument to
> `file-remote-p`. It’s easy for this to be nil while you still want to
> rename the host. So perhaps we shouldn’t require it to be CONNECTED.
But the CONNECTED argument doesn't influence, whether `file-remote-p'
gives you a valid result. It shall only prevent actions on the remote
host when not connected, like excercising `expand-file-name' and
friends. Or do I miss something?
Best regards, Michael.
- Re: No longer accessible host paths, (continued)
- Re: No longer accessible host paths, Michael Albinus, 2019/11/14
- Re: No longer accessible host paths, JD Smith, 2019/11/14
- Re: No longer accessible host paths, Michael Albinus, 2019/11/15
- Re: No longer accessible host paths, JD Smith, 2019/11/13
- Re: No longer accessible host paths, Michael Albinus, 2019/11/14
- Re: No longer accessible host paths, JD Smith, 2019/11/13
- Re: No longer accessible host paths,
Michael Albinus <=
- Re: No longer accessible host paths, yary, 2019/11/04
- Re: No longer accessible host paths, Michael Albinus, 2019/11/05