GNU bug report logs - #10897
copy-directory create new directory when copying a symlink

Previous Next

Package: emacs;

Reported by: Thierry Volpiatto <thierry.volpiatto <at> gmail.com>

Date: Mon, 27 Feb 2012 08:51:02 UTC

Severity: minor

Tags: confirmed

Found in version 25.1

Fixed in version 28.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #90 received at 10897 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Marco Centurion <mcenturion <at> fing.edu.uy>
Cc: 10897 <at> debbugs.gnu.org
Subject: Re: bug#10897: copy-directory create new directory when copying a
 symlink
Date: Fri, 20 Aug 2021 08:51:19 +0300
> From: Marco Centurion <mcenturion <at> fing.edu.uy>
> Date: Thu, 19 Aug 2021 22:08:30 -0300
> 
> I failed to document the new behaviour in the docstring.
> 
> The patch I sent didn't manage the creation of the new symlink correctly
> either, as it created it with the same name as the target.  That is, in
> the examples given the result was:
> 
> -------------------------
> (copy-directory "~/tmp/foo" "~/Test" nil t)
> =>
> [mcenturion <at> localhost ~]$ ls -l Test
> total 4
> lrwxrwxrwx. 1 mcenturion mcenturion 26 ago 19 21:21 Test1 -> /home/mcenturion/tmp/Test1
> -------------------------
> 
> This new patch corrects both mistakes.

Thanks.

FWIW, I think this feature should be controlled by a user option, at
least because it changes a very old behavior.  Also, on some systems
(MS-Windows, for example) creating a symlink requires non-default
privileges, so it could be a nuisance to force this on such users.




This bug report was last modified 4 years ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.