From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Michael Heerdegen Newsgroups: gmane.emacs.devel Subject: dired-do-copy may create infinite directory hierarchy, again Date: Thu, 29 Mar 2012 04:58:22 +0200 Message-ID: <87fwcsw1td.fsf@web.de> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1332989816 20276 80.91.229.3 (29 Mar 2012 02:56:56 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 29 Mar 2012 02:56:56 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Mar 29 04:56:54 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SD5Xf-0001Qb-1j for ged-emacs-devel@m.gmane.org; Thu, 29 Mar 2012 04:56:51 +0200 Original-Received: from localhost ([::1]:57875 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SD5Xe-00022U-Gn for ged-emacs-devel@m.gmane.org; Wed, 28 Mar 2012 22:56:50 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:38713) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SD5Xa-00021m-SC for emacs-devel@gnu.org; Wed, 28 Mar 2012 22:56:48 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SD5XY-0007KZ-Sa for emacs-devel@gnu.org; Wed, 28 Mar 2012 22:56:46 -0400 Original-Received: from fmmailgate04.web.de ([217.72.192.242]:46524) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SD5XY-0007K1-MC for emacs-devel@gnu.org; Wed, 28 Mar 2012 22:56:44 -0400 Original-Received: from moweb001.kundenserver.de (moweb001.kundenserver.de [172.19.20.114]) by fmmailgate04.web.de (Postfix) with ESMTP id 8D904744054E for ; Thu, 29 Mar 2012 04:56:42 +0200 (CEST) Original-Received: from snow.dragon ([89.204.130.227]) by smtp.web.de (mrweb002) with ESMTPA (Nemesis) id 0Lh6fv-1SZGjm28hz-00nhHa; Thu, 29 Mar 2012 04:56:42 +0200 User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.94 (gnu/linux) X-Provags-ID: V02:K0:TWINjEKayuy2ISQMx1TPwhpPu85QxMapJu2RKMEjywT ENiXCg1vb1nD2e7AOdcyO3N7s87Q5LQbyLo9KkKZoJZHXYHpDy bUvi0nwXQYQJEVWGFU+ixyWPQ6+gyiqYvw3l9vzU6ZJsOAeS9G 4PtGtDDAYoShfODERS6IUuI6mnqkxIfni56pw7N0wFPIS7JkAn t03lvM/Oz+jcKKgoh8lQ8FldFHEt9Y8Ou/LY6krCm4= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4-2.6 X-Received-From: 217.72.192.242 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:149241 Archived-At: Hi, I had sent a reply to bug#10489: 24.0.92; dired-do-copy may create infinite directory hierarchy after it had been closed, saying that there are still problems. Unfortunately I got no answer. Since it was an important bug: Can please somebody have a look? Thanks. This was my message: Hello again, I'm afraid there are still problems. I encountered these two: 1. Creating symlinks to parent directories doesn't work anymore. E.g. if you have a directory "~/test/dir1/", open a dired for "~", go to "test/", hit S, enter "~/test/dir1/" and hit RET. You get the error dired-create-files: Cannot copy `/home/micha/test' into its subdirectory `/home/micha/test/dir1/test' But I only wanted a symlink... This worked in Emacs 23. 2. Symlinks to parent directories (still) lead to ininite loops when copying containing dir. To use the above example: just create this symlink from outside Emacs, so you get e.g. this: /home/micha/test/dir1: total used in directory 8,0K available 94267456 drwxr-xr-x 2 micha users 4,0K M=C3=A4r 22 02:32 . drwxr-xr-x 3 micha users 4,0K M=C3=A4r 22 02:33 .. lrwxrwxrwx 1 micha users 22 M=C3=A4r 22 02:32 test -> /home/micha/test Now dired "~", and copy "~/test" to "~/test2". You get a hierarchy ~/test2/dir1/test/dir1/test/... again (the command terminates without error, btw). And all these are real directories, and _not_ symlinks! I also wonder why dired doesn't copy the symlink itself, but copies the target instead? This seems to be the case also in other examples. If I copy a directory containing any symlinks with dired, copying always copies the targets of the symlinks. Michael