unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: tramp-devel@gnu.org, emacs-devel@gnu.org
Subject: Re: Tramp and recursive file operations
Date: Tue, 29 Sep 2009 16:53:11 -0400	[thread overview]
Message-ID: <jwvvdj1h3y9.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <nqmy4dlsqt.fsf@alcatel-lucent.de> (Michael Albinus's message of "Tue, 29 Sep 2009 16:39:54 +0200")

> recursive copy or deletion of files can last a long time, because all
> operations are performed file by file. This could be much faster, if
> Tramp would be allowed to apply such operations in one step, for a whole
> directory. Think about "scp" or "rsync".

> Therefore, I propose to add a file name handler to `dired-copy-file-recursive'.

> Recursive file deletion happens via `dired-delete-file'. Here I propose
> to add a new function `dired-delete-file-recursive', which takes over
> the recursive part of `dired-delete-file', and which calls also a file
> name handler when appropriate.

> I volunteer to implement such handlers in Tramp :-)

> What do people think?

It seems OK, but I'd rather see them renamed to copy-file-recursive and
delete-file-recursive at the same time and made independent from dired.


        Stefan




  parent reply	other threads:[~2009-09-29 20:53 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 [this message]
2009-09-30  8:06   ` Michael Albinus
2009-09-30 13:45     ` Stefan Monnier
2009-09-30 14:07       ` Michael Albinus
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvvdj1h3y9.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.de \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).