Re: No longer accessible host paths

[Michael Albinus]

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.