Re: PR: dired-do-create-files now checks for trailing slashes in the target

[Eli Zaretskii]

> From: Tassilo Horn <tsdh@gnu.org>
> Date: Thu, 30 Sep 2021 16:10:02 +0200
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org,
>  rudiwillalwaysloveyou@gmail.com, Stefan Kangas <stefankangas@gmail.com>
> 
> `dired-create-destination-dirs' already exists.  But in Rudi's most
> recent patch version, he added a new one.
> 
> --8<---------------cut here---------------start------------->8---
> +(defcustom dired-create-destination-dirs-trailing-separator-special nil

That's a mouthful, IMO.  How about

  dired-create-dirs-with-trailing-slash

instead?

> Rudi proposed that the default value should probably be `t' given that
> this feels so intuitive and the only gotcha is renaming/moving or
> copying a directory source/ to a non-existent target or target/ where
> the former has rename/make a copy semantics and the latter has move/copy
> *into* the to be created target/ directory.

Please don't make it t by default.  I'm quite sure you didn't consider
all the use cases.  E.g., what about foo -> Foo on case-insensitive
filesystems?  That is a valid use case where the user wants a
directory renamed with a different letter-case.

We should only turn it on by default after it has been tested by
enough users for long enough.