Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Bug#479764: shell builtin mv fails to move files across devices
- X-seq: zsh-workers 24955
- From: Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
- To: martin f krafft <madduck@xxxxxxxxxx>
- Subject: Re: Bug#479764: shell builtin mv fails to move files across devices
- Date: Tue, 6 May 2008 21:52:58 +0100
- Cc: zsh-workers@xxxxxxxxxx, 479764@xxxxxxxxxxxxxxx
- In-reply-to: <20080506165555.GB17377@xxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20080506144208.GA15225@xxxxxxxxxxxxxxxxx> <20080506150303.GB31177@xxxxxxxx> <080506084541.ZM1350@xxxxxxxxxxxxxxxxxxxxxx> <20080506165555.GB17377@xxxxxxxxxxxxxxxxx>
On Tue, 6 May 2008 17:55:55 +0100
martin f krafft <madduck@xxxxxxxxxx> wrote:
> also sprach Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> [2008.05.06.1645 +0100]:
> > I'd rather we didn't. rename(2) is atomic, but there's no
> > reasonable way to make cp+rm be so, and I think it's better if the
> > user is forced to be aware of the issue.
> >
> > Also note that "cp" is (intentionally) NOT one of the commands
> > supplied by the zsh/files module, so changing mv means
> > implementing cp.
>
> What, if I may ask, is the purpose of zsh/files?
Its primary purpose has been as a fallback on a system where the shell
is working but nothing much else is. Hence it provides the limited,
easy-to-implement things you're likely to need to fix what needs
fixing. Moving things between file systems typically isn't something
you need (though in any given case it may be, as well as a whole load of
other stuff the shell doesn't provide).
--
Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/
Messages sorted by:
Reverse Date,
Date,
Thread,
Author