bug-wget
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-wget] [bug #44966] wget -nv is too verbose, -q too quiet


From: Darshit Shah
Subject: Re: [Bug-wget] [bug #44966] wget -nv is too verbose, -q too quiet
Date: Thu, 30 Apr 2015 15:04:02 +0530

Won't work, because Wget writes all its output to stderr.

On Thu, Apr 30, 2015 at 1:20 PM, Pär Karlsson <address@hidden> wrote:
> Also, at least on Unix like systems, there is the standard redirection
> operators in the shell. If you don't want to see errors, just redirect
> stderr to null, as in wget [...] 2>/dev/null
>
>
> 2015-04-30 8:59 GMT+02:00 Darshit Shah <address@hidden>:
>>
>> Follow-up Comment #2, bug #44966 (project wget):
>>
>> Not really. Sometimes I expect Wget to fail and do not want it's output
>> messing my script up. In other cases, I know how to handle Wget's failures
>> using exit codes and do not want the output to make things ugly.
>>
>> I usually run wget with -q --show-progress and would hate for errors to
>> clutter up the otherwise perfect screen.
>>
>> Also, the -q switch should really be "quiet". We do not want to print
>> *anything* at all if it can be avoided to the screen.
>>
>> The -nv switch is think is already that sweet spot between verbose and
>> quiet.
>> It will print only error messages and a success message for each file it
>> downloads.
>>
>> In my opinion, we should not change / add any more verbosity options.
>>
>>     _______________________________________________________
>>
>> Reply to this item at:
>>
>>   <http://savannah.gnu.org/bugs/?44966>
>>
>> _______________________________________________
>>   Message sent via/by Savannah
>>   http://savannah.gnu.org/
>>
>>
>



-- 
Thanking You,
Darshit Shah



reply via email to

[Prev in Thread] Current Thread [Next in Thread]