Re: No longer accessible host paths

[Michael Albinus]

Michael Albinus <address@hidden> writes:

Hi,

>>     - Now, the command goes through all buffers. Buffers which have a
>>      buffer-file-name starting with the old name, "/ssh:bad:/tmp/",
>>     are
>>      presented to me, plus the prompt "Set visited file name:
>>      /ssh:good:/var/tmp/". Confirming this with RET, sets the new
>>      name. This is editable, of course.
>>
>> Also confused here.  Is this not a new file but a *new* path to file?
>> I entered “file.txt” here, which was interpreted as a directory,
>> leading to auto-save errors for directory “file.txt/“.   If it is a
>> new file *path*, it seems redundant with the search-replace of the
>> longest common prefix string.
>
> Here I am undecided how to handle best. We have two options, call either
> `set-visited-file-name', or `write-file'. The former just changes the
> buffer's file name and marks the buffer as modified. The latter writes
> the buffer contents to the new location.
>
> I've decided for the first option, because it let you decide later,
> whether you need to save this file really, or whether it is not
> important enough to be saved somewhere else.
>
> I understand that the default UI of interactive `set-visited-file-name'
> is not convenient here. I will see whether I could write a wrapper
> around. At least, it calls for proper documentation.

I've reworked the docstring, and I've added also some phrases to the
Info manual. Since I'm notorious bad in writing proper documentation,
feedback is much appreciated!

Best regards, Michael.