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

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 ignor

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

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... :( che

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

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. I

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

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 n

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

-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... W

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

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: Brian ___

what will happen to the --reply option?

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' 'n

Re: Please ,answer to me

This looks like a configuration problem with Samba. You should direct your query to the Samba mailing available at https://lists.samba.org/mailman/ Thanks! On Saturday 25 August 2007 9:19:22 pm thanh phuong wrote: > Dear sir/madam >What's a pity when i sent this letter to you. I am stil

Please ,answer to me

Dear sir/madam What's a pity when i sent this letter to you. I am still confiuring Samba on CentOS 5. I have some problems with permission files and folder on Samba. I have create one folder "abcd" which permision like "tmp" But when i started samba. I can't create folder on directory "abcd

broken symlinks after updating from gnulib

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've noticed that after using either gnulib-tool (such as in m4 or findutils) or bootstrap (in coreutils), when symlinks are used instead of copies, that the deletion of a file in gnulib leaves a broken symlink in the tree. In the worst case, when a .

Re: html manual on case-insensitive systems

Eric Blake <[EMAIL PROTECTED]> wrote: > I noticed that when trying to browse the one-page-per-node html > documentation on a case-insensitive directory, I was unable to see both > index.html (the overview) and Index.html (the concept index). Here's how > M4 avoided the problem: > > 2007-08-25 Eri

html manual on case-insensitive systems

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I noticed that when trying to browse the one-page-per-node html documentation on a case-insensitive directory, I was unable to see both index.html (the overview) and Index.html (the concept index). Here's how M4 avoided the problem: 2007-08-25 Eric

Re: bug in /bin/test ?

Quoting Brian Dessent <[EMAIL PROTECTED]>: effectively swallowing it ... test program does not see any STRING argument at all. Ok, thanks for your fast answer Brian. Regards, Emanuele This message was sent using IMP, the In

[bug #18927] feature request: user defined format for ls output

Follow-up Comment #4, bug #18927 (project coreutils): My experience with find -printf format letters (and I'm sure of the coreutils developers with command-line option letters) is that there just aren't enough letters. The ones you end up with still available just aren't mnemonic for a new use

Re: bug in /bin/test ?

Emanuele Tomasi wrote: > $> /usr/bin/test -n $casa && echo yes || echo no > yes > > $> /usr/bin/test $casa && echo yes || echo no > no > > $> /usr/bin/test -z $casa && echo yes || echo no > yes I think you may not be understanding the fact that the shell expands $casa into the empty string befor

bug in /bin/test ?

Hi, is it a bug of /bin/test? Please see this output: 1) --- $> which test /bin/test $> casa= $> /usr/bin/test -n $casa && echo yes || echo no yes $> /usr/bin/test $casa && echo yes || echo no no --

[bug #18927] feature request: user defined format for ls output

Update of bug #18927 (project coreutils): Severity: 3 - Normal => 1 - Wish ___ Reply to this item at: ___