unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: yary <not.com@gmail.com>
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: Fri, 02 Oct 2009 07:10:37 +0200	[thread overview]
Message-ID: <nqocoqjs8i.fsf@alcatel-lucent.de> (raw)
In-Reply-To: <75cbfa570909300852j3bcba55cw3ae4ac3922a1b0d3@mail.gmail.com> (yary's message of "Wed, 30 Sep 2009 17:52:43 +0200")

yary <not.com@gmail.com> writes:

>> 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.
>>
>> Comments?
>
> Is there any existing code that may be using the error-check in
> copy-file to ensure that the first arg is not a directory? I like the
> idea of making the existing copy-file smart enough to "do the right
> thing" when the first argument is a dir, but it could need an optional
> RECURSIVE parameter if and only if other callers rely on it rejecting
> directories.

We don't know what people are doing outside the Emacs core packages with
copy-file. So I cannot answer your question.

Adding a RECURSIVE parameter might be an option; OTOH copy-file has
already a long list, and it would be inconvenient to count the number of
nil until you can say t for RECURSIVE. That's why I prefer to introduce
copy-directory.

> -y

Best regards, Michael.




      reply	other threads:[~2009-10-02  5:10 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
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 [this message]

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=nqocoqjs8i.fsf@alcatel-lucent.de \
    --to=michael.albinus@gmx.de \
    --cc=emacs-devel@gnu.org \
    --cc=not.com@gmail.com \
    --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).