Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


The file libo/src/fetch.log has entries such as this:

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

But my copy of the terminal log shows this:

Clearly this kind of output is useful only when running the download interactively. For some reason 
I don't see anything like that in my fetch.log, and donät remember seeing it on the terminal 
either. I nthe fetch.log I just see occasional lines like

2011-05-06 16:40:34 
URL:http://download.go-oo.org/src/29721a16f25967d59969d5f0ae485b4a-libwps-0.2.2.tar.bz2 
[295486/295486] -> "29721a16f25967d59969d5f0ae485b4a-libwps-0.2.2.tar.bz2" [1]

but mostly just lines with only a timestamp (which are pointless I think and could be removed).

Is it wget or curl that outputs the thing you see? I would have thought that they would be clever 
enough to not print anything like that if stdout is not a terminal. Could you please investigate if 
there is some switch to pass to wget or curl to get them to be less chatty, and then use that 
option if test ! -t 1 , or something.

Question 2: How do I go about stepping through bash scipts? 

Eh, I had no idea that there even was a bash debugger, nice!

Traditionally one just uses debugging prints, i.e. "echo" statements, to debug shell scripts... As 
the bashdb configure script says, if you want to use it, you need a newer bash, so you need to 
build it yourself.

--tml


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.