Re: Tramp and file-precious-flag.

[Michael Albinus <michael.albinus@gmx.de>]

Luc Teirlinck <teirllm@dms.auburn.edu> writes:

> If `file-precious-flag' is t, then if one saves a remote file using
> Tramp, the visited file modtime gets set to 0.  As a result, there
> will be no warning when trying to save the buffer if the file changed
> on disk.  This problem does not exist for local files.

Somehow, I'm not able to reproduce the behaviour. Scenario:

C-x C-f ~/123
M-: file-precious-flag -> t
M-: (file-attributes (buffer-name (current-buffer)))
 -> (nil 1 1000 1000 (16634 52569) (16634 52242) (16634 52242) 125 "-rw-r--r--" nil 476194 770)
editing ... saving
M-: (file-attributes (buffer-name (current-buffer)))
 -> (nil 1 1000 1000 (16634 52660) (16634 52660) (16634 52660) 137 "-rw-r--r--" nil 476526 770)

C-x C-f /ssh:localhost:~/123
M-: file-precious-flag -> t
M-: (file-attributes (buffer-name (current-buffer)))
 -> (nil 1 1000 1000 (16634 52704) (16634 52660) (16634 52660) 137 "-rw-r--r--" t (7 . 17774) (-1 2))
editing ... saving
M-: (file-attributes (buffer-name (current-buffer)))
 -> (nil 1 1000 1000 (16634 52728) (16634 52728) (16634 52729) 118 "-rw-r--r--" t (7 . 17443) (-1 2))


> Sincerely,
>
> Luc.

Best regards, Michael.