[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cp -f behavior
From: |
Jim Meyering |
Subject: |
Re: cp -f behavior |
Date: |
Thu, 06 Jun 2002 09:33:15 +0200 |
User-agent: |
Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.3.50 (i686-pc-linux-gnu) |
Andrew D Jewell <address@hidden> wrote:
> At 8:38 AM -0400 6/5/02, Ryan McGuigan wrote:
>>--force (-f) not cancelling the effect of -i is insanely annoying. i do
>>not understand what the point of following that behavior(per POSIX) when
>>most systems do not use that behavior, at least none i've used
>>recently. and why should the cp command behave differently from the
>>other commands?
>>
>>either it should be changed back, an option while building, or there
>>should be another way of cancelling -i
>
> -f actually means something distinctly different from cancelling
> -i. In fact, specifying both can make sense.
>
> I would strongly recommend another way of cancelling -i, for example
>
> -I, --non-interactive don't prompt before overwrite
>
> here's the patch against fileutils-4.1.8
Thanks for the patch, but cp (from fileutils-4.1.8) already has an
option intended to solve that problem:
--reply={yes,no,query} specify how to handle the prompt about an
existing destination file