As far as I know, tup buffers all output because it can run several commands in parallel. It only outputs stdout and stderr when a command has finished. If you really want to get around this I see two options:
1. You could try to patch tup so that if it's run with a single job it doesn't buffer. I have no clue how hard this would be to patch, but it's an option. 2. You could have your command output the progress some other way e.g. write to a file that tup didn't care about, and then read from it with `tail -f` or similar. I don't necessarily recommend this, but it does "work". On Mon, Apr 4, 2016 at 9:58 AM Vanush Vaswani <[email protected]> wrote: > This may be a stupid question, but I have a long running command which > itself has its own progress bar. How can I view this while running tup? (It > seems like it's stuck at 0%). > > -- > -- > tup-users mailing list > email: [email protected] > unsubscribe: [email protected] > options: http://groups.google.com/group/tup-users?hl=en > --- > You received this message because you are subscribed to the Google Groups > "tup-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
