Bug 6010 - Need a --noprogress option
Summary: Need a --noprogress option
Status: CLOSED INVALID
Alias: None
Product: rsync
Classification: Unclassified
Component: core (show other bugs)
Version: 3.1.0
Hardware: Other Other
: P3 normal (vote)
Target Milestone: ---
Assignee: Wayne Davison
QA Contact: Rsync QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-03 14:12 UTC by Dave Yost
Modified: 2009-01-03 22:39 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Yost 2009-01-03 14:12:31 UTC 
My script constructs an rsync command with a --progress arg by default.
I let the user of my script specify rsync args, which I append to the default args.
Without a --noprogress arg, the user can't turn off the default I chose.

I could work around this by recognizing --noprogress, deleting it from the user list and deleting --progress from my default list. Messier, and it also introduces into the user's mind that there is a --noprogress arg to rsync, which there isn't.
Comment 1 Dave Yost 2009-01-03 14:14:30 UTC 
oh.
Comment 2 Wayne Davison 2009-01-03 22:39:12 UTC 
I assume you found the --no-progress option (which I note here to make the bug's comments complete).  Enjoy!