From: Tassilo Horn <tsdh@gnu.org>
To: Rudi C <rudiwillalwaysloveyou@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
stefankangas@gmail.com, emacs-devel@gnu.org
Subject: Re: PR: dired-do-create-files now checks for trailing slashes in the target
Date: Wed, 29 Sep 2021 15:37:08 +0200 [thread overview]
Message-ID: <87v92j33g2.fsf@gnu.org> (raw)
In-Reply-To: <CAE9z9A1NMnF0XPX=3XkGg9RS-9vJnxHX35AOXYi1uJHxweWG5w@mail.gmail.com>
Rudi C <rudiwillalwaysloveyou@gmail.com> writes:
>> how do I rename old_name into new_name so that it overwrites new_name
>
> Overwriting a directory is a highly destructive activity. It would be
> better to make the user explicitly delete the old directory, and then
> do the rename IMO.
I would agree. And while it could made work for the target being an
empty directory, hopefully nobody will assume this to be a sensible
operation if the target is a non-empty directory.
> But we can add a new custom variable. I am all for giving everyone
> options. I don't think it can integrate with
> `dired-create-destination-dirs' though;
> `dired-create-destination-dirs-trailing-slash-special'?
Have a look at my reply to Eli. AFAICS, dired doesn't overwrite a
directory even without your patch when you rename a directory foo to bar
which already exists. It also moves foo into bar.
So from my POV, no new defcustom is needed.
Bye,
Tassilo
next prev parent reply other threads:[~2021-09-29 13:37 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 17:50 PR: dired-do-create-files now checks for trailing slashes in the target Rudi C
2021-09-28 18:17 ` Stefan Kangas
2021-09-28 18:42 ` Rudi C
2021-09-28 19:03 ` Stefan Kangas
2021-09-28 19:38 ` Tassilo Horn
2021-09-28 20:07 ` Stefan Kangas
2021-09-28 20:23 ` Rudi C
2021-09-28 18:42 ` Eli Zaretskii
2021-09-28 19:29 ` Tassilo Horn
2021-09-28 19:55 ` Eli Zaretskii
2021-09-29 4:46 ` Tassilo Horn
2021-09-29 13:09 ` Eli Zaretskii
2021-09-29 13:20 ` Rudi C
2021-09-29 13:34 ` Eli Zaretskii
2021-09-29 13:37 ` Tassilo Horn [this message]
2021-09-29 13:42 ` Stefan Kangas
2021-09-29 13:53 ` Tassilo Horn
2021-09-29 14:31 ` Rudi C
2021-09-29 13:23 ` Tassilo Horn
2021-09-29 13:41 ` Eli Zaretskii
2021-09-29 13:42 ` Tassilo Horn
2021-09-29 13:57 ` Eli Zaretskii
2021-09-29 14:21 ` Lars Ingebrigtsen
2021-09-29 15:04 ` Stefan Kangas
2021-09-29 15:17 ` Tassilo Horn
2021-09-30 6:06 ` Lars Ingebrigtsen
2021-09-30 7:29 ` Lars Ingebrigtsen
2021-09-30 8:32 ` Tassilo Horn
2021-09-30 13:33 ` Lars Ingebrigtsen
2021-09-30 14:10 ` Tassilo Horn
2021-09-30 16:03 ` Eli Zaretskii
2021-09-30 16:48 ` Tassilo Horn
2021-09-30 17:47 ` Eli Zaretskii
2021-09-30 18:52 ` Rudi C
2021-09-30 19:02 ` Eli Zaretskii
2021-11-01 15:37 ` Rudi C
2021-11-02 14:44 ` Lars Ingebrigtsen
2021-11-02 15:08 ` Rudi C
2021-11-02 15:15 ` Eli Zaretskii
2021-11-09 12:52 ` Rudi C
2021-11-09 13:47 ` Eli Zaretskii
2021-12-05 12:12 ` Tassilo Horn
2021-12-05 13:26 ` Rudi C
2021-12-05 17:00 ` Tassilo Horn
2021-12-06 4:34 ` Richard Stallman
2021-12-05 20:24 ` Lars Ingebrigtsen
2021-12-06 6:01 ` Tassilo Horn
2021-09-30 15:45 ` [External] : " Drew Adams
2021-09-30 13:54 ` Stefan Kangas
2021-09-30 13:59 ` Lars Ingebrigtsen
2021-09-29 15:44 ` Eli Zaretskii
2021-09-29 17:01 ` [External] : " Drew Adams
2021-09-29 19:09 ` Tassilo Horn
2021-09-29 19:35 ` Drew Adams
2021-09-29 13:57 ` Stefan Kangas
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=87v92j33g2.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rudiwillalwaysloveyou@gmail.com \
--cc=stefankangas@gmail.com \
/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.