zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: phil@athenaeum.demon.co.uk (Phil Pennock), zsh-workers@math.gatech.edu
Subject: PATCH: v3.1.4 Files/mv bug is a feature
Date: Wed, 14 Oct 1998 07:46:26 -0700	[thread overview]
Message-ID: <981014074626.ZM18376@candle.brasslantern.com> (raw)
In-Reply-To: <199810140948.KAA20183@diamond.tao.co.uk>

On Oct 14, 10:48am, Zefram wrote:
} Subject: Re: v3.1.4 Files/mv bug
}
} Phil Pennock wrote:
} >In zsh v.3.1.4, the 'files' module ... the 'mv' command doesn't handle
} >moving across devices.
} 
} This is a deliberate feature.

That probably ought to be documented, then.

Index: Doc/Zsh/mod_files.yo
===================================================================
--- mod_files.yo	1998/06/01 17:08:43	1.1.1.1
+++ mod_files.yo	1998/10/14 14:45:04
@@ -48,6 +48,12 @@
 The tt(-i) option causes the user to be queried about replacing
 any existing files.  The tt(-f) option causes any existing files to be
 silently deleted, without querying.  tt(-f) takes precedence.
+
+Note that this tt(mv) command performs renaming only.  It cannot move
+files across devices.  This is a deliberate feature.  Files can only
+be copied across devices, not truly moved, and the purpose of tt(mv)
+is to move files.  If the desired action is copy followed by remove,
+use tt(cp) and tt(rm).
 )
 findex(rm)
 item(tt(rm) [ tt(-dfirs) ] var(filename) ...)(

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  reply	other threads:[~1998-10-14 14:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-13 23:04 v3.1.4 Files/mv bug Phil Pennock
1998-10-14  9:48 ` Zefram
1998-10-14 14:46   ` Bart Schaefer [this message]
1998-10-14 15:07   ` Dan Nelson
1998-10-14 17:38   ` 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=981014074626.ZM18376@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=phil@athenaeum.demon.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).