From: Andreas Schwab <schwab@suse.de>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: Bug in copy-file
Date: Fri, 31 Jan 2003 12:18:05 +0100 [thread overview]
Message-ID: <jefzr9r2j6.fsf@sykes.suse.de> (raw)
In-Reply-To: <3E3A278D.905@math.ku.dk> (Lars Hansen's message of "Fri, 31 Jan 2003 08:36:45 +0100")
Lars Hansen <larsh@math.ku.dk> writes:
|> Andreas Schwab wrote:
|>
|> >Lars Hansen <larsh@math.ku.dk> writes:
|> >
|> >|> A bug has been introduced since Emacs 21.2.
|> >|> A "!" has been added where it should not be.
|> >|> As a consequence the keep-time parameter functions
|> >|> opposite of what is intended. The patch below
|> >|> should fix the problem.
|> >
|> >Why do you think so? The use of keep-time is correct according to the
|> >doc string.
|> >
|> >Andreas.
|> >
|> Maybe I am misreading the code or the doc string. I read them like this:
|> Doc string says:
|>
|> Fourth arg KEEP-TIME non-nil means give the new file the same
|> last-modified time as the old one.
|>
|> But when keep_time is non-nil, NILP (keep_time) is false, so !NILP
|> (keep_time)
|> is true. Thus the code following if (NILP (keep_time)) is entered. In
|> this code it
|> reads
|>
|> EMACS_GET_TIME (now);
|>
|> and
|>
|> if (set_file_times (filename, now, now))
|>
|> so the time is set to now, not kept.
|>
|> Am I wrong?
No, you are right. I didn't know that windows is backwards.
|> By the way, it is easy to test: Just do eg:
You first need to install a proprietary operating system, which is a very
difficult and expensive part.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2003-01-31 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 16:30 Bug in copy-file Lars Hansen
2003-01-30 17:28 ` Andreas Schwab
2003-01-31 7:36 ` Lars Hansen
2003-01-31 11:18 ` Andreas Schwab [this message]
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=jefzr9r2j6.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=bug-gnu-emacs@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.