From: John Paul Wallington <jpw@gnu.org>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: dired not bold enough to move directories
Date: Sat, 08 Feb 2003 02:24:37 +0000 [thread overview]
Message-ID: <874r7fse56.fsf@china.shootybangbang.com> (raw)
In-Reply-To: <200302080137.TAA28103@eel.dms.auburn.edu> (Luc Teirlinck's message of "Fri, 7 Feb 2003 19:37:06 -0600 (CST)")
Luc Teirlinck wrote:
> > Well, gosh, if I can move a directory like this,
> > $ cd /var/tmp
> > $ mv affordablehost_logs ~/tmp
> >
> > then why can't I remame it with R in dired?
>
> Because they are on separate partitions.
> dired should behave like mv in such a case.
>
> I understand both above lines, but it is not immediately obvious to
> me what your conclusion is. It seems to me that you agree with
> Dan, because (from version `4.0' of the fileutils onward) mv no
> longer cares about partitions. (Do I understand this correctly?)
Yup.
> I personally agree with Dan (and you?) too, unless there would be
> some good reason for dired to behave differently from mv in this
> case. (I can not think of any, but that does, of course, not mean
> that there is none.)
Presently Frename_file calls rename or link (and unlink) then does:
if (errno == EXDEV)
{
Fcopy_file (file, newname,
/* We have already prompted if it was an integer,
so don't have copy-file prompt again. */
NILP (ok_if_already_exists) ? Qnil : Qt, Qt);
Fdelete_file (file);
}
which deals with renaming files across file systems. Maybe it should
recursively copy directories too? If not, then dired could handle it
in lisp instead.
next prev parent reply other threads:[~2003-02-08 2:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-08 1:37 dired not bold enough to move directories Luc Teirlinck
2003-02-08 2:24 ` John Paul Wallington [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-06 18:25 Dan Jacobson
2003-02-06 19:49 ` John Paul Wallington
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=874r7fse56.fsf@china.shootybangbang.com \
--to=jpw@gnu.org \
--cc=bug-gnu-emacs@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.