From: Bill Benedetto <bbenedetto@goodyear.com>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: Emacs 29 and Tramp and Remote Dired confusion
Date: Fri, 7 Jul 2023 14:42:14 +0000 [thread overview]
Message-ID: <DM4PR18MB4191300A8DD671A5398F197DB92DA@DM4PR18MB4191.namprd18.prod.outlook.com> (raw)
In-Reply-To: <83h6qfg94a.fsf@gnu.org>
Great idea!
Remembering that this is emacs 29.
1. emacs -Q
2. C-x C-f
3. /ssh:me@remotemachine:.
4. C-x 1
5. C (dired-do-copy)
6. type a new name for the target file and hit <return>
The new file will have the current timestamp instead of the original timestamp.
In previous versions of emacs/tramp, it would have the original timestamp.
I also checked dired-copy-preserve-time and it is t in both versions that I am testing (28 and 29 pretest 29.0.92)
Is this any clearer?
-Bill
-----Original Message-----
From: help-gnu-emacs-bounces+bbenedetto=goodyear.com@gnu.org <help-gnu-emacs-bounces+bbenedetto=goodyear.com@gnu.org> On Behalf Of Eli Zaretskii
Sent: Friday, July 7, 2023 9:11 AM
To: help-gnu-emacs@gnu.org
Subject: Re: [EXT] Re: Emacs 29 and Tramp and Remote Dired confusion
> From: Bill Benedetto <bbenedetto@goodyear.com>
> CC: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
> Date: Fri, 7 Jul 2023 12:58:55 +0000
>
> If I do like you said, copy from a remote to a local dired, it does retain the timestamp.
> And if I copy from a remote to a different remote dired, the timestamp is still retained.
>
> But if I copy within the same remote dired to a new name within that same remote dired, the timestamp changes.
> (Like to make a backup copy of the original file.)
What do you mean by "that same remote dired"? What is "the same" in this case?
How about showing a complete recipe, starting from "emacs -Q" and showing all the commands and key sequences you type to reproduce the problem?
next prev parent reply other threads:[~2023-07-07 14:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 12:14 Emacs 29 and Tramp and Remote Dired confusion Bill Benedetto
2023-07-07 12:39 ` Michael Albinus
2023-07-07 12:58 ` [EXT] " Bill Benedetto
2023-07-07 13:10 ` Eli Zaretskii
2023-07-07 14:42 ` Bill Benedetto [this message]
2023-07-07 17:30 ` Michael Albinus
2023-07-07 17:57 ` Bill Benedetto
2023-07-08 13:50 ` Michael Albinus
2023-07-10 11:23 ` Bill Benedetto
2023-07-07 13:05 ` Eli Zaretskii
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=DM4PR18MB4191300A8DD671A5398F197DB92DA@DM4PR18MB4191.namprd18.prod.outlook.com \
--to=bbenedetto@goodyear.com \
--cc=help-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.
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).