From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: copy-file: ok-if-already-exists versus mustbenew
Date: Mon, 15 May 2006 12:57:04 -0500 (CDT) [thread overview]
Message-ID: <200605151757.k4FHv4Ov014980@jane.dms.auburn.edu> (raw)
In-Reply-To: <4468A7A3.8060302@student.lu.se> (message from Lennart Borgman on Mon, 15 May 2006 18:09:07 +0200)
Lennart Borgman wrote:
I am trying to enhance my reading capabilities, but I can not understand
the difference between the arguments ok-if-already-exists and mustbenew
in the doc for `copy-file'. Can someone please explain this to me?
The only difference I see is that "never overwrite" is mentioned for
"mustbenew" - though I hope this holds for the first argument too.
I do not immediately see the difference either. mustbenew was
introduced by the following change:
2005-04-23 Richard M. Stallman <rms@gnu.org>
* fileio.c (Fcopy_file): New arg MUSTBENEW.
(Frename_file): Pass new arg to Fcopy_file.
I do not immediately understand why Frename_file could not have used
the ok-if-already-exists arg.
However it sounds like the second argument should be about modification
times, but the doc string does not say so.
I do not understand this one. I assume you mean the second _optional_
argument. From the docstring:
Fourth arg keep-time non-nil means give the output file the same
last-modified time as the old one. (This works on only some systems.)
Another problem is that the preserve-uid-gid arg is not mentioned in
the `(elisp)Changing Files' description of copy-file.
Sincerely,
Luc.
next prev parent reply other threads:[~2006-05-15 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 16:09 copy-file: ok-if-already-exists versus mustbenew Lennart Borgman
2006-05-15 17:57 ` Luc Teirlinck [this message]
2006-05-15 20:11 ` Lennart Borgman
2006-05-16 4:28 ` 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=200605151757.k4FHv4Ov014980@jane.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).