From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "tramp-devel@gnu.org" <tramp-devel@gnu.org>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Tramp and recursive file operations
Date: Wed, 30 Sep 2009 16:07:14 +0200 [thread overview]
Message-ID: <nqws3g8r1p.fsf@alcatel-lucent.de> (raw)
In-Reply-To: <jwvvdj04kgp.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 30 Sep 2009 15:45:40 +0200")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> OK. Looking outside dired, there is already delete-directory, good for
>> empty directories. Maybe we add an optional parameter RECURSIVE?
>
> Sounds OK, except for the fact that delete-directory is implemented in
> C, so you'd have to code the recursion in C as well.
I've seen that. I'll do my best ...
>> A copy-directory function does not exist. What about allowing the first
>> parameter of copy-file to be a directory name? This would imply to copy
>> recursively.
>
> If we were starting over from scratch, that would be fine, but I'm
> afraid that some code somewhere relies on the fact that copy-file only
> copies files and not directories. And of course, copy-file is also
> implemented in C, so you'd have to code the recursion in C as well.
So we go with copy-directory? Just DIRNAME and NEWNAME as parameters, or
the other ones from copy-file as well? I guess that we dont't need
OK-IF-ALREADY-EXISTS, because if directory NEWNAME already exists, we
create a subdirectory.
And this could be a Lisp function.
> Stefan
Best regards, Michael.
next prev parent reply other threads:[~2009-09-30 14:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 14:39 Tramp and recursive file operations Michael Albinus
2009-09-29 17:49 ` joakim
2009-09-29 20:53 ` Stefan Monnier
2009-09-30 8:06 ` Michael Albinus
2009-09-30 13:45 ` Stefan Monnier
2009-09-30 14:07 ` Michael Albinus [this message]
2009-09-30 19:56 ` Stefan Monnier
2009-10-01 15:53 ` Michael Albinus
2009-09-30 15:52 ` yary
2009-10-02 5:10 ` Michael Albinus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nqws3g8r1p.fsf@alcatel-lucent.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=tramp-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.