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
View this message in rfc822 format
Eli Zaretskii <eliz <at> gnu.org> writes:
Hi Eli,
>> 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".
>
> Yes, sure. We should support that with remote files as much as
> possible.
Will do. Thinking about, it makes only sense when both DIRECTORY and
NEWNAME are located on the same host. That's what I'm going to implement.
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.