unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Tramp and file-precious-flag.
Date: Thu, 22 Jul 2004 20:12:00 -0500 (CDT)	[thread overview]
Message-ID: <200407230112.i6N1C0C13413@raven.dms.auburn.edu> (raw)
In-Reply-To: <87k6wvixuu.fsf@gmx.de> (message from Michael Albinus on Thu, 22 Jul 2004 22:35:37 +0200)

Michael Albinus wrote:

   In fact, the problem was due to documentation vagueness of
   `write-region'. It is said, that modtime of visited file must be
   updated in case `visit' is equal t. Nothing is said if `visit' is a
   string. But the code of `write-region' shows it must be updated always
   when `visit' is not nil.

Do you really mean "always when `visit' is not nil" or do you mean
"when `visit' is t or a string":

If visit is neither t nor nil nor a string,
  that means do not display the "Wrote file" message.

   Is it worth a documentation clarification?

Probably it might be good to clarify the docstring and the Elisp
manual, as long as it really makes things more clear.

Docstring:

    Optional fifth argument VISIT if t means
      set the last-save-file-modtime of buffer to this file's modtime
      and mark buffer not modified.
    If VISIT is a string, it is a second file name; the output goes to
      FILENAME, but the buffer is marked as visiting VISIT.  VISIT is also
      the file name to lock and unlock for clash detection.

In the case of a string, one would have to specify which file's
modtime, because there is FILENAME and VISIT.  I guess the buffer also
gets marked not modified (I did not check).

Sincerely,

Luc.

  reply	other threads:[~2004-07-23  1:12 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 [this message]
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
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200407230112.i6N1C0C13413@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).