From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16997 invoked from network); 14 Oct 1998 09:53:43 -0000 Received: from math.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 14 Oct 1998 09:53:43 -0000 Received: (from list@localhost) by math.gatech.edu (8.9.1/8.9.1) id FAA23138; Wed, 14 Oct 1998 05:44:43 -0400 (EDT) Resent-Date: Wed, 14 Oct 1998 05:44:43 -0400 (EDT) Message-Id: <199810140948.KAA20183@diamond.tao.co.uk> Subject: Re: v3.1.4 Files/mv bug To: phil@athenaeum.demon.co.uk (Phil Pennock) Date: Wed, 14 Oct 1998 10:48:00 +0100 (BST) From: "Zefram" Cc: zsh-workers@math.gatech.edu In-Reply-To: <199810132304.AAA01495@athenaeum.demon.co.uk> from "Phil Pennock" at Oct 14, 98 00:04:07 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"jrhBm1.0.Qf5.AA79s"@math> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/4428 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu 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. -zefram