View Single Post
Old 07-18-2022, 06:00 AM   #90
un_pogaz
Chalut o/
un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.
 
un_pogaz's Avatar
 
Posts: 446
Karma: 672378
Join Date: Dec 2017
Device: Kobo
Quote:
Originally Posted by chaley View Post
For those who always run calibre in debug mode (calibre-debug -g), I added a tweak to stop printing exception tracebacks. This removes the many (!) lines you see when typing in the template tester, telling you that the program isn't valid. You will still see the exception reason as the output of the formatter. If the exception occurred while evaluating a composite column you will see a single log line naming the column.

In the plugin tweaks section, set
Code:
show_stack_traces_in_formatter = False
Oh, I'm interested, I had used the template dialog and it took me a while to stop panicking about all the exceptions I had introduced in my code.
But how do I use it? I add "show_stack_traces_in_formatter = False" in any tweark configuration or I edit directly "tweaks.json" ?
un_pogaz is offline   Reply With Quote