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

2007-08-27 Thread Matthew Woehlke
alessandro salvatori wrote: except it is not guaranteed to be on a machine Neither is coreutils. -- Matthew Microsoft: driving people fscking insane... ___ Bug-coreutils mailing list Bug-coreutils@gnu.org

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

2007-08-26 Thread alessandro salvatori
what are the cases when a prompt would not have been shown? AFAIK, those cases can be there only because of further options provided by the user, so it's his fault... my scripts just does: cp -d --preserve=mode,timestamps,links --reply=no and i can't be sure everybody have rsync installed.

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 Mark Rose
Yeah, that's exactly the feature I've been wanting (only with mv instead of cp). I actually joined this list to figure out why it had been deprecated. One day, when I have time to fully understand the source code, I'll sit down and write a --no-overwrite patch for mv and cp that silently

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

2007-08-26 Thread Bob Proulx
alessandro salvatori wrote: 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. In that case Eric's suggestion of rsync --ignore-existing is perfect then. Bob

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

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

2007-08-26 Thread Bob Proulx
Mark Rose wrote: Yeah, that's exactly the feature I've been wanting (only with mv instead of cp). I actually joined this list to figure out why it had been deprecated. It was removed because it did not actually prevent overwriting files. Try this with the old 'mv --reply=no'. $ touch bar

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'

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

2007-08-25 Thread Brian Dessent
alessandro salvatori wrote: On top of that the only way for me to get the desired behaviour of skipping existing files seems to be: See the previous thread from earlier this month: http://lists.gnu.org/archive/html/bug-coreutils/2007-08/msg0.html Brian

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

2007-08-25 Thread Eric Blake
-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 option is deprecated; use -i or -f instead which is fairly annoying... We

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

2007-08-25 Thread Bob Proulx
Eric Blake wrote: Why not use rsync --ignore-existing instead? Agreed that rsync is definitely the right tool for this task. Most of the time when people are trying to avoid overwriting existing files it is because they are trying to avoid spending the computer time to do the copy again and not