"Wilber" <[EMAIL PROTECTED]> wrote: > When using the option --reply=no for mv, it still overwrites the file when it > is not supposed to. > > Here is a quick demo: > [EMAIL PROTECTED] ~]# mkdir mvtest > [EMAIL PROTECTED] ~]# cd mvtest/ > [EMAIL PROTECTED] mvtest]# mkdir moveto > [EMAIL PROTECTED] mvtest]# echo test > file.ext > [EMAIL PROTECTED] mvtest]# touch moveto/file.ext > [EMAIL PROTECTED] mvtest]# ls > file.ext moveto > [EMAIL PROTECTED] mvtest]# mv --reply=no -v file.ext moveto/ > `file.ext' -> `moveto/file.ext' > [EMAIL PROTECTED] mvtest]# ls > moveto > [EMAIL PROTECTED] mvtest]# > > This is wrong as the destination file should not be overwritten when using > --reply=no
Thanks for the report. However, you are misunderstanding the admittedly unclear description of --reply=no. That is why the --reply=... option is being deprecated and will be removed in an upcoming release. With --reply=no, mv declines to do the "move" operation only in those unusual cases (i.e., read-only target) in which it would have prompted you. _______________________________________________ Bug-coreutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-coreutils
