From: Dan Nelson <dnelson@emsphone.com>
To: Zefram <zefram@tao.co.uk>, Phil Pennock <phil@athenaeum.demon.co.uk>
Cc: zsh-workers@math.gatech.edu
Subject: Re: v3.1.4 Files/mv bug
Date: Wed, 14 Oct 1998 10:07:39 -0500 [thread overview]
Message-ID: <19981014100739.A9435@emsphone.com> (raw)
In-Reply-To: <199810140948.KAA20183@diamond.tao.co.uk>; from "Zefram" on Wed Oct 14 10:48:00 GMT 1998
In the last episode (Oct 14), Zefram said:
> Phil Pennock wrote:
> >Another issue for you. In zsh v.3.1.4, the 'files' module, (built
> >for Linux/x86, but not really relevant), the 'mv' command doesn't
> >handle moving across devices.
>
> This is a deliberate feature. The logic is that you can't actually
> move files across devices, and the purpose of mv is to move files, so
> mv can't move files across devices. The historical versions that do
> a copy and remove are actually providing behaviour radically
> different from what mv is intended for. If you want a copy and
> remove, rather than a move, you can use cp and rm yourself.
I haven't used 3.1.* at all, so I'm just guessing here, but shouldn't
any builtin command that overrides an external command do _exactly_
what that external command was supposed to do? Otherwise script
writers will have to use "command mv" or whatever, to guarantee that
they get a working "mv".
See the X/Open specification at
http://www.opengroup.org/onlinepubs/7908799/xcu/mv.html for a
description of at least one "standard" for mv, which allows
cross-device moves.
-Dan Nelson
dnelson@emsphone.com
next prev parent reply other threads:[~1998-10-14 15:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-13 23:04 Phil Pennock
1998-10-14 9:48 ` Zefram
1998-10-14 14:46 ` PATCH: v3.1.4 Files/mv bug is a feature Bart Schaefer
1998-10-14 15:07 ` Dan Nelson [this message]
1998-10-14 17:38 ` v3.1.4 Files/mv bug Phil Pennock
1998-10-14 17:46 ` Zefram
1998-10-14 18:05 ` Phil Pennock
1998-10-14 18:41 ` Bart Schaefer
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=19981014100739.A9435@emsphone.com \
--to=dnelson@emsphone.com \
--cc=phil@athenaeum.demon.co.uk \
--cc=zefram@tao.co.uk \
--cc=zsh-workers@math.gatech.edu \
/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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).