On Freitag, 2. Juni 2017 20:32:01 CEST Avinash Sonawane wrote: > On Fri, Jun 2, 2017 at 1:17 PM, Tim Rühsen <[email protected]> wrote: > > 3. Tell wget not to read a config file at all with --no-config. > > Thanks! Didn't know that! > > But it seems this is specific to --config only and not for other > similar options.
Yes, it is. > For example, > I have `logfile = wget.log` in my .wgetrc along with other commands. > And now I want to override this specific .wgetrc configuration and > would like wget to show log on terminal (default behavior). How do I > do that? There is no --logfile but --output-file, still you have to use 'logfile' in the config file (sigh). One of those historical stupidities... > 1. There is no `--no-output-file` to achieve this. > > 2. --output-file="" makes wget exit without downloading the document > and spitting out an error about there being no such file or directory. "-" is normally stdout. So you could say --output-file=-, I guess. > Of course, as you suggested I can create an another rc file for this > specific use case containing all of .wgetrc but this specific command. > But then there as other similar options as well and so this doesn't > look scalable. > > May be we should accommodate 1. or 2. or may be both? For Wget2 we have -no- also for strings/filenames. So the problem is solved for me. Instead of wasting time with Wget1.x we should use that time to make Wget2 release ready (IMO). With Best Regards, Tim
signature.asc
Description: This is a digitally signed message part.
