View Single Post
Old 09-29-2018, 05:15 PM   #1230
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,691
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
So long as none of the various entry point functions' parameter numbers/orders are altered (there are several existing plugins and wrapper programs that use KindleUnpack pieces via import), feel free to submit a pull request on github. But we can discuss it here, I think.

I think most of the people still using the standalone version of KindleUnpack are probably using it for debugging problematic Kindlebooks. So they tend to want as much output as possible for that purpose. For those using the various plugin-ized versions of KindleUnpack, the debug output doesn't really matter anyway.

I'm not opposed to the idea. I just don't know how utilized it would be. I always want to see all the print statements when I use kindleunpack from the command line. Needing to see everything is frankly why I'd be using the standalone version of KU from the command-line in the first place.

Last edited by DiapDealer; 09-29-2018 at 05:20 PM.
DiapDealer is online now   Reply With Quote