-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
What is the correct way to debug issues? #250
Comments
Right now there's no correct way. I use But to sort out your issue I think it's because your image viewer doesn't have the time to open the file before tut deletes it. Other people are experiencing this, so I'll try to include a fix in the next release |
If you try the version |
Yes that does it. With the upgrade to 2.0.0, I guess there was a switch to using Want me to close this, or is there more work here? Obviously with delete off, |
Nah, we can leave this open as some logs would be a nice addition :)
It was expected it wouldn't bee carried over, but maybe I should have informed about it more clearly.
Tut will remove all files when you close the application, so it shouldn't be that many files. Only if you run the application for days. If you want to clear files while running tut you can run the command |
Eh. Just making sure it was not doing something you were expecting it to.
It isn't, for me. I just tested it by:
This is with tut 2.0.0, and |
Is there a way to enable (background) logging? For example, i'm having issues with
[M]edia
; it's failing silently, and I can't figure out how to figure out why. Is theimage-viewer
command not working? Why?There doesn't appear to be a
logging
ordebug
option in theconfig.ini
, or on the command line. Can I get at the STDERR or STDOUT of the commands that tut is executing?The text was updated successfully, but these errors were encountered: