Red Hat Bugzilla – Bug 161615
mv --reply=no does not work as expected
Last modified: 2007-11-30 17:11:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4
Description of problem:
touch file1 file2
mv --reply=no file1 file2
ls file1 file2
mv should not overwrite file2. It does.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. touch file1 file2
2. mv --reply=no file1 file2
3. ls file1 file2
Actual Results: /bin/ls: file1: No such file or directory
Expected Results: file1 file2
*** Bug 161616 has been marked as a duplicate of this bug. ***
Why would you expect that behaviour? Omitting '--reply=no' would not cause a
prompt to reply to!
From "info coreutils mv":
"Specify `--reply=no' to make `mv' act as if `no' were given as a response to
every prompt about a destination file. "
$ touch file1 file2
$ mv --reply=query file1 file2
mv: overwrite `file2'? n
I have a script that renames files. But I do not want this scipt to ever
clobber an existing file. Right now, I do "mv --reply=query" or "mv -i" to keep
the existing file from being overwriten. Then I manually type "n". I want to
not have to type "n" each time.
Acording to the man page, "--reply=no" should "specify how to handle the prompt
about an existing destination file." In other words: "No, I don't want to
overwrite that file."
Omitting '--reply=' would be equivilent to "--reply=yes"