[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RFC: cp -if a b: should it prompt? POSIX says `yes', most don't
From: |
Jim Meyering |
Subject: |
Re: RFC: cp -if a b: should it prompt? POSIX says `yes', most don't |
Date: |
Thu, 19 Feb 2004 23:07:41 +0100 |
Hi Paul,
Paul Eggert <address@hidden> wrote:
> As I understand it, Jim's current thought is that -f should cancel a
> preceding -i, but -i should not cancel a preceding -f.
Actually, no.
I was considering making it so that both -i and -f control
whether cp prompts for an existing destination. Whichever
is used last controls that aspect. But if -f is ever used, then
cp would also exhibit its currently behavior:
-f, --force if an existing destination file cannot be
opened, remove it and try again
i.e., -i would not cancel that aspect of a preceding -f.
- RFC: cp -if a b: should it prompt? POSIX says `yes', most don't, Jim Meyering, 2004/02/17
- Re: RFC: cp -if a b: should it prompt? POSIX says `yes', most don't, Paul Jarc, 2004/02/17
- Re: RFC: cp -if a b: should it prompt? POSIX says `yes', most don't, Jim Meyering, 2004/02/17
- Re: RFC: cp -if a b: should it prompt? POSIX says `yes', most don't, era+gmane, 2004/02/18
- Re: RFC: cp -if a b: should it prompt? POSIX says `yes', most don't, Paul Jarc, 2004/02/18
- Re: RFC: cp -if a b: should it prompt? POSIX says `yes', most don't, Tim Waugh, 2004/02/18
- Re: RFC: cp -if a b: should it prompt? POSIX says `yes', most don't, Paul Eggert, 2004/02/19
- Re: RFC: cp -if a b: should it prompt? POSIX says `yes', most don't,
Jim Meyering <=