Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

calibre-debug(1) [debian man page]

CALIBRE-DEBUG(1)						      calibre							  CALIBRE-DEBUG(1)

NAME

       calibre-debug - part of calibre

SYNOPSIS

       calibre-debug  [options]

DESCRIPTION

       Run an embedded python interpreter.

       Whenever you pass arguments to calibre-debug that have spaces in them, enclose the arguments in quotation marks.

OPTIONS

       --version
	      show program's version number and exit

       -h, --help
	      show this help message and exit

       -c, --command
	      Run python code.

       -e, --exec-file
	      Run the python code in file.

       -d, --debug-device-driver
	      Debug the specified device driver.

       -g, --gui
	      Run the GUI with debugging enabled. Debug output is printed to stdout and stderr.

       --gui-debug
	      Run  the	GUI  with a debug console, logging to the specified path. For internal use only, use the -g option to run the GUI in debug
	      mode

       --show-gui-debug
	      Display the specified log file. For internal use only.

       -w, --viewer
	      Run the ebook viewer

       --paths
	      Output the paths necessary to setup the calibre environment

       --migrate
	      Migrate old database. Needs two arguments. Path to library1.db and path to new library folder.

       --add-simple-plugin
	      Add a simple plugin (i.e. a plugin that consists of only a .py file), by specifying the path to the py file  containing  the  plugin
	      code.

       --reinitialize-db
	      Re-initialize the sqlite calibre database at the specified path. Useful to recover from db corruption. You can also specify the path
	      to an SQL dump which will be used instead of trying to dump the database. This can be useful when dumping fails,	but  dumping  with
	      sqlite3 works.

       -p, --py-console
	      Run python console

       -m, --inspect-mobi
	      Inspect the MOBI file(s) at the specified path(s)

       --tweak-book
	      Tweak  the  book (exports the book as a collection of HTML files and metadata, which you can edit using standard HTML editing tools,
	      and then rebuilds the file from the edited HTML. Makes no additional changes to the HTML, unlike a full calibre conversion).

       --test-build
	      Test binary modules in build

SEE ALSO

       The User Manual is available at http://manual.calibre-ebook.com

       Created by Kovid Goyal <kovid@kovidgoyal.net>

calibre-debug (calibre 0.8.51)					   January 2013 						  CALIBRE-DEBUG(1)

Check Out this Related Man Page

IPC::Run::Debug(3)					User Contributed Perl Documentation					IPC::Run::Debug(3)

NAME

       IPC::Run::Debug - debugging routines for IPC::Run

SYNOPSIS

	  ##
	  ## Environment variable usage
	  ##
	  ## To force debugging off and shave a bit of CPU and memory
	  ## by compile-time optimizing away all debugging code in IPC::Run
	  ## (debug => ...) options to IPC::Run will be ignored.
	  export IPCRUNDEBUG=none

	  ## To force debugging on (levels are from 0..10)
	  export IPCRUNDEBUG=basic

	  ## Leave unset or set to "" to compile in debugging support and
	  ## allow runtime control of it using the debug option.

DESCRIPTION

       Controls IPC::Run debugging.  Debugging levels are now set by using words, but the numbers shown are still supported for backwards
       compatibility:

	  0  none	  disabled (special, see below)
	  1  basic	  what's running
	  2  data	  what's being sent/recieved
	  3  details	  what's going on in more detail
	  4  gory	  way too much detail for most uses
	  10 all	  use this when submitting bug reports
	     noopts	  optimizations forbidden due to inherited STDIN

       The "none" level is special when the environment variable IPCRUNDEBUG is set to this the first time IPC::Run::Debug is loaded: it prevents
       the debugging code from being compiled in to the remaining IPC::Run modules, saving a bit of cpu.

       To do this in a script, here's a way that allows it to be overridden:

	  BEGIN {
	     unless ( defined $ENV{IPCRUNDEBUG} ) {
		eval 'local $ENV{IPCRUNDEBUG} = "none"; require IPC::Run::Debug"'
		   or die $@;
	     }
	  }

       This should force IPC::Run to not be debuggable unless somebody sets the IPCRUNDEBUG flag; modify this formula to grep @ARGV if need be:

	  BEGIN {
	     unless ( grep /^--debug/, @ARGV ) {
		eval 'local $ENV{IPCRUNDEBUG} = "none"; require IPC::Run::Debug"'
		or die $@;
	  }

       Both of those are untested.

AUTHOR

       Barrie Slaymaker <barries@slaysys.com>, with numerous suggestions by p5p.

perl v5.12.1							    2010-04-01							IPC::Run::Debug(3)
Man Page