GNU bug report logs -
#10897
copy-directory create new directory when copying a symlink
Previous Next
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 #110 received at 10897 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
Hi Eli,
>> > 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.
>>
>> Hmm. Is this something we want also in Tramp?
>
> Which part, specifically?
Copy a symbolic link as-is. Example:
--8<---------------cut here---------------start------------->8---
(make-directory "/ssh::/tmp/foo")
(write-region "baz" nil "/ssh::/tmp/foo/baz")
(make-symbolic-link "/ssh::/tmp/foo" "/ssh::/tmp/bar")
(copy-directory "/ssh::/tmp/bar" "/ssh::/tmp/bla")
--8<---------------cut here---------------end--------------->8---
Currently, this creates a new directory "/ssh::/tmp/bla", which contains
the file "baz". If the new user option copy-directory-create-symlink is
non-nil, this should create the symlink "/ssh::/tmp/bla", pointing to
"/tmp/foo".
There are many traps in implementation, especially in case DIRECTORY and
NEWNAME of copy-directory are located on different hosts. But first, we
shall decide whether such a feature is useful for Tramp files in general.
(I would say yes, with all pain I see in the implementation.)
Best regards, Michael.
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.