Wget 1.x has had the "dot" progress bar for a very long time. This is a fall back mechanism for cases where the output document can't support ansi escape sequences, like very dumb terminals, a text file or even an in memory buffer.
It would be nice if we had such a progress bar implemented as well.
Designs
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related or that one is blocking others.
Learn more.
@darnir I would like to work on it, exploring the codebase now. I believe the implementation will go in bar.c only. will see if I can comeup with something.
can you recommend me how to use a dumb terminal terminal? I've never used something like that before.
I'm not entirely sure of where the implementation will go. Either bar.c, or it could have its own file.
Well, you don't really need a dumb terminal. Take a look at how --progress=dot works in wget. We want something like that here as well. It's not really very complicated. Should be a fairly straightforward task
What do we expect to be the behavior of the dot bar when downloading more than 1 file at the same time?
If it behaves like the "usual" bar (this is, just having more than one dot bar on the screen) then this won't work when output is a text file (which is one of the cases stated above). If we just have a "global" dot bar amounting for all the files we download, the percentages that are showed at the end of every line should be removed, as anything displayed there could be misleading
Can we have both ? More than one dot bar on the console, but just one for a text file ?
Currently I can imagine how this would look like in a text file, tbh.
Could you create an example output file and share it here ?
This is the output to wget --progress=bar -o file https://ftp.gnu.org/gnu/emacs/emacs-27.2.tar.gz on the file called 'file' (I attached the full file):
The idea would be to implement a similar dot bar to this one but without the percentage on the right, as it could be misleading (Because when downloading more than one file in parallel, we don't know the full size of the download queue, and so we can't calculate a coherent percentage. Think for example on a recursive download). Of course, we can support multiple dot bars when downloading in the console.