Thread: Print() in Restart in debug mode
View Single Post
Old 12-20-2022, 04:44 AM   #1
lktr45
Zealot
lktr45 knows the difference between 'who' and 'whom'lktr45 knows the difference between 'who' and 'whom'lktr45 knows the difference between 'who' and 'whom'lktr45 knows the difference between 'who' and 'whom'lktr45 knows the difference between 'who' and 'whom'lktr45 knows the difference between 'who' and 'whom'lktr45 knows the difference between 'who' and 'whom'lktr45 knows the difference between 'who' and 'whom'lktr45 knows the difference between 'who' and 'whom'lktr45 knows the difference between 'who' and 'whom'lktr45 knows the difference between 'who' and 'whom'
 
Posts: 135
Karma: 10280
Join Date: Oct 2016
Device: none
Print() in Restart in debug mode
Hello,

Since version 6.4 of Calibre, I no longer see the Print() in the log file in Restart in debug mode (CTRL+Shift+R).
On the other hand, the Print() appear well in the console with the calibre-debug -g command.

For example, if I run the Comments Cleaner plugin:
- calibre-debug -g command, I get the DEBUG lines in the console
- Restart in debug mode: no DEBUG lines in the log file

For my personal plugin tests, I use Calibre Portable and when I created a bug to report the problem, I forgot to specify that I was in Restart in debug mode. The bug was invalidated by Kovid rightly, either because he checked with the command, or indeed the Print() appeared well in Restart in debug mode.

I'm on Windows 10 and maybe I have an environment problem.

1- Could someone confirm (or not) that the Print() appear in the log file in Restart in debug mode?
2 - Is it possible to launch Calibre Portable with the calibre-debug -g command?

Thank you for your answers
lktr45 is offline   Reply With Quote