> Would it be enough to just print out what step scour is at some level of detail, ie
Well, where I was coming from was that I had generated some 2D plots with scilab, which, when exported to SVG are ridiculously huge (1.8MB), however I want to keep them at print quality, so I ran scour. I came back three hours later and it was still running.
If you want super-awesomeness, a wget style 0[======> ]100% meter would be perfect, which is something along the lines of:
Step (1/15) 0 [===================> ] 100%
however I am not sure how portable this is across mutliple terminals. At the very least your suggestion would be nice.
I would suggest that this need be explicitly enabled, and would be written to stderr. Does this work on windows though? Do they have a separation of stdout/stderr ? For windows you may need to force the usage of -o.
> Would it be enough to just print out what step scour is at some level of detail, ie
Well, where I was coming from was that I had generated some 2D plots with scilab, which, when exported to SVG are ridiculously huge (1.8MB), however I want to keep them at print quality, so I ran scour. I came back three hours later and it was still running.
If you want super-awesomeness, a wget style 0[======> ]100% meter would be perfect, which is something along the lines of:
Step (1/15) 0 [====== ======= ======> ] 100%
however I am not sure how portable this is across mutliple terminals. At the very least your suggestion would be nice.
I would suggest that this need be explicitly enabled, and would be written to stderr. Does this work on windows though? Do they have a separation of stdout/stderr ? For windows you may need to force the usage of -o.
Thanks!