Skip to content
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

pirouette is not silent #2

Closed
richelbilderbeek opened this issue Jul 4, 2018 · 9 comments
Closed

pirouette is not silent #2

richelbilderbeek opened this issue Jul 4, 2018 · 9 comments

Comments

@richelbilderbeek
Copy link
Owner

richelbilderbeek commented Jul 4, 2018

From @Giappo:

I noticed that in "pir_run" even if "verbose" is set to its default
(which is FALSE) you will still get a very abundant printed output. Do
you think user might need a method to drastically cut the printed
output or remove it completely?
@richelbilderbeek
Copy link
Owner Author

richelbilderbeek commented Jul 4, 2018

Hmmm, this is new to me, as I do like to follow the UNIX Golden Rule of Silence.

Got demo code where this happens?

@richelbilderbeek
Copy link
Owner Author

richelbilderbeek commented Jul 4, 2018

Demo code from @Giappo: pir_run-printed_output.rmd.zip

@richelbilderbeek
Copy link
Owner Author

I got this output:

2018-07-04-075308_1102x1006_scrot

@richelbilderbeek
Copy link
Owner Author

Sent email to @Giappo:

I am sorry, you can see #2 that I cannot reproduce the noise.Could you please try to do so again?

@Giappo
Copy link
Collaborator

Giappo commented Jul 4, 2018

I mean all the stuff printed like the one you see on top of this screenshot. This is, of course, only the last part of it. Is there a way to prevent it being printed?

screenshot 2018-07-04 13 21 46

@richelbilderbeek
Copy link
Owner Author

I cannot reproduce this.

I assume it has to do with your operating system, which is Windows.

As I do not use Windows, nor do I have easy access to this, I can only point you to this part of the beastier::run_beast2 function, where I mute the output for UNIX.

From that, I hope someone with Windows will fix it then 👼

@richelbilderbeek
Copy link
Owner Author

@Giappo tried, but the beastier Pull Request did not build properly.

@richelbilderbeek
Copy link
Owner Author

Issue is moved to a beastier Issue

@richelbilderbeek
Copy link
Owner Author

As Issue is moved to a beastier Issue, I close this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants