From: "Drew Adams" <drew.adams@oracle.com>
To: <11326@debbugs.gnu.org>
Subject: bug#11326: 24.1.50; doc of `dired-recursive-copies', `dired-recursive-deletes'
Date: Tue, 24 Apr 2012 09:46:46 -0700 [thread overview]
Message-ID: <C2EFFEB31FA2438B824F93D11020C734@us.oracle.com> (raw)
In-Reply-To: <E60405881CCD474C815DE8A9E5962BC3@us.oracle.com>
> The doc string for `dired-recursive-deletes' is slightly better than
> that for `dired-recursive-copies', because it at least
> mentions deleting recursively.
This part was wrong. They both mention copying/deleting recursively.
But the rest of what I wrote was correct. It is misleading and unclear to talk
about recursive copies etc.
next prev parent reply other threads:[~2012-04-24 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 16:37 bug#11326: 24.1.50; doc of `dired-recursive-copies', `dired-recursive-deletes' Drew Adams
2012-04-24 16:46 ` Drew Adams [this message]
2012-06-22 7:40 ` Chong Yidong
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=C2EFFEB31FA2438B824F93D11020C734@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=11326@debbugs.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).