[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: No longer accessible host paths
From: |
JD Smith |
Subject: |
Re: No longer accessible host paths |
Date: |
Thu, 14 Nov 2019 19:14:56 -0500 |
One more small bug I discovered when changing networks. In
`tramp-rename-read-file-name-dir`, `file-remote-p` returns nil when you are
truly disconnected, since the CONNECTED argument is t. This signals an error
on rename. The connection doesn’t persist for bad hosts. Probably safe to
make CONNECTED nil.
JD
- 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/15
- Re: No longer accessible host paths, Michael Albinus, 2019/11/16
- Message not available
- Re: No longer accessible host paths, Michael Albinus, 2019/11/16
- Re: No longer accessible host paths, JD Smith, 2019/11/16
- Re: No longer accessible host paths, JD Smith, 2019/11/17
- Re: No longer accessible host paths, Michael Albinus, 2019/11/18
- Re: No longer accessible host paths, Michael Albinus, 2019/11/14
- Re: No longer accessible host paths,
JD Smith <=
- 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, 2019/11/14
- Re: No longer accessible host paths, yary, 2019/11/04
- Re: No longer accessible host paths, Michael Albinus, 2019/11/05