-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
uvcdat script now will redirect all output appropriately #1623
Conversation
@chaosphere2112 as part of this PR could you please add documentation as well? Wiki for now should be good. |
@aashish24 Documentation for what? The command line args we accept? |
Right. |
If it makes sense. |
@aashish24 Well, they do get displayed if you do |
@chaosphere2112 thanks. |
@chaosphere2112 I meant for capture, target etc. as well but sounds like they are shown as well? |
redirect=false | ||
fi | ||
;; | ||
--output-std) redirect=false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this mis-aligned?
@chaosphere2112 looks good to me. I didn't run it myself. Just had one minor question. |
Ah, I misunderstood. Added some comments to the script to explain what everything does. |
thanks for taking care of it @chaosphere2112. LGTM 👍 |
uvcdat script now will redirect all output appropriately
Fixes #1239; parses arguments passed to UV-CDAT, detects where output should be sent, and redirects all stdout and stderr to append at that location (in addition to the standard UV-CDAT logging mechanisms that are already printing at that point). Should fix the issues we've been having with miscellaneous C++ level logging getting dumped to the console (like the annoying Qt modal window non-error).