View Single Post
Old 12-22-2024, 01:47 PM   #553
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,884
Karma: 6120478
Join Date: Nov 2009
Device: many
No ideas here at all. On macOS, I always directly edit the plugin.py (or whatever py file I am debugging) inside my local Library/Application Support/sigil-ebook/sigil/plugins/MYPLUGINFOLDER/ and save it.

I just make sure to always close completely out of the Sigil Plugin Runner dialog first before editing anything.

I have never needed to change versions in plugin.xml file or reinstall.

I keep Sigil open and running with a test epub while doing this. I can repeatedly launch the plugin and get my output in the Sigil Plugin Runner console (as long as I change plugin.py to return a -1 indicating error always until fully debugged).

So very fast: "run - see output or errors - modify - run" cycles are possible.

Last edited by KevinH; 12-22-2024 at 02:44 PM.
KevinH is online now   Reply With Quote