Re: Tramp and file-precious-flag.

[Michael Albinus]

Luc Teirlinck <address@hidden> writes:

> When I create a new file with `file-precious-flag' eq t, using Tramp
> (ssh), then initially `visited-file-modtime' now returns (-1 65535).
> That is good.  However, when I then make changes and save them, the
> return value after that is _still_ (-1 65535).  As a result, when I
> try to make changes, I get warned that the file has changed on disk.
> Only when I save the file for the _second_ time does it get a "real"
> modtime, after which everything works normally.

The problem was that Tramp tried to examine the modtime of the file
the buffer is visiting. But this file is different from the file to
be saved in case `file-precious-flag' equals t, so Tramp is failing
(still believing the file does not exists yet).

I've changed it such a way that `set-visited-file-modtime' passes the
modtime of the file just saved as parameter. Committed to Tramp CVS,
branch "branch-2-0-stable".

> Sincerely,
>
> Luc.

Thanx a lot for your testing, and best regards, Michael.