Re: what will happen to the --reply option?

2007-08-26 Thread alessandro salvatori
| tr 'y' 'n'!!! -Alessandro On 8/25/07, Eric Blake [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to alessandro salvatori on 8/25/2007 9:58 PM: Hello, some scripts I wrote time ago are now displaying a lot of lines like this one: cp: the --reply

Re: what will happen to the --reply option?

2007-08-26 Thread alessandro salvatori
My case is the exact opposite of what you are talking about. Irrespectively of the original files, i want to keep the existing files at the destination, even if older. and cp --reply=no, without any other fancy thing that would have avoided a prompt, was the sweetest thing to do. it was... :(

Re: what will happen to the --reply option?

2007-08-26 Thread alessandro salvatori
except it is not guaranteed to be on a machine I will go for an horrible: yes n | cp -i src/ dst/ 21 | grep -v ' overwrite ' Thanks! -A On 8/26/07, Bob Proulx [EMAIL PROTECTED] wrote: alessandro salvatori wrote: My case is the exact opposite of what you are talking about. Irrespectively

what will happen to the --reply option?

2007-08-25 Thread alessandro salvatori
Hello, some scripts I wrote time ago are now displaying a lot of lines like this one: cp: the --reply option is deprecated; use -i or -f instead which is fairly annoying... On top of that the only way for me to get the desired behaviour of skipping existing files seems to be: yes | tr 'y'