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

Pronterface can't log to stdout #1472

Closed
Fat-Zer opened this issue Dec 4, 2024 · 2 comments
Closed

Pronterface can't log to stdout #1472

Fat-Zer opened this issue Dec 4, 2024 · 2 comments

Comments

@Fat-Zer
Copy link
Contributor

Fat-Zer commented Dec 4, 2024

subj;

As tooltip in Settings->Options->User Interface->Log Path says:

Path to the log file. An empty path will log to the console.

But specifying an empty string causes pronterface to log to the default path instead (which is home directory).

This happens because for an empty logpath pronterface saves set log_path to .pronsolerc, which is interpreted as "print log_path" instead of "reset the variable to an empty string".

@DivingDuck
Copy link
Collaborator

Good point.
This is an intended behavior that we introduce with version 2.0 as we had often the problem that users wasn't able to tell us what they really did and/or they never found the log file. Since then we have always a log file available in the home directory except the user choose an other location.
We should delete the second sentence because of the change we did.

Btw, for Windows it is called printrun.log

@Fat-Zer
Copy link
Contributor Author

Fat-Zer commented Dec 4, 2024

It would be nice to have an option to log to stdout (or better stderr) as well then, as it's easier to track during debug.

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

No branches or pull requests

3 participants