Bug 161615
| Summary: | mv --reply=no does not work as expected | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Hal Canary <halcanary> |
| Component: | coreutils | Assignee: | Tim Waugh <twaugh> |
| Status: | CLOSED UPSTREAM | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | athlon | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-06-27 09:25:23 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Hal Canary
2005-06-24 20:26:47 UTC
*** 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" |