llines(1) [debian man page]
llines(1) General Commands Manual llines(1) NAME
llines - LifeLines genealogy program SYNOPSIS
llines [OPTION]... llines [OPTION]...Database DESCRIPTION
llines invokes the LifeLines genealogy program. For up to date documentation please refer to the Documentation section of this man page. LifeLines is a program to manipulate genealogical information in lineage-linked GEDCOM format. It has a curses interface, and a built-in interpreter for its own genealogical report language. OPTIONS
The following options are some of the options available for llines. -C Specify configuration file location. -F Finnish option (only available if compiled with Finnish flag) -I Specify a user property (e.g. -ILLEDITOR=gvim) -a Log dynamic memory operation (for debugging) -c Supply cache values (eg, -ci400,4000f400,4000 sets direct indi & fam caches to 400, and indirect indi & fam caches to 4000) -d Developmental/debug mode (signals are not caught) -f Force open a database (only for use if reader/writer count is wrong) -i Open database with immutable access (no protection against other access -- for use on read-only media) -k Always show key values (normally key is not shown if a REFN is shown) -l Lock (-ly) or unlock (-ln) a database for use with read only media (access to a locked database is treated as immutable) -n Do not use traditional family rules -o Specify program output filename (eg, -o/tmp/mytests) -r Open database with read-only access (protect against other writer access) -uCOLS,ROWS Specify window size (eg, -u120,34 specifies 120 columns by 34 rows) -w Open database with writeable access (protecte against other reader or writer access) -x Execute a single lifelines report program directly -z Use normal ASCII characters for drawing lines in user interface rather than the vt100 special characters -? Display options summary, (on UNIX or Linux use the -h option) llexec is a version of llines without the user interface for non-interactive processing of report programs. (Typically used with the -x option.) dbverify is a utility program to verify Lifelines databases. For information about options, run dbverify with the -h option. FILES
/etc/lifelines.conf ~/.linesrc ~/lines.cfg ./linesrc ./lines.cfg Possible locations for Lifelines configuration file Lifelines looks for a configuration file for various settings. See section Sys- tem And User Properties in the userguide for details. DOCUMENTATION
The LifeLines documentation should be installed as part of the installation, and may also be viewed at the project site: http://life- lines.sourceforge.net. Look for ll-userguide and ll-reportmanual (with appropriate extensions for text, html and pdf formats). The normal installation process includes a large number of sample report programs that you can customize to suit your needs. In the directory con- taining these reports you should find a file named index.html which gives a very brief summary of each report. SEE ALSO
llexec(1), dbverify(1), btedit(1) Lifelines 3.0.61 2007 Aug llines(1)
Check Out this Related Man Page
COVER(1p) User Contributed Perl Documentation COVER(1p) NAME
cover - report coverage statistics VERSION
version 0.89 SYNOPSIS
cover -help -info -version -summary -report report_format -outputdir dir -select filename -ignore filename -select_re RE -ignore_re RE -write [db] -delete -dump_db -launch -silent -coverage criterion -test -gcov -make [make] -add_uncoverable_point -delete_uncoverable_point -clean_uncoverable_points -uncoverable_file [report specific options] coverage_database [coverage_database ...] DESCRIPTION
Report coverage statistics in a variety of formats. The summary option produces a short textual summary. Other reports are available by using the report option. The following reports are currently available: text - detailed textual summary html - detailed HTML reports OPTIONS
The following command line options are supported: -h -help - show help -i -info - show documentation -v -version - show version -silent - don't print informational messages (default off) -summary - give summary report (default on) -report report_format - report format (default html) -outputdir - directory for output (default db) -launch - launch report in viewer (if avail) (default off) -select filename - only report on the file (default all) -ignore filename - don't report on the file (default none) -select_re RE - append to REs of files to select (default none) -ignore_re RE - append to REs of files to ignore (default none) -write [db] - write the merged database (default off) -delete - drop database(s) (default off) -dump_db - dump database(s) (for debugging) (default off) -coverage criterion - report on criterion (default all available) -test - drop database(s) and run make test (default off) -gcov - run gcov to cover XS code (default on if using gcc) -make make_prog - use the given 'make' program for 'make test' other options specific to the report format REPORT FORMATS
Tool accepts -report option: html|html_minimal (default) HTML reporting. Percentage thresholds are color-coded and configurable via -report_c0 <integer>, -report_c1 <integer> and -report_c2 <integer>.: 0% 75% 90% 100% | .. | .. | .. | <c0 <c1 <c2 c3 red yellow orange green html_basic HTML reporting with syntax highlighting if PPI::HTML or Perl::Tidy module is detected. Like html|html_minimal reporting, percentage thresholds are color-coded and configurable. text Plain text reporting. compilation Like text but hacked to give a minimal output in a format similar to that output by Perl itself so that it's easier to step through the untested locations with Emacs compilation mode. DETAILS
Any number of coverage databases may be specified on the command line. These databases will be merged and the reports will be based on the merged information. If no databases are specified the default database (cover_db) will be used. The -write option will write out the merged database. If no name is given for the new database, the first database read in will be overwritten. When this option is used no reports are generated by default. Specify -select and -ignore options to report on specific files. Specify -coverage options to report on specific criteria. By default all available information on all criteria in all files will be reported. Available coverage options are statement, branch, condition, subroutine, and pod. However, if you know you only want coverage information for certain criteria it is better to only collect data for those criteria in the first place by specifying them at that point. This will make the data collection and reporting processes faster and less memory intensive. See the documentation for Devel::Cover for more information. The -test option will delete the databases and run your tests to generate new coverage data before reporting on it. Devel::Cover knows how to work with standard Perl Makefiles as well as Module::Build based distributions. For detailed instructions see the documentation for ExtUtils::MakeMaker at https://metacpan.org/module/ExtUtils::MakeMaker or for Module::Build at https://metacpan.org/module/Module::Build both of which come as standard in recent Perl distributions. The -gcov option will try to run gcov on any XS code. This requires that you are using gcc of course. If you are using the -test option will be turned on by default. EXIT STATUS
The following exit values are returned: 0 All operations were completed successfully. >0 An error occurred. SEE ALSO
Devel::Cover BUGS
Did I mention that this is alpha code? See the BUGS file. LICENCE
Copyright 2001-2012, Paul Johnson (paul@pjcj.net) This software is free. It is licensed under the same terms as Perl itself. The latest version of this software should be available from my homepage: http://www.pjcj.net perl v5.14.2 2012-06-15 COVER(1p)