Re: Tramp file modification time for not yet existing files.

[Luc Teirlinck]

Kai Grossjohann wrote:

   Luc Teirlinck <address@hidden> writes:

   > If one creates a buffer visiting a not yet existing file on a remote
   > machine using Tramp, then `visited-file-modtime' originally (before
   > the file is saved) returns 0.  The return value for local files in
   > the same situation is (-1 65535), that is, -1.

   I'm afraid that I'm just before a deadline at work at the moment, so
   if you already know what needs to happen, it would be wonderful if
   you could just do it.  Since the stable Tramp branch and Emacs are
   now in sync, it will be easy to merge changes.

I will take a look at it.

   What confuses me most is your wording of "setting the modtime".

(tramp-handle-set-visited-file-modtime '(-1 65535))

   I think Tramp now uses (0 0) for those cases.

   Does Ange-FTP need a similar change?  Tramp uses (0 0) as a dont-know
   value because Ange-FTP does it, and I didn't understand the issues at
   that time.

The problem is that it makes `visited-file-modtime' return 0 and then
`verify-visited-file-modtime' will *never* warn, even though there are
situations where it should.  I will take a look at Ange-FTP.

Sincerely,

Luc.