Re: bug in copy-directory

[Thierry Volpiatto <thierry.volpiatto@gmail.com>]

Michael Albinus <michael.albinus@gmx.de> writes:

> Chong Yidong <cyd@stupidchicken.com> writes:
>
>> Michael Albinus <michael.albinus@gmx.de> writes:
> It works fine, thank you. But there seems to be a bug in dired; when I
> copy "/tmp/test" to "~/" twice, I see the corrupted directory structure.

What we could do also is create a function copy-directory-contents, that
reuse the code of precedent version of copy-directory (but not
interactive this time) and call this function in
dired-copy-file-recursive instead of copy-directory.

In this case we could rewrite copy-directory to avoid duplicate code,
possibly: (no urge in this case as actual copy-directory works fine) 

1) Writing copy-directory-contents (or whatever name) to allow
creating the structure like actual copy-directory, or not like ancient
version leaving this job to dired-create-files.

2) Writing a copy-directory that reuse dired code (i.e dired-create-files).
In this case it would have all interactive messages, ask etc..

WDYT?

-- 
A+ Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997