From: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: Tramp and file-precious-flag.
Date: Sun, 25 Jul 2004 13:06:20 +0200 [thread overview]
Message-ID: <87smbgfis3.fsf@gmx.de> (raw)
In-Reply-To: <200407250224.i6P2OW728568@raven.dms.auburn.edu> (Luc Teirlinck's message of "Sat, 24 Jul 2004 21:24:32 -0500 (CDT)")
Luc Teirlinck <teirllm@dms.auburn.edu> 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.
next prev parent reply other threads:[~2004-07-25 11:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 19:34 Tramp and file-precious-flag Luc Teirlinck
2004-07-18 19:25 ` Michael Albinus
2004-07-18 19:51 ` Luc Teirlinck
2004-07-22 20:35 ` Michael Albinus
2004-07-23 1:12 ` Luc Teirlinck
2004-07-23 8:00 ` Michael Albinus
2004-07-24 1:54 ` Luc Teirlinck
2004-07-24 18:49 ` Michael Albinus
2004-07-25 2:24 ` Luc Teirlinck
2004-07-25 11:06 ` Michael Albinus [this message]
2004-07-24 3:02 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87smbgfis3.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.