Quote:
Originally Posted by thiago.eec
I prefer to open calibre as 'calibre-debug -g' from the terminal. This way I can restart many times while debugging.
|
Hey thiago.ecc, thanks for the suggestion.
I tried that using this bat script
C:\CALIBRE_8\Calibre\calibre-debug.exe -g
That's a portable install; I do most tests using portable calibre instances (different versions, distinct settings). What happens is that, when running it that way I have my system default library open instead of the one in the portable path. And it loads settings from the OS install as well... (%appdata%\calibre)
At one point I also tried Kovid's original way of debugging using calibre-customize but couldn't adapt it to my workflow with portable instances.
I get this when running --paths..
C:\CALIBRE_8\Calibre>C:\CALIBRE_8\Calibre\calibre-debug.exe --paths
CALIBRE_RESOURCES_PATH=C:\CALIBRE_8\Calibre\app\re sources
CALIBRE_EXTENSIONS_PATH=C:\CALIBRE_8\Calibre\app\b in
CALIBRE_PYTHON_PATH=
What's the correct way to debug a portable instance, loading the settings and library from the portable install path?