diff options
| author | Karl Berry <karl@freefriends.org> | 2017-11-20 22:01:59 +0000 |
|---|---|---|
| committer | Karl Berry <karl@freefriends.org> | 2017-11-20 22:01:59 +0000 |
| commit | 16db2735dd5c2cd2aa72643ed707730eb62e5bb1 (patch) | |
| tree | 009a21f673192e806c3b4143d9ab932e371b5620 | |
| parent | 21337afd777f807a4932c5b0a106798dcfd9d626 (diff) | |
latexmk (20nov17)
git-svn-id: svn://tug.org/texlive/trunk@45867 c570f23f-e606-0410-a88d-b1316a301751
| -rwxr-xr-x | Build/source/texk/texlive/linked_scripts/latexmk/latexmk.pl | 221 | ||||
| -rw-r--r-- | Master/texmf-dist/doc/man/man1/latexmk.1 | 370 | ||||
| -rw-r--r-- | Master/texmf-dist/doc/man/man1/latexmk.man1.pdf | bin | 148846 -> 182837 bytes | |||
| -rw-r--r-- | Master/texmf-dist/doc/support/latexmk/CHANGES | 38 | ||||
| -rw-r--r-- | Master/texmf-dist/doc/support/latexmk/INSTALL | 2 | ||||
| -rw-r--r-- | Master/texmf-dist/doc/support/latexmk/README | 12 | ||||
| -rw-r--r-- | Master/texmf-dist/doc/support/latexmk/example_rcfiles/bib2gls_latexmkrc | 35 | ||||
| -rw-r--r-- | Master/texmf-dist/doc/support/latexmk/example_rcfiles/glossary_latexmkrc | 32 | ||||
| -rwxr-xr-x | Master/texmf-dist/doc/support/latexmk/extra-scripts/dvipdfm_call.bat | 36 | ||||
| -rwxr-xr-x | Master/texmf-dist/doc/support/latexmk/extra-scripts/dvipdfmx_call.bat | 36 | ||||
| -rw-r--r-- | Master/texmf-dist/doc/support/latexmk/latexmk.pdf | bin | 174974 -> 182806 bytes | |||
| -rw-r--r-- | Master/texmf-dist/doc/support/latexmk/latexmk.txt | 3042 | ||||
| -rwxr-xr-x | Master/texmf-dist/scripts/latexmk/latexmk.pl | 221 | ||||
| -rwxr-xr-x | Master/texmf-dist/source/support/latexmk/latexmk.bat | 10 |
14 files changed, 2320 insertions, 1735 deletions
diff --git a/Build/source/texk/texlive/linked_scripts/latexmk/latexmk.pl b/Build/source/texk/texlive/linked_scripts/latexmk/latexmk.pl index 0a84e0e647a..343fc01dc6e 100755 --- a/Build/source/texk/texlive/linked_scripts/latexmk/latexmk.pl +++ b/Build/source/texk/texlive/linked_scripts/latexmk/latexmk.pl @@ -1,5 +1,7 @@ #!/usr/bin/env perl +# SEE "POSSIBLE BUG" aournd line 2221 + # ?? Still need to fix bcf error issue. # Don't keep looping after error # pvc: Only re-run on USER FILE CHANGE. @@ -121,13 +123,13 @@ use warnings; $my_name = 'latexmk'; $My_name = 'Latexmk'; -$version_num = '4.52c'; -$version_details = "$My_name, John Collins, 19 Jan. 2017"; +$version_num = '4.54'; +$version_details = "$My_name, John Collins, 20 Nov. 2017"; use Config; use File::Basename; use File::Copy; -use File::Glob ':glob'; # Better glob. Does not use space as item separator. +use File::Glob ':bsd_glob'; # Better glob. Does not use space as item separator. use File::Path 2.08 qw( make_path ); use FileHandle; use File::Find; @@ -195,9 +197,43 @@ else { ## ## 12 Jan 2012 STILL NEED TO DOCUMENT some items below ## +## 20 Nov 2017 John Collins Ver. 4.54 +## 18 Nov 2017 John Collins Add item to @file_not_found for generic +## package warning about "No file", as produced +## by glossaries-extra. +## In run_bibtex, make change in environment +## be local, not global. +## 4 Sep 2017 John Collins Restore default of $analyze_input_log_always +## to 1. This restores the default detection +## of certain constructs for dependencies for +## input files in the .log file. See the +## comments on this variable. This corrects +## a problem caused by a change in the +## behavior of lualatex in TeXLive 2017. +## 2 Sep 2017 John Collins Remove insertion of name of deps file in +## list of targets in deps file. +## Don't print deps info in deps mode (unless +## diagnostics on). +## 1 Sep 2017 John Collins Customized default previewers for MSys +## 14 Jul 2017 John Collins Correct collection of timing information so +## that it works even in silent mode +## 14 Jun 2017 John Collins Extra value for $bibtex_use +## 12 Jun 2017 John Collins Change glob to bsd_glob, since +## File::Glob's glob is now deprecated. +## Remove unused glob_list. +## 16 May 2017 John Collins Optimize away current directory string in +## $out_dir and $aux_dir. +## 15 May 2017 John Collins Fix incorrect deletion of non-generated +## aux files. +## 13 May 2017 John Collins Correct ordering of list of options given +## by -help +## 6 Apr 2017 John Collins In deps_list, correct bug in identifying +## generated files. Otherwise, generated files +## may be identified as true source files. ## 19 Jan 2017 John Collins Make -jobname work with -pdfxe and -pdflua -## (v. 4.53c) -## 17 Jan 2017 John Collins Fix bbl file detection bug. +## 18 Jan 2017 John Collins Update to v. 4.53. +## 17 Jan 2017 John Collins Update to v. 4.52b (official release). +## Fix bbl file detection bug. ## Bbl files were previously only identified ## from occurrence as input files in log ## file rather than from fls as well. @@ -299,6 +335,7 @@ $log_wrap = 79; '.*?:\\d*: LaTeX Error: File `([^\\\']*)\\\' not found\\.', '^LaTeX Warning: File `([^\\\']*)\\\' not found', '^Package .* [fF]ile `([^\\\']*)\\\' not found', + '^Package .* No file `([^\\\']*)\\\'', 'Error: pdflatex \(file ([^\)]*)\): cannot find image file', ': File (.*) not found:\s*$', '! Unable to load picture or PDF file \\\'([^\\\']+)\\\'.', @@ -527,12 +564,22 @@ $bibtex = 'bibtex %O %B'; # Switch(es) to make biber & bibtex silent: $biber_silent_switch = '--onlylog'; $bibtex_silent_switch = '-terse'; -$bibtex_use = 1; # Whether to actually run bibtex to update bbl files - # 0: Never run bibtex +$bibtex_use = 1; # Whether to actually run bibtex to update bbl files. + # This variable is also used in deciding whether to + # delete bbl files in clean up operations. + # 0: Never run bibtex. + # Do NOT delete bbl files on clean up. # 1: Run bibtex only if the bibfiles exists # according to kpsewhich, and the bbl files - # appear to be out-of-date + # appear to be out-of-date. + # Do NOT delete bbl files on clean up. + # 1.5: Run bibtex only if the bibfiles exists + # according to kpsewhich, and the bbl files + # appear to be out-of-date. + # Only delete bbl files on clean up if bibfiles exist. # 2: Run bibtex when the bbl files are out-of-date + # Delete bbl files on clean up. + # # In any event bibtex is only run if the log file # indicates that the document uses bbl files. @@ -661,8 +708,8 @@ $MSWin_fudge_break = 1; # Give special treatment to ctrl/C and ctrl/break # System-dependent overrides: # Currently, the cases I have tests for are: MSWin32, cygwin, linux and -# darwin, with the main complications being for MSWin32 and cygwin. -# Special treatment may also be useful for MSYS (for which $^O reports +# darwin, msys, with the main complications being for MSWin32 and cygwin. +# Further special treatment may also be useful for MSYS (for which $^O reports # "msys"). This is another *nix-emulation/system for MSWindows. At # present it is treated as unix-like, but the environment variables # are those of Windows. (The test for USERNAME as well as USER was @@ -846,6 +893,13 @@ elsif ( $^O eq "cygwin" ) { $pid_position = -1; # offset of PID in output of pscmd. # Negative means I cannot use ps } +elsif ( $^O eq "msys" ) { + $pdf_previewer = q[sh -c 'start %S']; + $ps_previewer = q[sh -c 'start %S']; + $dvi_previewer = q[sh -c 'start %S']; + $ps_previewer_landscape = $ps_previewer; + $dvi_previewer_landscape = "$dvi_previewer"; +} else { # Assume anything else is UNIX or clone @@ -1049,10 +1103,26 @@ $silent = 0; # Silence latex's messages? $silence_logfile_warnings = 0; # Do list warnings in log file $kpsewhich_show = 0; # Show calls to and results from kpsewhich $landscape_mode = 0; # default to portrait mode -$analyze_input_log_always = 0; # Always analyze .log for input files in the +$analyze_input_log_always = 1; # Always analyze .log for input files in the # <...> and (...) constructions. Otherwise, only # do the analysis when fls file doesn't exist or is # out of date. + # Under normal circumstances, the data in the fls file + # is reliable, and the test of the log file gets lots + # of false positives; usually $analyze_input_log_always + # is best set to zero. But the test of the log file + # is needed at least in the following situation: + # When a user needs to persuade latexmk that a certain + # file is a source file, and latexmk doesn't otherwise + # find it. User code causes line with (...) to be + # written to log file. One important case is for + # lualatex, which doesn't always generate lines in the + # .fls file for input lua files. (The situation with + # lualatex is HIGHLY version dependent, e.g., between + # 2016 and 2017.) + # To keep backward compatibility with older versions + # of latexmk, the default is to set + # $analyze_input_log_always to 1. # The following two arrays contain lists of extensions (without # period) for files that are read in during a (pdf)LaTeX run but that @@ -1522,6 +1592,7 @@ while ($_ = $ARGV[0]) elsif (/^-bibtex-$/) { $bibtex_use = 0; } elsif (/^-nobibtex$/) { $bibtex_use = 0; } elsif (/^-bibtex-cond$/) { $bibtex_use = 1; } + elsif (/^-bibtex-cond1$/) { $bibtex_use = 1.5; } elsif (/^-c$/) { $cleanup_mode = 2; $cleanup_fdb = 1; $cleanup_only = 1; } elsif (/^-C$/ || /^-CA$/ ) { $cleanup_mode = 1; $cleanup_fdb = 1; $cleanup_only = 1; } elsif (/^-CF$/) { $cleanup_fdb = 1; } @@ -1753,17 +1824,20 @@ if ( $bad_options > 0 ) { warn "$My_name: This is $version_details, version: $version_num.\n", unless $silent; + if ( ($out_dir ne '') && ($aux_dir eq '') ){ $aux_dir = $out_dir; } -# Versions terminating in directory/path separator +# Normalize versions terminating in directory/path separator +# and versions referring to current directory $out_dir1 = $out_dir; $aux_dir1 = $aux_dir; foreach ( $aux_dir1, $out_dir1 ) { if ( ($_ ne '') && ! m([\\/\:]$) ) { $_ .= '/'; } + while ( s[^\.\/][] ) {} } # At least one widely package (revtex4-1) generates a bib file @@ -2190,6 +2264,8 @@ foreach $filename ( @file_list ) my %other_generated = (); my @index_bibtex_generated = (); my @aux_files = (); + my @missing_bib_files = (); + my $bibs_all_exist = 0; $have_fdb = 0; if ( -e $fdb_name ) { print "$My_name: Examining fdb file '$fdb_name' for rules ...\n" @@ -2207,15 +2283,29 @@ foreach $filename ( @file_list ) elsif ( $rule =~ /^(bibtex|biber)/ ) { push @index_bibtex_generated, $$Pdest, "$base.blg"; push @aux_files, $$Psource; - } + if ( $bibtex_use == 1.5) { + foreach ( keys %$PHsource ) { + if ( ( /\.bib$/ ) && (! -e $_) ) { + push @missing_bib_files, $_; + } + } + } + } elsif ( exists $other_generated{$$Psource} ) { - $other_generated{$$Pdest}; +# print "=========== CHECKING: source file of rule '$rule', '$$Psource'\n", +# " is a generated file.\n"; + ## OLD with apparent bug: + #$other_generated{$$Pdest}; } + foreach my $key (keys %$PHdest) { + $other_generated{$key} = 1; + } }, sub { # Find generated files at source file level if ( $file =~ /\.aux$/ ) { push @aux_files, $file; } } - ); + ); + if ($#missing_bib_files == -1) { $bibs_all_exist = 1; } } elsif ( -e $log_name ) { # No fdb file, but log file exists, so do inferior job by parse_log @@ -2242,21 +2332,34 @@ foreach $filename ( @file_list ) if ( ($go_mode == 2) && !$silent ) { warn "$My_name: Removing all generated files\n" unless $silent; } - if ($bibtex_use < 2) { - delete $generated_exts_all{'bbl'}; + my $keep_bbl = 1; + if ( ($bibtex_use > 1.6) + || + ( ($bibtex_use == 1.5) && ($bibs_all_exist) ) + ) { + $keep_bbl = 0; + } + if ($keep_bbl) { + delete $generated_exts_all{'bbl'}; } # Convert two arrays to hashes: my %index_bibtex_generated = (); my %aux_files = (); + my %aux_files_to_save = (); foreach (@index_bibtex_generated) { $index_bibtex_generated{$_} = 1 - unless ( /\.bbl$/ && ($bibtex_use < 2) ); + unless ( /\.bbl$/ && ($keep_bbl) ); delete( $other_generated{$_} ); } foreach (@aux_files) { - $aux_files{$_} = 1; - delete( $other_generated{$_} ); + if (exists $other_generated{$_} ) { + $aux_files{$_} = 1; + } + else { + $aux_files_to_save{$_} = 1; + } } + if ($diagnostics) { show_array( "For deletion, the following were determined from fdb file or log file:\n" ." Generated (from makeindex and bibtex):", @@ -2265,9 +2368,12 @@ foreach $filename ( @file_list ) show_array( " Other generated files:\n" ." (only deleted if \$cleanup_includes_generated is set): ", keys %other_generated ); - show_array( " Yet other generated files:\n", + show_array( " Yet other generated files are specified by patterns:\n". + " Explicit pattern with %R or root-filename.extension:", keys %generated_exts_all ); + show_array( " Aux files to SAVE and not delete:", keys %aux_files_to_save ); } + &cleanup1( $aux_dir1, $fdb_ext, 'blg', 'ilg', 'log', 'aux.bak', 'idx.bak', split('\s+',$clean_ext), keys %generated_exts_all @@ -3249,8 +3355,8 @@ sub cleanup1 { my $dir = fix_pattern( shift ); my $root_fixed = fix_pattern( $root_filename ); foreach (@_) { - (my $name = /%R/ ? $_ : "%R.$_") =~ s/%R/$dir$root_fixed/; - unlink_or_move( glob( "$name" ) ); + (my $name = /%R/ ? $_ : "%R.$_") =~ s/%R/${dir}${root_fixed}/; + unlink_or_move( bsd_glob( "$name" ) ); } } #END cleanup1 @@ -3370,7 +3476,9 @@ sub print_help " - Currently this only works with MiKTeX\n", " -bibtex - use bibtex when needed (default)\n", " -bibtex- - never use bibtex\n", - " -bibtex-cond - use bibtex when needed, but only if the bib files exist\n", + " -bibtex-cond - use bibtex when needed, but only if the bib file exists\n", + " -bibtex-cond1 - use bibtex when needed, but only if the bib file exists;\n", + " on cleanup delete bbl file only if bib file exists\n", " -bm <message> - Print message across the page when converting to postscript\n", " -bi <intensity> - Set contrast or intensity of banner\n", " -bs <scale> - Set scale for banner\n", @@ -3416,6 +3524,8 @@ sub print_help " give list of warnings after run of (pdf)latex\n", " -logfilewarninglist- or -logfilewarnings- \n", " do not give list of warnings after run of (pdf)latex\n", + " -lualatex - use lualatex for processing files to pdf\n", + " and turn dvi/ps modes off\n", " -M - Show list of dependent files after processing\n", " -MF file - Specifies name of file to receives list dependent files\n", " -MP - List of dependent files includes phony target for each source file.\n", @@ -3472,8 +3582,6 @@ sub print_help " -view=none - no viewer is used\n", " -view=ps - viewer is for ps\n", " -view=pdf - viewer is for pdf\n", - " -lualatex - use lualatex for processing files to pdf\n", - " and turn dvi/ps modes off\n", " -xelatex - use xelatex for processing files to pdf\n", " and turn dvi/ps modes off\n", "\n", @@ -3665,6 +3773,8 @@ sub check_biber_log { sub run_bibtex { my $return = 999; + # Prevent changes we make to environment becoming global: + local %ENV = %ENV; if ( $aux_dir ) { # Use \Q and \E round directory name in regex to avoid interpretation # of metacharacters in directory name: @@ -5919,7 +6029,7 @@ sub deps_list { # Call: deps_list(fh) # List dependent files to file open on fh my $fh = $_[0]; - print $fh "#===Dependents for $filename:\n"; + print $fh "#===Dependents, and related info, for $filename:\n"; my @dest_exts = (); if ($pdf_mode) {push @dest_exts, '.pdf';} if ($dvi_mode) {push @dest_exts, '.dvi';} @@ -5929,25 +6039,35 @@ sub deps_list { my @accessible_all = rdb_accessible( keys %requested_filerules ); rdb_for_some( \@accessible_all, - sub{ + sub{ # foreach (keys %$PHdest) { print "----- $_\n"; } push @generated, keys %$PHdest; }, sub{ $source{$file} = 1; } ); foreach (keys %generated_exts_all) { - (my $name = /%R/ ? $_ : "%R.$_") =~ s/%R/$root_filename/; + (my $name = /%R/ ? $_ : "%R.$_") =~ s/%R/${aux_dir1}${root_filename}/; push @generated, $name; } + show_array( "Generated:", @generated ) if $diagnostics; foreach (@generated) { delete $source{$_}; } + show_array( "Sources:", keys %source ) if $diagnostics; foreach my $ext (@dest_exts) { - if ($deps_file eq '-' ) { - print $fh "${out_dir1}${root_filename}${ext} :"; - } else { - print $fh "${out_dir1}${root_filename}${ext} $deps_file :"; - } + # Don't insert name of deps file in targets. + # The previous behavior of inserting the name of the deps file + # matched the method recommended by GNU make for automatically + # generated prerequisites -- see Sec. "Generating Prerequisites + # Automatically" of GNU make manual (v. 4.2). But this can + # cause problems in complicated cases, and as far as I can see, + # it doesn't actually help, despite the reasoning given. + # The only purpose of the deps file is to to determine source + # files for a particular rule. The files whose changes make the + # deps file out-of-date are the same as those that make the real + # target file (e.g., .pdf) out-of-date. So the GNU method seems + # completely unnecessary. + print $fh "${out_dir1}${root_filename}${ext} :"; foreach (sort keys %source) { print $fh "\\\n $_"; } @@ -6328,7 +6448,7 @@ sub rdb_make1 { if ($bibtex_use == 0) { $bibtex_not_run = 2; } - elsif ($bibtex_use == 1) { + elsif ( ($bibtex_use == 1) || ($bibtex_use == 1.5) ) { foreach ( keys %$PHsource ) { if ( ( /\.bib$/ ) && (! -e $_) ) { push @missing_bib_files, $_; @@ -6474,7 +6594,7 @@ sub rdb_make1 { # Missing output file was reported to be NOT an error $$Pout_of_date = 0; } - elsif ( ($bibtex_use <= 1) && ($bibtex_not_run > 0) ) { + elsif ( ($bibtex_use <= 1.5) && ($bibtex_not_run > 0) ) { # Lack of destination file is not to be treated as an error # for a bibtex rule when latexmk is configured not to treat # this as an error, and the lack of a destination file is the @@ -7769,18 +7889,6 @@ sub Parray { #************************************************************ -sub glob_list { - # Glob a collection of filenames. Sort and eliminate duplicates - # Usage: e.g., @globbed = glob_list(string, ...); - my @globbed = (); - foreach (@_) { - push @globbed, glob; - } - return uniqs( @globbed ); -} - -#================================================== - sub glob_list1 { # Glob a collection of filenames. # But no sorting or elimination of duplicates @@ -7803,7 +7911,7 @@ sub glob_list1 { } else { # This glob fails to work as desired, if the pattern contains spaces. - push @globbed, glob( "$file_spec" ); + push @globbed, bsd_glob( "$file_spec" ); } } return @globbed; @@ -8463,8 +8571,15 @@ sub tempfile1 { sub Run_msg { # Same as Run, but give message about my running warn_running( "Running '$_[0]'" ); + return Run($_[0]); +} #END Run_msg + +#================== + +sub Run { + # This is wrapper around Run_no_time to capture timing information my $time1 = processing_time(); - my ($pid, $return) = Run($_[0]); + my ($pid, $return) = Run_no_time($_[0]); my $time = processing_time() - $time1; push @timings, "'$_[0]': time = $time\n"; return ($pid, $return); @@ -8472,9 +8587,9 @@ sub Run_msg { #================== -sub Run { -# Usage: Run ("command string"); -# or Run ("one-or-more keywords command string"); +sub Run_no_time { +# Usage: Run_no_time ("command string"); +# or Run_no_time ("one-or-more keywords command string"); # Possible keywords: internal, NONE, start, nostart. # # A command string not started by keywords just gives a call to system with diff --git a/Master/texmf-dist/doc/man/man1/latexmk.1 b/Master/texmf-dist/doc/man/man1/latexmk.1 index e970ff1d6b2..17d952ea214 100644 --- a/Master/texmf-dist/doc/man/man1/latexmk.1 +++ b/Master/texmf-dist/doc/man/man1/latexmk.1 @@ -1,4 +1,4 @@ -.TH LATEXMK 1 "19 January 2017" "" +.TH LATEXMK 1 "20 November 2017" "" .SH NAME latexmk \- generate LaTeX document .SH SYNOPSIS @@ -177,18 +177,22 @@ When the source file uses bbl files for bibliography, run bibtex or biber as needed to regenerate the bbl files. This property can also be configured by setting the \fI$bibtex_use\fR -variable to 2 in a configuration file +variable to 2 in a configuration file. .TP .B -bibtex- -Never run bibtex or biber. +Never run bibtex or biber. Also, always treat .bbl files as precious, +i.e., do not delete them in a cleanup operation. A common use for this option is when a document comes from an external source, complete with its bbl file(s), and the user does not have the corresponding bib files available. In this situation use of the \fB-bibtex-\fR option will prevent \fIlatexmk\fR from trying to run \fIbibtex\fR or \fIbiber\fR, which would result in overwriting of the -bbl files. +bbl files. + +This property can also be configured by setting the \fI$bibtex_use\fR +variable to 0 in a configuration file. .TP .B -bibtex-cond @@ -198,7 +202,21 @@ only if the relevant bib file(s) exist. Thus when the bib files are not available, \fIbibtex\fR or \fIbiber\fR is not run, thereby avoiding overwriting of -the bbl file(s). This is the default setting. +the bbl file(s). +Also, always treat .bbl files as precious, +i.e., do not delete them in a cleanup operation. + +This is the default setting. +It can also be configured by setting the \fI$bibtex_use\fR +variable to 1 in a configuration file. + +The reason for using this setting is that sometimes a .bbl file is +available containing the bibliography for a document, but the .bib +file is not available. An example would be for a scientific journal +where authors submit .tex and .bbl files, but not the original .bib +file. In that case, running \fIbibtex\fR or \fIbiber\fR would not +work, and the .bbl file should be treated as a user source file, and +not as a file that can be regenerated on demand. (Note that it is possible for \fIlatexmk\fR to decide that the bib file does not exist, even though the bib file does exist and @@ -213,6 +231,18 @@ search path as \fIbibtex\fR and \fIbiber\fR. If this problem arises, use the \fB-bibtex\fR option when invoking \fIlatexmk\fR.) .TP +.B -bibtex-cond1 +The same as \fB-bibtex-cond1\fR except that .bbl files are only +treated as precious if one or more bibfiles fails to exist. + +Thus if all the bib files exist, \fIbibtex\fR or \fIbiber\fR is run to +generate .bbl files as needed, and then it is appropriate to delete +the bbl files in a cleanup operation since they can be re-generated. + +This property can also be configured by setting the \fI$bibtex_use\fR +variable to 1.5 in a configuration file. + +.TP .B -bm <message> A banner message to print diagonally across each page when converting the dvi file to postscript. The message must be a single argument on @@ -254,12 +284,22 @@ removed. This cleanup is instead of a regular make. See the \fB-gg\fR option if you want to do a cleanup then a make. -If \fI$bibtex_use\fR is set to 0 or 1, bbl files are counted as -non-regeneratable. +\fITreatment of .bbl files:\fR If \fI$bibtex_use\fR is set to 0 or 1, +bbl files are always treated as non-regeneratable. If +\fI$bibtex_use\fR is set to 1.5, bbl files are counted as +non-regeneratable conditionally: If the bib file exists, then bbl +files are regeneratable, and are deleted in a clean up. But if +\fI$bibtex_use\fR is 1.5 and a bib file doesn't exist, then the bbl +files are treated as non-regeneratable and hence are not deleted. -If \fI$cleanup_includes_cusdep_generated\fR is nonzero, regeneratable +In contrast, if \fI$bibtex_use\fR is set to 2, bbl files are always +treated as regeneratable, and are deleted in a cleanup. + +\fITreatment of files generated by custom dependencies:\fRIf +\fI$cleanup_includes_cusdep_generated\fR is nonzero, regeneratable files are considered as including those generated by custom -dependencies and are also deleted. Otherwise these files are not deleted. +dependencies and are also deleted. Otherwise these files are not +deleted. .TP .B -C @@ -271,8 +311,8 @@ in the \fI$clean_full_ext\fR configuration variable. This cleanup is instead of a regular make. See the \fB-gg\fR option if you want to do a cleanup than a make. -If \fI$bibtex_use\fR is set to 0 or 1, bbl files are counted as -non-regeneratable. +See the \fB-c\fR option for the specification of whether or not .bbl +files are treated as non-regeneratable or regeneratable. If \fI$cleanup_includes_cusdep_generated\fR is nonzero, regeneratable files are considered as including those generated by custom @@ -683,6 +723,12 @@ Turn off generation of pdf version of document. It may get overridden if some other option requires the generation of a pdf file.) +If after all options have been processed, pdf generation is still +turned off, then generation of a dvi file will be turned on, and then +the program used to compiled a document will be \fIlatex\fR (or, more +precisely, whatever program is configured to be used in the +\fI$latex\fR configuration variable). + .TP .B -pdflatex="COMMAND" This sets the string specifying the command to run \fIpdflatex\fR, and is @@ -1445,6 +1491,29 @@ applies only if preview-continuous mode (-pvc option) is used. See file is created. .TP +.B $analyze_input_log_always [1] + +After a run of latex (etc), always analyze .log for input files in the +<...> and (...) constructions. Otherwise, only do the analysis when +fls file doesn't exist or is out of date. + +Under normal circumstances, the data in the fls file is reliable, and +the test of the log file gets lots of false positives; usually +$analyze_input_log_always is best set to zero. But the test of the +log file is needed at least in the following situation: When a user +needs to persuade latexmk that a certain file is a source file, and +latexmk doesn't otherwise find it. Then the user can write code that +causes a line with (...) to be written to log file. One important +case is for lualatex, which doesn't always generate lines in the .fls +file for input lua files. (The situation with lualatex is HIGHLY +version dependent, e.g., there was a big change between TeXLive 2016 +and TeXLive 2017.) + +To keep backward compatibility with older versions +of latexmk, the default is to set +$analyze_input_log_always to 1. + +.TP .B $auto_rc_use [1] Whether to automatically read the standard initialization (rc) files, which are the system RC file, the user's RC file, and the RC file in @@ -1455,7 +1524,6 @@ automatic reading of the later RC files. This variable does not affect the reading of RC files specified on the command line by the \fB-r\fR option. - .TP .B $aux_dir [""] The directory in which auxiliary files (aux, log, etc) are to be @@ -1475,7 +1543,6 @@ what directory names are suitable. If you also use the \fB-cd\fR option, and \fI$out_dir\fR (or \fI$aux_dir\fR) contains a relative path, then the path is interpreted relative to the document directory. - .TP .B $banner [0] If nonzero, the banner message is printed across each page when @@ -1553,17 +1620,26 @@ from the log file that one (or more) are used, it can run \fIbibtex\fR or \fIbiber\fR whenever it appears necessary to regenerate the bbl file(s) from their source bib database file(s). - But sometimes, the bib file(s) are not available (e.g., for a document obtained from an external archive), but the bbl files are provided. -In that case use of \fIbibtex\fR or \fIbiber\fR will result in incorrect -overwriting of the precious bbl files. The variable \fI$bibtex_use\fR -controls whether this happens. Its possible values are: 0: never use -BibTeX or biber. 1: only use \fIbibtex\fR or \fIbiber\fR if the bib -files exist. -2: run \fIbibtex\fR or \fIbiber\fR whenever it appears necessary to +In that case use of \fIbibtex\fR or \fIbiber\fR will result in +incorrect overwriting of the precious bbl files. The variable +\fI$bibtex_use\fR controls whether this happens, and also controls +whether or not .bbl files are deleted in a cleanup operation. + +The possible values of \fI$bibtex_use\fR are: + 0: never use BibTeX or biber; +never delete .bbl files in a cleanup. + 1: only use \fIbibtex\fR or \fIbiber\fR if the bib files exist; +never delete .bbl files in a cleanup. + 1.5: only use \fIbibtex\fR or \fIbiber\fR if the bib files exist; +conditionally delete .bbl files in a cleanup (i.e., delete them only +when the bib files all exist). + 2: run \fIbibtex\fR or \fIbiber\fR whenever it appears necessary to update the bbl -files, without testing for the existence of the bib files. +files, without testing for the existence of the bib files; +always delete .bbl files in a cleanup. + .TP .B $cleanup_includes_cusdep_generated [0] If nonzero, specifies that cleanup also deletes files that are @@ -1605,7 +1681,6 @@ in an initialization file will imply that when a clean-up operation is specified, not only is the standard set of files deleted, but also files of the form FOO.out, FOO-blx.bib, and %R-figures*.log, where FOO stands for the basename of the file being processed (as in FOO.tex). - .TP .B $clean_full_ext [""] Extra extensions of files for \fIlatexmk\fR to remove when the \fB-C\fR @@ -1613,7 +1688,6 @@ option is selected, i.e., extensions of files to remove when the .dvi, etc files are to be cleaned-up. More general patterns are allowed, as for \fI$clean_ext\fR. - .TP .B $compiling_cmd [undefined], $failure_cmd [undefined], $success_cmd [undefined] @@ -1650,11 +1724,9 @@ the title of the edit window. The visual indication in a window title can useful, since the user does not have to keep shifting attention to the (possibly hidden) compilation window to know the status of the compilation. - .TP .B @cus_dep_list [()] Custom dependency list -- see section on "Custom Dependencies". - .TP .B @default_excluded_files [()] When \fIlatexmk\fR is invoked with no files specified on the command @@ -1681,7 +1753,6 @@ change the set of files to be processed. Notes: 1. This variable has no effect except when no files are specified on the \fIlatexmk\fR command line. 2. Wildcards are allowed in \fI@default_excluded_files\fR. - .TP .B @default_files [("*.tex")] Default list of files to be processed. @@ -1713,7 +1784,6 @@ filename specifications is possible. If you want \fIlatexmk\fR to process all .tex files with a few exceptions, see the \fI@default_excluded_files\fR array variable. - .TP .B $dependents_phony [0] If a list of dependencies is output, this variable determines whether @@ -1765,14 +1835,12 @@ appropriate to the operating system). But sometimes letting \fIlatexmk\fR do the detaching is not appropriate (for a variety of non-trivial reasons), so you should put the "start " bit in yourself, whenever it is needed. - .TP .B $dvi_previewer_landscape ["start xdvi %O %S"] The command to invoke a dvi-previewer in landscape mode. [Under MS-Windows the default is "start"; then \fIlatexmk\fR arranges to use the MS-Windows \fIstart\fR program, which will cause to be run whatever command the system has associated with .dvi files.] - .TP .B $dvipdf ["dvipdf %O %S %D"] Command to convert dvi to pdf file. A common reconfiguration is to @@ -1784,7 +1852,6 @@ WARNING: The default dvipdf script generates pdf files with bitmapped fonts, which do not look good when viewed by acroread. That script should be modified to give dvips the options "-P pdf" to ensure that type 1 fonts are used in the pdf file. - .TP .B $dvipdf_silent_switch ["-q"] Switch(es) for dvipdf program when silent mode is on. @@ -1961,7 +2028,6 @@ STDOUT of running the command is then piped to \fIlatexmk\fR.) See also the \fI@BIBINPUTS\fR variable for another way that \fIlatexmk\fR also uses to try to locate files; it applies only in the case of .bib files. - .TP .B $kpsewhich_show [0] Whether to show diagnostics about invocations of \fIkpsewhich\fR: the @@ -1970,7 +2036,6 @@ shown if \fI$kpsewhich_show\fR is non-zero or if diagnostics mode is on. (But in the second case, lots of other diagnostics are also shown.) Without these diagnostics there is nothing visible in \fIlatexmk\fR's screen output about invocations of \fIkpsewhich\fR. - .TP .B $landscape_mode [0] If nonzero, run in landscape mode, using the landscape mode previewers and @@ -2015,7 +2080,6 @@ dependency for \fIlatexmk\fR, and should also have done the appropriate programming in the LaTeX source file to enable the file to be read. The standard extensions are handled by LaTeX and its graphics/graphicx packages. - .TP .B $latex_silent_switch ["-interaction=batchmode"] Switch(es) for the LaTeX processing program when silent mode is on. @@ -2060,12 +2124,10 @@ If \fIgsview\fR is installed in a different directory, you will need to make the appropriate change. Note the double quotes around the name: this is necessary because one part of the command name ("Program Files") contains a space which would otherwise be misinterpreted. - .TP .B $lualatex ["lualatex %O %S"] The LaTeX processing program that is to be used when the \fIlualatex\fR program is called for (e.g., by the option \fB-lualatex\fR. - .TP .B %lualatex_input_extensions This variable specifies the extensions tried by \fIlatexmk\fR when it finds @@ -2081,7 +2143,6 @@ are 'tex', 'pdf', 'jpg, and 'png'. See details of the \fI%latex_input_extensions\fR for other information that equally applies to \fI%lualatex_input_extensions\fR. - .TP .B $lualatex_silent_switch ["-interaction=batchmode"] Switch(es) for the \fIlualatex\fR program (specified in the variable @@ -2089,11 +2150,9 @@ Switch(es) for the \fIlualatex\fR program (specified in the variable See details of the \fI$latex_silent_switch\fR for other information that equally applies to \fI$lualatex_silent_switch\fR. - .TP .B $make ["make"] The make processing program. - .TP .B $makeindex ["makeindex %O -o %D %S"] The index processing program. @@ -2126,7 +2185,6 @@ It is conceivable that under certain situations this is undesirable, so the configuration can be changed. (A possible example might be when some of the software is implemented using Cygwin, which provides a Unix-like environment inside MS-Windows.) - .TP .B $new_viewer_always [0] This variable applies to \fIlatexmk\fR \fBonly\fR in @@ -2136,7 +2194,6 @@ same file, and if one is running will not start a new one. If \fI$new_viewer_always\fR is non-zero, this check will be skipped, and \fIlatexmk\fR will behave as if no viewer is running. .TP - .B $out_dir [""] If non-blank, this variable specifies the directory in which output files are to be written by a run of @@ -2169,7 +2226,6 @@ higher-level directory, and you need to use \fImakeindex\fR or operating system environment variable openout_any to "a" (as in "all"), to override the default "paranoid" setting. .TP - .B $pdf_mode [0] If zero, do NOT generate a pdf version of the document. If equal to 1, generate a pdf version of the document using \fIpdflatex\fR, @@ -2186,9 +2242,7 @@ document using \fIxelatex\fR, using the commands specified by the In \fI$pdf_mode\fR=2, it is ensured that dvi and ps files are also made. In \fI$pdf_mode\fR=3, it is ensured that a dvi file is also made. - .TP - .B $pdflatex ["pdflatex %O %S"] The LaTeX processing program in a version that makes a pdf file instead of a dvi file. @@ -2203,7 +2257,6 @@ to \fI$pdflatex\fR to allow the use of \fIlualatex\fR or \fIxelatex\fR instead of \fIpdflatex\fR. There are now separate configuration variables for the use of \fIlualatex\fR or \fIxelatex\fR. See \fI$lualatex\fR and \fI$xelatex\fR.) - .TP .B %pdflatex_input_extensions This variable specifies the extensions tried by \fIlatexmk\fR when it finds @@ -2219,7 +2272,6 @@ are 'tex', 'pdf', 'jpg, and 'png'. See details of the \fI%latex_input_extensions\fR for other information that equally applies to \fI%pdflatex_input_extensions\fR. - .TP .B $pdflatex_silent_switch ["-interaction=batchmode"] Switch(es) for the \fIpdflatex\fR program (specified in the variable @@ -2227,7 +2279,6 @@ Switch(es) for the \fIpdflatex\fR program (specified in the variable See details of the \fI$latex_silent_switch\fR for other information that equally applies to \fI$pdflatex_silent_switch\fR. - .TP .B $pdf_previewer ["start acroread %O %S"] The command to invoke a pdf-previewer. @@ -2260,7 +2311,6 @@ appropriate to the operating system). But sometimes letting \fIlatexmk\fR do the detaching is not appropriate (for a variety of non-trivial reasons), so you should put the "start " bit in yourself, whenever it is needed. - .TP .B $pdf_update_command [""] When the pdf previewer is set to be updated by running a command, this @@ -2290,7 +2340,6 @@ The first setting arranges for the xpdf program to be used in its "remote server mode", with the server name specified as the rootname of the TeX file. The second setting arranges for updating to be done in response to a command, and the third setting sets the update command. - .TP .B $pdf_update_signal [Under UNIX: SIGHUP, which is a system-dependent value] The number of the signal that is sent to the pdf viewer when it is @@ -2405,18 +2454,15 @@ that for the value 4, to run a command to do the update, the command is specified by the variable \fI$ps_update_command\fR, and for the value 2, to specify update by signal, the signal is specified by \fI$ps_update_signal\fR.) - .TP .B $ps_update_signal [Under UNIX: SIGHUP, which is a system-dependent value] The number of the signal that is sent to the pdf viewer when it is updated by sending a signal -- see \fI$ps_update_method\fR. The default value is the one appropriate for gv on a UNIX system. - .TP .B $pvc_view_file_via_temporary [1] The same as \fI$always_view_file_via_temporary\fR, except that it only applies in preview-continuous mode (-pvc option). - .TP .B $quote_filenames [1] This specifies whether substitutions for placeholders in command @@ -2452,7 +2498,6 @@ Document.fls. However, some implementations instead produce files named for the program, i.e., latex.fls or pdflatex.fls. In this second case, \fIlatexmk\fR copies the latex.fls or pdflatex.fls to a file with the basename of the main LaTeX document, e.g., Document.fls. - .TP .B $search_path_separator [See below for default] The character separating paths in the environment variables TEXINPUTS, @@ -2478,11 +2523,9 @@ you'll need to find out what is needed, and set \fI$search_path_separator\fR explicitly. (The same goes, of course, for unusual operating systems that are not in the MSWin, Linux, OS-X, Unix collection.) - .TP .B $show_time [0] Whether to show CPU time used. - .TP .B $silence_logfile_warnings [0] Whether after a run of (pdf)latex to summarize warnings in the log @@ -2498,12 +2541,10 @@ warnings. The command line options Note that multiple occurrences for the same undefined object on the same page and same line will be compressed to a single warning. - .TP .B $silent [0] Whether to run silently. Setting $silent to 1 has the same effect as the \fB-quiet\fR of \fB-silent\fR options on the command line. - .TP .B $sleep_time [2] The time to sleep (in seconds) between checking for source file @@ -2521,11 +2562,9 @@ For backward compatibility, if you choose to set \fI$texfile_search\fR, it is a string of space-separated filenames, and then \fIlatexmk\fR replaces \fI@default_files\fR with the filenames in \fI$texfile_search\fR to which is added "*.tex". - .TP .B $success_cmd [undefined] See the documentation for $compiling_cmd. - .TP .B $tmpdir [See below for default] Directory to store temporary files that \fIlatexmk\fR may generate while @@ -2557,24 +2596,20 @@ Which kind of file is to be previewed if a previewer is used. The possible values are "default", "dvi", "ps", "pdf". The value of "default" means that the "highest" of the kinds of file generated is to be used (among dvi, ps and pdf). - .TP .B $xdvipdfmx ["xdvipdfmx -o %D %O %S"] The program to make a pdf file from an xdv file (used in conjunction with \fIxelatex\fR when \fI$pdf_mode\fR=5). - .TP .B $xdvipdfmx_silent_switch ["-q"] Switch(es) for the \fIxdvipdfmx\fR program when silent mode is on. - .TP .B $xelatex ["xelatex %O %S"] The LaTeX processing program of in a version that makes a pdf file instead of a dvi file, when the \fIxelatex\fR program is called for. See the documentation of the \fB-xelatex\fR option for some special properties of \fIlatexmk\fR's use of \fIxelatex\fR. - .TP .B %xelatex_input_extensions This variable specifies the extensions tried by \fIlatexmk\fR when it finds @@ -2590,7 +2625,6 @@ are 'tex', 'pdf', 'jpg, and 'png'. See details of the \fI%latex_input_extensions\fR for other information that equally applies to \fI%xelatex_input_extensions\fR. - .TP .B $xelatex_silent_switch ["-interaction=batchmode"] Switch(es) for the \fIxelatex\fR program (specified in the variable @@ -2606,20 +2640,23 @@ that equally applies to \fI$xelatex_silent_switch\fR. In any RC file a set of custom dependencies can be set up to convert a file with one extension to a file with another. An example use of this would be to allow \fIlatexmk\fR to convert a \fI.fig\fR file to -\fI.eps\fR to be included in the \fI.tex\fR file. +\fI.eps\fR to be included in the \fI.tex\fR file. + +.SS Defining a custom dependency: +The old method of configuring \fIlatexmk\fR to use a custom dependency +was to directly manipulate the \fB@cus_dep_list\fR array that contains +information defining the custom dependencies. (See the section "Old Method of +Defining Custom Dependencies" for details.) This method still +works, but is no longer preferred. -The old method of configuring \fIlatexmk\fR was to directly manipulate -the \fB@cus_dep_list\fR array that contains information defining the -custom dependencies. This method still works. But now there are -subroutines that allow convenient manipulations of the custom -dependency list. These are +A better method is to use the subroutines that allow convenient +manipulations of the custom dependency list. These are add_cus_dep( fromextension, toextension, must, subroutine ) remove_cus_dep( fromextension, toextension ) show_cus_dep() -The custom dependency is a list of rules, each of which is specified -as follow: +The arguments are as follows: .TP .B from extension: The extension of the file we are converting from (e.g. "fig"). @@ -2641,14 +2678,28 @@ file conversion. The first argument to the subroutine is the base name of the file to be converted without any extension. The subroutines are declared in the syntax of \fIPerl\fR. The function should return 0 if it was successful and a nonzero number if it failed. + .PP + +Naturally \fIadd_cus_dep\fR adds a custom dependency with the +specified from and to extensions. If a custom dependency has been +previously defined (e.g., in an rcfile that was read earlier), then it +is replaced by the new one. + +The subroutine \fIremove_cus_dep\fR removes the specified custom +dependency. The subroutine \fIshow_cus_dep\fR causes a list of the +currently defined custom dependencies to be sent to the screen +output. + +.SS How custom dependencies are used: A custom dependency rule is invoked whenever \fIlatexmk\fR detects that a run of latex/pdflatex needs to read a file, like a graphics file, whose extension is the to-extension of a custom dependency. Then \fIlatexmk\fR examines whether a file exists with the same name, but with the corresponding from-extension, as specified in the -custom-dependency rule. If it does, then the rule whenever the destination +custom-dependency rule. If it does, then the rule is invoked whenever +the destination file (the one with the to-extension) is out-of-date with respect to the corresponding source file. @@ -2659,15 +2710,23 @@ external program; this can be done by following the templates below, even by those without knowledge of the \fIPerl\fR programming language. Of course, experts could do something much more elaborate. -One other item in each custom-dependency rule, labeled "must" above, +One other item in the specification of +each custom-dependency rule, labeled "must" above, specifies how the rule should be applied when the source file fails to exist. -A simple and typical example of code in an initialization rcfile is +.SS Function to implement custom dependency, traditional method: +The function that implements a custom dependency gets the information +on the files to be processed in two ways. The first is through its +one argument; the argument contains the base name of the source and +destination files. The second way is described later. + +A simple and typical example of code in an initialization rcfile using +the first method is: add_cus_dep( 'fig', 'eps', 0, 'fig2eps' ); sub fig2eps { - return system( "fig2dev -Leps \\"$_[0].fig\\" \\"$_[0].eps\\"" ); + system( "fig2dev -Leps \\"$_[0].fig\\" \\"$_[0].eps\\"" ); } The first line adds a custom dependency that converts a file with @@ -2701,12 +2760,13 @@ replace the above code in an initialization file by add_cus_dep( 'fig', 'pdf, 0, 'fig2pdf' ); sub fig2pdf { - return system( "fig2dev -Lpdf \\"$_[0].fig\\" \\"$_[0].pdf\\"" ); + system( "fig2dev -Lpdf \\"$_[0].fig\\" \\"$_[0].pdf\\"" ); } \fBNote 1:\fR In the command lines given in the system commands in the above examples, double quotes have been inserted around the file names -(implemented by '\\"' in the Perl language). They immunize the running +(implemented by '\\"' \" " COMMENT TO FOOL EDITOR INTO MATCHING DOUBLE QUOTES +in the Perl language). They immunize the running of the program against special characters in filenames. Very often these quotes are not necessary, i.e., they can be omitted. But it is normally safer to keep them in. Even though the rules for quoting @@ -2724,10 +2784,21 @@ separators; but their correct use normally requires quoted filenames. (See a log file from a run of MiKTeX (at least in v. 2.9) for an example of the use of both directory separators.) +\fBNote 3:\fR The subroutines implementing custom dependencies in the +examples given just have a single line invoking an external program. +That's the usual situation. But since the subroutines are in the Perl +language, you can implement much more complicated processing if you +need it. + +.SS Removing custom dependencies, and when you might need to do this: If you have some general custom dependencies defined in the system or user initialization file, you may find that for a particular project they are undesirable. So you might want to delete the unneeded ones. -For example, you remove any "fig" to "eps" rule by the line +A situation where this would be desirable is where there are multiple +custom dependencies with the same from-extension or the same +to-extension. In that case, \fIlatexmk\fR might choose a different one +from the one you want for a specific project. As an example, to +remove any "fig" to "eps" rule you would use: remove_cus_dep( 'fig', 'eps' ); @@ -2739,44 +2810,92 @@ line in an initialization file. -Another example of a custom dependency overcomes a limitation of -\fIlatexmk\fR concerning index files. The only index-file conversion -built-in to \fIlatexmk\fR is from an ".idx" file written on one run of -latex/pdflatex to an ".ind" file to be read in on a subsequent run. -But with the index.sty package you can create extra indexes with -extensions that you configure. \fILatexmk\fR does not know how to -deduce the extensions from the information it has. But you can easily -write a custom dependency. For example if your latex file uses the -command "\\newindex{special}{ndx}{nnd}{Special index}" you will need to -convert files with the extension \fI.ndx\fR to \fI.nnd\fR. The -following lines in an initialization RC file will cause this to -happen: - - add_cus_dep('ndx', 'nnd', 0, 'makendx2nnd'); - sub makendx2nnd { +.SS Function implementing custom dependency, alternative methods: +So far the examples for functions to implement custom dependencies +have used the argument of the function to specify the base name of +converted file. This method has been available since very old +versions of \fIlatexmk\fR, and many examples can be found, e.g., on +the web. + +However in later versions of \fIlatexmk\fR the internal structure of +the implementation of its "rules" for the steps of processing, +including custom dependencies, became much more powerful. The +function implementing a custom dependency is executed within a special +context where a number of extra variables and subroutines are +defined. Publicly documented ones, intended to be long-term stable, +are listed below, under the heading "Variables and subroutines for +processing a rule". + +Examples of their use is given in the following examples, concerning +multiple index files and glossaries. + +The only index-file conversion built-in to \fIlatexmk\fR is from an +".idx" file written on one run of latex/pdflatex to an ".ind" file to +be read in on a subsequent run. But with the index.sty package, for +example, you can create extra indexes with extensions that you +configure. \fILatexmk\fR does not know how to deduce the extensions +from the information it has. But you can easily write a custom +dependency. For example if your latex file uses the command +"\\newindex{special}{ndx}{nnd}{Special index}" you will need to get +\fIlatexmk\fR to convert files with the extension \fI.ndx\fR to +\fI.nnd\fR. The most elementary method is to define a custom +dependency as follows: + + add_cus_dep( 'ndx', 'nnd', 0, 'ndx2nnd' ); + sub ndx2nnd { return system( "makeindex -o \\"$_[0].nnd\\" \\"$_[0].ndx\\"" ); } + push @generated_exts, 'ndx', 'nnd'; + +Notice the added line compared with earlier examples. The extra line +gets the extensions "ndx" and "nnd" added to the list of extensions +for generated files; then the extra index files will be deleted by +clean-up operations + +But if you have yet more indexes with yet different extensions, e.g., +"adx" and "and", then you will need a separate function for each pair +of extensions. This is quite annoying. You can use the +\fIRun_subst\fR function to simplify the definitions to use a single +function: + + add_cus_dep( 'ndx', 'nnd', 0, 'dx2nd' ); + add_cus_dep( 'adx', 'and', 0, 'dx2nd' ); + sub dx2nd { + return Run_subst( "makeindex -o %D %S" ); + } + push @generated_exts, 'ndx', 'nnd', 'adx', 'and'; + +You could also instead use -Those of you with experience with Makefiles, will undoubtedly be + add_cus_dep( 'ndx', 'nnd', 0, 'dx2nd' ); + add_cus_dep( 'adx', 'and', 0, 'dx2nd' ); + sub dx2nd { + return Run_subst( $makeindex ); + } + push @generated_exts, 'ndx', 'nnd', 'adx', 'and'; + +This last example uses the command specification in \fB$makeindex\fR, +and so any customization you have made for the standard index also +applies to your extra indexes. + +Similar techniques can be applied for glossaries. + +Those of you with experience with Makefiles, may get concerned that the \fI.ndx\fR file is written during a run of latex/pdflatex and is always later than the \fI.nnd\fR last read in. Thus the \fI.nnd\fR appears to be perpetually out-of-date. This -situation, of circular dependencies, is endemic to latex, and -\fIlatexmk\fR in its current version works correctly with circular -dependencies. It examines the contents of the files (by use of an md5 -checksum), and only does a remake when the file contents have actually -changed. +situation, of circular dependencies, is endemic to latex, and is one +of the issues that \fIlatexmk\fR is programmed to overcome. It +examines the contents of the files (by use of a checksum), and only +does a remake when the file contents have actually changed. Of course if you choose to write random data to the \fI.nnd\fR (or the \fI.aux\fR file, etc) that changes on each new run, then you will have a problem. For real experts: See the \fI%hash_cal_ignore_pattern\fR if you have to deal with such problems. -Glossaries can be dealt with similarly. - - -.SH OLD METHOD OF DEFINING CUSTOM DEPENDENCIES -In previous versions of \fIlatexmk\fR, the only method of defining +.SS Old Method of Defining Custom Dependencies: +In much older versions of \fIlatexmk\fR, the only method of defining custom dependencies was to directly manipulate the table of custom dependencies. This is contained in the \fB@cus_dep_list\fR array. It is an array of strings, and each string in the array has four items in @@ -2793,10 +2912,10 @@ of \fI.fig\fR files to \fI.eps\fR files: return system( "fig2dev -Lps \\"$_[0].fig\\" \\"$_[0].eps\\"" ); } -This method still works, and is equivalent to the earlier code using -the add_cus_dep subroutine, except that it doesn't delete any previous -custom-dependency for the same conversion. So the new method is -preferable. +This method still works, and is almost equivalent to the code given +earlier that used the \fIadd_cus_dep\fR subroutine. However, the old +method doesn't delete any previous custom-dependency for the same +conversion. So the new method is preferable. .SH ADVANCED CONFIGURATION: Some extra resources and advanced tricks @@ -2810,7 +2929,7 @@ Perl language, since this is what is used in the rc files. See also the section DEALING WITH ERRORS, PROBLEMS, ETC. See also the examples in the directory \fIexample_rcfiles\fR in the \fIlatexmk\fR distributions. Even if none of the examples apply to -your case, they may give ideas +your case, they may give you useful ideas .SS Variables and subroutines for processing a rule @@ -2828,23 +2947,19 @@ users, and their specifications will generally have stability under upgrades. Generally, the variables should be treated as read-only: Changing their values can have bad consequences, since it is liable to mess up the consistency of what \fIlatexmk\fR is doing. - .TP .B $rule This variable has the name of the rule, as known to \fIlatexmk\fR. Note that the exact contents of this variable for a given rule may be dependent on the version of \fIlatexmk\fR - .TP .B $$Psource This gives the name of the primary source file. Note the double dollar signs. - .TP .B $$Pdest This gives the name of the main output file if any. Note the double dollar signs. - .TP .B rdb_ensure_file( $rule, file ) This a subroutine that ensures that the given file is among the source @@ -2857,29 +2972,38 @@ appropriate to specify it by \fB$rule\fR. For examples of its use, see some of the files in the directory \fIexample_rcfiles\fR of \fIlatexmk\fR's distribution. Currently the -cases that use this subroutine are \fIexceltex_latexmkrc\fR and -\fItexinfo-latexmkrc\fR. These illustrate typical cases where -\fIlatexmk\fR's normal processing fails to detect certain extra source -files. - +cases that use this subroutine are \fIbib2gls-latexmkrc\fR, +\fIexceltex_latexmkrc\fR and \fItexinfo-latexmkrc\fR. These +illustrate typical cases where \fIlatexmk\fR's normal processing fails +to detect certain extra source files. .TP .B rdb_remove_files( $rule, file, ... ) This subroutine removes one or more files from the dependency list for the given rule. - .TP .B rdb_list_source( $rule ) This subroutine returns the list of source files (i.e., the dependency list) for the given rule. - .TP .B rdb_set_source( $rule, file, ... ) +.TP .B rdb_set_source( $rule, @files ) This subroutine sets the dependency list for the given rule to be the specified files. Files that are already in the list have unchanged information. Files that were not in the list are added to it. Files in the previous dependency list that are not in the newly specified list of files are removed from the dependency list. +.TP +.B Run_subst( command_spec ) +This subroutine runs the command specified by \fIcommand_spec\fR. The +specification is a string in the format listed in the section "Format +of Command Specifications". An important action of the +\fIRun_subst\fR is to make substitutions of placeholders, e.g., %S and +%D for source and destination files; these get substituted before the +command is run. In addition, the command after substitution is +printed to the screen unless \fIlatexmk\fR is running in silent mode. + +.PP .SS Advanced configuration: Using \fIlatexmk\fB with \fImake\fR @@ -3015,7 +3139,7 @@ Thus we now have a method by which all the subsidiary processing is delegated to \fImake\fR. .SH SEE ALSO -latex(1), bibtex(1). +latex(1), bibtex(1), lualatex(1), pdflatex(1), xelatex(1). .SH BUGS Sometimes a viewer (gv) tries to read an updated .ps or .pdf file after its creation is started but before the file is complete. Work @@ -3042,10 +3166,10 @@ David Coppit (username david at node coppit.org) who made many useful suggestions that contributed to version 3, and Herbert Schulz. (Please note that the e-mail addresses are not written in their standard form to avoid being -harvested by worms and viruses.) +harvested too easily.) .SH AUTHOR Current version, by John Collins (username jcc8 at node psu.edu). -(Version 4.52c). +(Version 4.54). Released version can be obtained from CTAN: <http://www.ctan.org/pkg/latexmk/>, and from the diff --git a/Master/texmf-dist/doc/man/man1/latexmk.man1.pdf b/Master/texmf-dist/doc/man/man1/latexmk.man1.pdf Binary files differindex c90a405c97d..d3ce7128f26 100644 --- a/Master/texmf-dist/doc/man/man1/latexmk.man1.pdf +++ b/Master/texmf-dist/doc/man/man1/latexmk.man1.pdf diff --git a/Master/texmf-dist/doc/support/latexmk/CHANGES b/Master/texmf-dist/doc/support/latexmk/CHANGES index 54801480ce4..31e7d53b52d 100644 --- a/Master/texmf-dist/doc/support/latexmk/CHANGES +++ b/Master/texmf-dist/doc/support/latexmk/CHANGES @@ -534,5 +534,41 @@ From v. 4.52 to 4.52b when recorder mode is on. From v. 4.52b to 4.52c + Make -jobname work with -pdfxe and -pdflua. + +From v. 4.52c to 4.54 + In deps_list, correct bug in identifying generated files. + Otherwise, generated files could have been identified as true + source files. + Remove insertion of name of deps file in list of targets in deps file. + Don't send to screen deps info in deps mode (unless diagnostics on). + Correct ordering of list of options given by -help. + Fix incorrect deletion of non-generated aux files. + Optimize away current directory string in $out_dir and $aux_dir. + Make compatible with future versions of Perl where File::Glob's glob + function won't exist. + Add extra value 1.5 for $bibtex_use, with corresponding option + -bibtex-cond1; this treats bbl files as conditionally precious in + cleanup operations, depending on the existence or non-exisitence + of bib files. + When running bibtex, ensure that the change in search paths is made to work + around deficiencies in bibtex is local and does not affect other + programs. + Collection of timing information now works in silent mode. + Set better default previewers for MSys. + Restore default of $analyze_input_log_always to 1. + This restores the default detection of certain constructs for dependencies + for input files in the .log file. See the comments on this variable in + latexmk.pl for details. This works around a problem caused by a change in + the behavior of lualatex in TeXLive 2017; it no longer lists all input + files in the .fls file. Note that latexmk.pl always examines the .log + file for relevant information. The variable $analyze_input_log_always + only concerns whether it looks for <...> and (...) constructs. + Add item to @file_not_found for the particular format of generic package + warning about "No file", that is produced by glossaries-extra, and + probably other packages. + Documentation improvements, especially on methods of implementing + custom dependencies for multiple kinds of index. Document $kpsewhich_show variable. - Make -jobname work with -pdfxe and -pdflua + Add a sample latexmkrc file for use with bib2gls and glossaries-extra. + diff --git a/Master/texmf-dist/doc/support/latexmk/INSTALL b/Master/texmf-dist/doc/support/latexmk/INSTALL index 4feea9dd7e3..8b0e8a61fc4 100644 --- a/Master/texmf-dist/doc/support/latexmk/INSTALL +++ b/Master/texmf-dist/doc/support/latexmk/INSTALL @@ -1,6 +1,6 @@ INSTALLING latexmk ================== - (Version 4.52c, 19 January 2017) + (Version 4.54, 20 November 2017) John Collins Physics Department diff --git a/Master/texmf-dist/doc/support/latexmk/README b/Master/texmf-dist/doc/support/latexmk/README index 96ff552e517..e65b05fda0a 100644 --- a/Master/texmf-dist/doc/support/latexmk/README +++ b/Master/texmf-dist/doc/support/latexmk/README @@ -1,4 +1,4 @@ -Latexmk, version 4.52c, 19 January 2017 +Latexmk, version 4.54, 20 November 2017 --------------------------------------- Latexmk completely automates the process of generating a LaTeX @@ -91,7 +91,7 @@ NOTES:- John Collins ---------------------------- "latexmk -h" ---------------------------- -Latexmk 4.52c: Automatic LaTeX document generation routine +Latexmk 4.54: Automatic LaTeX document generation routine Usage: latexmk [latexmk_options] [filename ...] @@ -101,7 +101,9 @@ Usage: latexmk [latexmk_options] [filename ...] - Currently this only works with MiKTeX -bibtex - use bibtex when needed (default) -bibtex- - never use bibtex - -bibtex-cond - use bibtex when needed, but only if the bib files exist + -bibtex-cond - use bibtex when needed, but only if the bib file exists + -bibtex-cond1 - use bibtex when needed, but only if the bib file exists; + on cleanup delete bbl file only if bib file exists -bm <message> - Print message across the page when converting to postscript -bi <intensity> - Set contrast or intensity of banner -bs <scale> - Set scale for banner @@ -147,6 +149,8 @@ Usage: latexmk [latexmk_options] [filename ...] give list of warnings after run of (pdf)latex -logfilewarninglist- or -logfilewarnings- do not give list of warnings after run of (pdf)latex + -lualatex - use lualatex for processing files to pdf + and turn dvi/ps modes off -M - Show list of dependent files after processing -MF file - Specifies name of file to receives list dependent files -MP - List of dependent files includes phony target for each source file. @@ -203,8 +207,6 @@ Usage: latexmk [latexmk_options] [filename ...] -view=none - no viewer is used -view=ps - viewer is for ps -view=pdf - viewer is for pdf - -lualatex - use lualatex for processing files to pdf - and turn dvi/ps modes off -xelatex - use xelatex for processing files to pdf and turn dvi/ps modes off diff --git a/Master/texmf-dist/doc/support/latexmk/example_rcfiles/bib2gls_latexmkrc b/Master/texmf-dist/doc/support/latexmk/example_rcfiles/bib2gls_latexmkrc new file mode 100644 index 00000000000..53f13ff30a7 --- /dev/null +++ b/Master/texmf-dist/doc/support/latexmk/example_rcfiles/bib2gls_latexmkrc @@ -0,0 +1,35 @@ +# Implementing glossary with bib2gls and glossaries-extra, with the +# log file (.glg) analyzed to get dependence on a .bib file. + +# !!! ONLY WORKS WITH VERSION 4.54 or higher of latexmk + +push @generated_exts, 'glstex', 'glg'; + +add_cus_dep('aux', 'glstex', 0, 'run_bib2gls'); + +sub run_bib2gls { + if ( $silent ) { + my $ret = system "bib2gls --silent --group '$_[0]'"; + } else { + my $ret = system "bib2gls --group '$_[0]'"; + }; + + my ($base, $path) = fileparse( $_[0] ); + if ($path && -e "$base.glstex") { + rename "$base.glstex", "$path$base.glstex"; + } + + # Analyze log file. + local *LOG; + $LOG = "$_[0].glg"; + if (!$ret && -e $LOG) { + open LOG, "<$LOG"; + while (<LOG>) { + if (/^Reading (.*\.bib)\s$/) { + rdb_ensure_file( $rule, $1 ); + } + } + close LOG; + } + return $ret; +} diff --git a/Master/texmf-dist/doc/support/latexmk/example_rcfiles/glossary_latexmkrc b/Master/texmf-dist/doc/support/latexmk/example_rcfiles/glossary_latexmkrc index 937df6f9e71..203a0a3fe72 100644 --- a/Master/texmf-dist/doc/support/latexmk/example_rcfiles/glossary_latexmkrc +++ b/Master/texmf-dist/doc/support/latexmk/example_rcfiles/glossary_latexmkrc @@ -31,6 +31,32 @@ sub makeacr2acn { add_cus_dep( 'glo', 'gls', 0, 'makeglossaries' ); sub makeglossaries { - system( "makeglossaries \"$_[0]\"" ); - } - + my ($base_name, $path) = fileparse( $_[0] ); + pushd $path; + my $return = system "makeglossaries $base_name"; + popd; + return $return; + } + +# This code works around a problem with makeglossaries when the +# -output-directory option of latexmk is used. When makeglossaries is +# called with a filename that has a directory in it, e.g., +# +# makeglossaries output/document +# +# the makeindex or xindy commmands look for a document.ist or +# document.xdy file that is created by the glossaries package. The +# file is correctly created in the output/ directory, but the +# makeindex or xindy commands are called in way that they look for +# that file in the document directory, not in the output directory. +# So the above definition of a subroutine makeglossaries works around +# that. +# +# Note that the 3rd definition of a custom dependency, the one that +# invokes the makeglossaries script, has the advantage that it can +# change automatically to use the xindy program instead of makeindex, +# according to the setting by which the glossaries package is invoked +# in the document. The first two solutions I gave for the custom +# dependency have the choice of makeindex hard-coded (which can be +# changed, of course). Automatic switching would need a more +# complicated solution. diff --git a/Master/texmf-dist/doc/support/latexmk/extra-scripts/dvipdfm_call.bat b/Master/texmf-dist/doc/support/latexmk/extra-scripts/dvipdfm_call.bat index a0817015fe6..104bbabe858 100755 --- a/Master/texmf-dist/doc/support/latexmk/extra-scripts/dvipdfm_call.bat +++ b/Master/texmf-dist/doc/support/latexmk/extra-scripts/dvipdfm_call.bat @@ -1,19 +1,19 @@ -@echo off -REM Run dvipdfm from dvipdf-style command-line -REM Assume no options specified -REM If this script is called from latexmk, -REM we have %1=source.dvi, %2=dest.pdf -REM But for safety, let's handle correctly a one argument call, -REM i.e., %1=source, with no %2 - -if "%2" == "" goto onearg - -:twoarg -dvipdfm -o %2 %1 -goto done - -:onearg -dvipdfm %1 - - +@echo off
+REM Run dvipdfm from dvipdf-style command-line
+REM Assume no options specified
+REM If this script is called from latexmk,
+REM we have %1=source.dvi, %2=dest.pdf
+REM But for safety, let's handle correctly a one argument call,
+REM i.e., %1=source, with no %2
+
+if "%2" == "" goto onearg
+
+:twoarg
+dvipdfm -o %2 %1
+goto done
+
+:onearg
+dvipdfm %1
+
+
:done
\ No newline at end of file diff --git a/Master/texmf-dist/doc/support/latexmk/extra-scripts/dvipdfmx_call.bat b/Master/texmf-dist/doc/support/latexmk/extra-scripts/dvipdfmx_call.bat index 0068de2196d..01a140a65fe 100755 --- a/Master/texmf-dist/doc/support/latexmk/extra-scripts/dvipdfmx_call.bat +++ b/Master/texmf-dist/doc/support/latexmk/extra-scripts/dvipdfmx_call.bat @@ -1,19 +1,19 @@ -@echo off -REM Run dvipdfmx from dvipdf-style command-line -REM Assume no options specified -REM If this script is called from latexmk, -REM we have %1=source.dvi, %2=dest.pdf -REM But for safety, let's handle correctly a one argument call, -REM i.e., %1=source, with no %2 - -if "%2" == "" goto onearg - -:twoarg -dvipdfmx -o %2 %1 -goto done - -:onearg -dvipdfmx %1 - - +@echo off
+REM Run dvipdfmx from dvipdf-style command-line
+REM Assume no options specified
+REM If this script is called from latexmk,
+REM we have %1=source.dvi, %2=dest.pdf
+REM But for safety, let's handle correctly a one argument call,
+REM i.e., %1=source, with no %2
+
+if "%2" == "" goto onearg
+
+:twoarg
+dvipdfmx -o %2 %1
+goto done
+
+:onearg
+dvipdfmx %1
+
+
:done
\ No newline at end of file diff --git a/Master/texmf-dist/doc/support/latexmk/latexmk.pdf b/Master/texmf-dist/doc/support/latexmk/latexmk.pdf Binary files differindex a696b51e863..8d07811f7a2 100644 --- a/Master/texmf-dist/doc/support/latexmk/latexmk.pdf +++ b/Master/texmf-dist/doc/support/latexmk/latexmk.pdf diff --git a/Master/texmf-dist/doc/support/latexmk/latexmk.txt b/Master/texmf-dist/doc/support/latexmk/latexmk.txt index e5aa3d13745..8d389e732c0 100644 --- a/Master/texmf-dist/doc/support/latexmk/latexmk.txt +++ b/Master/texmf-dist/doc/support/latexmk/latexmk.txt @@ -61,7 +61,7 @@ DESCRIPTION - 19 January 2017 1 + 20 November 2017 1 @@ -127,7 +127,7 @@ LATEXMK OPTIONS AND ARGUMENTS ON COMMAND LINE - 19 January 2017 2 + 20 November 2017 2 @@ -193,7 +193,7 @@ LATEXMK(1) General Commands Manual LATEXMK(1) - 19 January 2017 3 + 20 November 2017 3 @@ -207,39 +207,80 @@ LATEXMK(1) General Commands Manual LATEXMK(1) or biber as needed to regenerate the bbl files. This property can also be configured by setting the $bibtex_use - variable to 2 in a configuration file + variable to 2 in a configuration file. -bibtex- - Never run bibtex or biber. + Never run bibtex or biber. Also, always treat .bbl files as + precious, i.e., do not delete them in a cleanup operation. - A common use for this option is when a document comes from an - external source, complete with its bbl file(s), and the user - does not have the corresponding bib files available. In this - situation use of the -bibtex- option will prevent latexmk from + A common use for this option is when a document comes from an + external source, complete with its bbl file(s), and the user + does not have the corresponding bib files available. In this + situation use of the -bibtex- option will prevent latexmk from trying to run bibtex or biber, which would result in overwriting of the bbl files. + This property can also be configured by setting the $bibtex_use + variable to 0 in a configuration file. + -bibtex-cond When the source file uses bbl file(s) for the bibliography, run bibtex or biber as needed to regenerate the bbl files, but only if the relevant bib file(s) exist. Thus when the bib files are not available, bibtex or biber is not run, thereby avoiding - overwriting of the bbl file(s). This is the default setting. - - (Note that it is possible for latexmk to decide that the bib - file does not exist, even though the bib file does exist and - bibtex or biber finds it. The problem is that the bib file may - not be in the current directory but in some search path; the + overwriting of the bbl file(s). Also, always treat .bbl files + as precious, i.e., do not delete them in a cleanup operation. + + This is the default setting. It can also be configured by set- + ting the $bibtex_use variable to 1 in a configuration file. + + The reason for using this setting is that sometimes a .bbl file + is available containing the bibliography for a document, but the + .bib file is not available. An example would be for a scien- + tific journal where authors submit .tex and .bbl files, but not + the original .bib file. In that case, running bibtex or biber + would not work, and the .bbl file should be treated as a user + source file, and not as a file that can be regenerated on + demand. + + (Note that it is possible for latexmk to decide that the bib + file does not exist, even though the bib file does exist and + bibtex or biber finds it. The problem is that the bib file may + not be in the current directory but in some search path; the places latexmk and bibtex or biber cause to be searched need not - be identical. On modern installations of TeX and related pro- - grams this problem should not arise, since latexmk uses the + be identical. On modern installations of TeX and related pro- + grams this problem should not arise, since latexmk uses the kpsewhich program to do the search, and kpsewhich should use the - same search path as bibtex and biber. If this problem arises, + same search path as bibtex and biber. If this problem arises, use the -bibtex option when invoking latexmk.) + + + 20 November 2017 4 + + + + + +LATEXMK(1) General Commands Manual LATEXMK(1) + + + -bibtex-cond1 + The same as -bibtex-cond1 except that .bbl files are only + treated as precious if one or more bibfiles fails to exist. + + Thus if all the bib files exist, bibtex or biber is run to gen- + erate .bbl files as needed, and then it is appropriate to delete + the bbl files in a cleanup operation since they can be re-gener- + ated. + + This property can also be configured by setting the $bibtex_use + variable to 1.5 in a configuration file. + + -bm <message> A banner message to print diagonally across each page when con- verting the dvi file to postscript. The message must be a sin- @@ -256,18 +297,6 @@ LATEXMK(1) General Commands Manual LATEXMK(1) is OK unless your toner cartridge is getting low. - - - - 19 January 2017 4 - - - - - -LATEXMK(1) General Commands Manual LATEXMK(1) - - -bs <scale> A decimal number that specifies how large the banner message will be printed. Experimentation is necessary to get the right @@ -293,141 +322,163 @@ LATEXMK(1) General Commands Manual LATEXMK(1) This cleanup is instead of a regular make. See the -gg option if you want to do a cleanup then a make. - If $bibtex_use is set to 0 or 1, bbl files are counted as non- - regeneratable. - If $cleanup_includes_cusdep_generated is nonzero, regeneratable - files are considered as including those generated by custom - dependencies and are also deleted. Otherwise these files are + + + 20 November 2017 5 + + + + + +LATEXMK(1) General Commands Manual LATEXMK(1) + + + Treatment of .bbl files: If $bibtex_use is set to 0 or 1, bbl + files are always treated as non-regeneratable. If $bibtex_use + is set to 1.5, bbl files are counted as non-regeneratable condi- + tionally: If the bib file exists, then bbl files are regenerat- + able, and are deleted in a clean up. But if $bibtex_use is 1.5 + and a bib file doesn't exist, then the bbl files are treated as + non-regeneratable and hence are not deleted. + + In contrast, if $bibtex_use is set to 2, bbl files are always + treated as regeneratable, and are deleted in a cleanup. + + Treatment of files generated by custom dependencies:If + $cleanup_includes_cusdep_generated is nonzero, regeneratable + files are considered as including those generated by custom + dependencies and are also deleted. Otherwise these files are not deleted. -C Clean up (remove) all regeneratable files generated by latex and - bibtex or biber. This is the same as the -c option with the - addition of dvi, postscript and pdf files, and those specified + bibtex or biber. This is the same as the -c option with the + addition of dvi, postscript and pdf files, and those specified in the $clean_full_ext configuration variable. - This cleanup is instead of a regular make. See the -gg option + This cleanup is instead of a regular make. See the -gg option if you want to do a cleanup than a make. - If $bibtex_use is set to 0 or 1, bbl files are counted as non- - regeneratable. + See the -c option for the specification of whether or not .bbl + files are treated as non-regeneratable or regeneratable. - If $cleanup_includes_cusdep_generated is nonzero, regeneratable - files are considered as including those generated by custom - dependencies and are also deleted. Otherwise these files are + If $cleanup_includes_cusdep_generated is nonzero, regeneratable + files are considered as including those generated by custom + dependencies and are also deleted. Otherwise these files are not deleted. - -CA (Obsolete). Now equivalent to the -C option. See that option + -CA (Obsolete). Now equivalent to the -C option. See that option for details. + -cd Change to the directory containing the main source file before + processing it. Then all the generated files (aux, log, dvi, + pdf, etc) will be relative to the source file. + This option is particularly useful when latexmk is invoked from + a GUI configured to invoke latexmk with a full pathname for the + source file. - 19 January 2017 5 + -cd- Do NOT change to the directory containing the main source file + before processing it. Then all the generated files (aux, log, + dvi, pdf, etc) will be relative to the current directory rather + than the source file. + This is the default behavior and corresponds to the behavior of -LATEXMK(1) General Commands Manual LATEXMK(1) + 20 November 2017 6 - -cd Change to the directory containing the main source file before - processing it. Then all the generated files (aux, log, dvi, - pdf, etc) will be relative to the source file. - This option is particularly useful when latexmk is invoked from - a GUI configured to invoke latexmk with a full pathname for the - source file. - -cd- Do NOT change to the directory containing the main source file - before processing it. Then all the generated files (aux, log, - dvi, pdf, etc) will be relative to the current directory rather - than the source file. +LATEXMK(1) General Commands Manual LATEXMK(1) - This is the default behavior and corresponds to the behavior of - the latex and pdflatex programs. However, it is not desirable - behavior when latexmk is invoked by a GUI configured to invoke - latexmk with a full pathname for the source file. See the -cd + + the latex and pdflatex programs. However, it is not desirable + behavior when latexmk is invoked by a GUI configured to invoke + latexmk with a full pathname for the source file. See the -cd option. - -CF Remove the file containing the database of source file informa- + -CF Remove the file containing the database of source file informa- tion, before doing the other actions requested. - -d Set draft mode. This prints the banner message "DRAFT" across - your page when converting the dvi file to postscript. Size and + -d Set draft mode. This prints the banner message "DRAFT" across + your page when converting the dvi file to postscript. Size and intensity can be modified with the -bs and -bi options. The -bm - option will override this option as this is really just a short + option will override this option as this is really just a short way of specifying: latexmk -bm DRAFT - Note that if the -d option is specified, the -ps option is + Note that if the -d option is specified, the -ps option is assumed. -deps Show a list of dependent files after processing. This is in the - form of a dependency list of the form used by the make program, + form of a dependency list of the form used by the make program, and it is therefore suitable for use in a Makefile. It gives an overall view of the files without listing intermediate files, as well as latexmk can determine them. - By default the list of dependent files is sent to stdout (i.e., - normally to the screen unless you've redirected latexmk's out- + By default the list of dependent files is sent to stdout (i.e., + normally to the screen unless you've redirected latexmk's out- put). But you can set the filename where the list is sent by the -deps-out= option. - See the section "USING latexmk WITH make" for an example of how + See the section "USING latexmk WITH make" for an example of how to use a dependency list with make. - Users familiar with GNU automake and gcc will find that the - -deps option is very similar in its purpose and results to the - -M option to gcc. (In fact, latexmk also has options -M, -MF, + Users familiar with GNU automake and gcc will find that the + -deps option is very similar in its purpose and results to the + -M option to gcc. (In fact, latexmk also has options -M, -MF, + and -MP options that behave like those of gcc.) + -dependents + Equivalent to -deps. - 19 January 2017 6 + -deps- Do not show a list of dependent files after processing. (This + is the default.) + -dependents- + Equivalent to -deps-. -LATEXMK(1) General Commands Manual LATEXMK(1) - and -MP options that behave like those of gcc.) + 20 November 2017 7 - -dependents - Equivalent to -deps. - -deps- Do not show a list of dependent files after processing. (This - is the default.) - -dependents- - Equivalent to -deps-. +LATEXMK(1) General Commands Manual LATEXMK(1) -deps-out=FILENAME - Set the filename to which the list of dependent files is writ- - ten. If the FILENAME argument is omitted or set to "-", then + Set the filename to which the list of dependent files is writ- + ten. If the FILENAME argument is omitted or set to "-", then the output is sent to stdout. - Use of this option also turns on the output of the list of + Use of this option also turns on the output of the list of dependent files after processing. - -dF Dvi file filtering. The argument to this option is a filter - which will generate a filtered dvi file with the extension - ".dviF". All extra processing (e.g. conversion to postscript, - preview, printing) will then be performed on this filtered dvi + -dF Dvi file filtering. The argument to this option is a filter + which will generate a filtered dvi file with the extension + ".dviF". All extra processing (e.g. conversion to postscript, + preview, printing) will then be performed on this filtered dvi file. Example usage: To use dviselect to select only the even pages of @@ -437,7 +488,7 @@ LATEXMK(1) General Commands Manual LATEXMK(1) -diagnostics - Print detailed diagnostics during a run. This may help for + Print detailed diagnostics during a run. This may help for debugging problems or to understand latexmk's behavior in diffi- cult situations. @@ -445,56 +496,56 @@ LATEXMK(1) General Commands Manual LATEXMK(1) -dvi Generate dvi version of document. - -dvi- Turn off generation of dvi version of document. (This may get - overridden, if some other file is made (e.g., a .ps file) that - is generated from the dvi file, or if no generated file at all + -dvi- Turn off generation of dvi version of document. (This may get + overridden, if some other file is made (e.g., a .ps file) that + is generated from the dvi file, or if no generated file at all is requested.) -e <code> - Execute the specified initialization code before processing. - The code is Perl code of the same form as is used in latexmk's + Execute the specified initialization code before processing. + The code is Perl code of the same form as is used in latexmk's + initialization files. For more details, see the information on + the -r option, and the section about "Configuration/initializa- + tion (RC) files". The code is typically a sequence of assign- + ment statements separated by semicolons. + The code is executed when the -e option is encountered during + latexmk's parsing of its command line. See the -r option for a + way of executing initialization code from a file. An error + results in latexmk stopping. Multiple instances of the -r and + -e options can be used, and they are executed in the order they + appear on the command line. + Some care is needed to deal with proper quoting of special char- + acters in the code on the command line. For example, suppose + you want to set the latex command to use its -shell-escape - 19 January 2017 7 + 20 November 2017 8 -LATEXMK(1) General Commands Manual LATEXMK(1) - initialization files. For more details, see the information on - the -r option, and the section about "Configuration/initializa- - tion (RC) files". The code is typically a sequence of assign- - ment statements separated by semicolons. +LATEXMK(1) General Commands Manual LATEXMK(1) - The code is executed when the -e option is encountered during - latexmk's parsing of its command line. See the -r option for a - way of executing initialization code from a file. An error - results in latexmk stopping. Multiple instances of the -r and - -e options can be used, and they are executed in the order they - appear on the command line. - Some care is needed to deal with proper quoting of special char- - acters in the code on the command line. For example, suppose - you want to set the latex command to use its -shell-escape option, then under UNIX/Linux you could use the line latexmk -e '$latex=q/latex %O -shell-escape %S/' file.tex - Note that the single quotes block normal UNIX/Linux command - shells from treating the characters inside the quotes as spe- - cial. (In this example, the q/.../ construct is a Perl idiom - equivalent to using single quotes. This avoids the complica- - tions of getting a quote character inside an already quoted - string in a way that is independent of both the shell and the + Note that the single quotes block normal UNIX/Linux command + shells from treating the characters inside the quotes as spe- + cial. (In this example, the q/.../ construct is a Perl idiom + equivalent to using single quotes. This avoids the complica- + tions of getting a quote character inside an already quoted + string in a way that is independent of both the shell and the operating-system.) - The above command line will NOT work under MS-Windows with - cmd.exe or command.com or 4nt.exe. For MS-Windows with these + The above command line will NOT work under MS-Windows with + cmd.exe or command.com or 4nt.exe. For MS-Windows with these command shells you could use latexmk -e "$latex=q/latex %O -shell-escape %S/" file.tex @@ -503,50 +554,48 @@ LATEXMK(1) General Commands Manual LATEXMK(1) latexmk -e "$latex='latex %O -shell-escape %S'" file.tex - The last two examples will NOT work with UNIX/Linux command + The last two examples will NOT work with UNIX/Linux command shells. - (Note: the above examples show are to show how to use the -e to - specify initialization code to be executed. But the particular + (Note: the above examples show are to show how to use the -e to + specify initialization code to be executed. But the particular effect can be achieved also by the use of the -latex option with less problems in dealing with quoting.) - -f Force latexmk to continue document processing despite errors. + -f Force latexmk to continue document processing despite errors. Normally, when latexmk detects that LaTeX or another program has found an error which will not be resolved by further processing, no further processing is carried out. - Note: "Further processing" means the running of other programs - or the rerunning of latex (etc) that would be done if no errors - had occurred. If instead, or additionally, you want the latex - - + Note: "Further processing" means the running of other programs + or the rerunning of latex (etc) that would be done if no errors + had occurred. If instead, or additionally, you want the latex + (etc) program not to pause for user input after an error, you + should arrange this by an option that is passed to the program, + e.g., by latexmk's option -interaction=nonstopmode. - 19 January 2017 8 + -f- Turn off the forced processing-past-errors such as is set by the + -f option. This could be used to override a setting in a con- + figuration file. + -g Force latexmk to process document fully, even under situations + where latexmk would normally decide that no changes in the + source files have occurred since the previous run. This option + is useful, for example, if you change some options and wish to + reprocess the files. -LATEXMK(1) General Commands Manual LATEXMK(1) + 20 November 2017 9 - (etc) program not to pause for user input after an error, you - should arrange this by an option that is passed to the program, - e.g., by latexmk's option -interaction=nonstopmode. - -f- Turn off the forced processing-past-errors such as is set by the - -f option. This could be used to override a setting in a con- - figuration file. - -g Force latexmk to process document fully, even under situations - where latexmk would normally decide that no changes in the - source files have occurred since the previous run. This option - is useful, for example, if you change some options and wish to - reprocess the files. +LATEXMK(1) General Commands Manual LATEXMK(1) -g- Turn off -g. @@ -561,17 +610,17 @@ LATEXMK(1) General Commands Manual LATEXMK(1) -jobname=STRING - Set the basename of output files(s) to STRING, instead of the + Set the basename of output files(s) to STRING, instead of the default, which is the basename of the specified TeX file. - This is like the same option for current implementations of the - latex, pdflatex, etc, and the passing of this option to these + This is like the same option for current implementations of the + latex, pdflatex, etc, and the passing of this option to these programs is part of latexmk's implementation of -jobname. -l Run in landscape mode, using the landscape mode for the preview- - ers and the dvi to postscript converters. This option is not - normally needed nowadays, since current previewers normally + ers and the dvi to postscript converters. This option is not + normally needed nowadays, since current previewers normally determine this information automatically. @@ -580,105 +629,105 @@ LATEXMK(1) General Commands Manual LATEXMK(1) -latex="COMMAND" This sets the string specifying the command to run latex, and is - typically used to add desired options. Since the string nor- + typically used to add desired options. Since the string nor- mally contains spaces, it should be quoted, e.g., latexmk -latex="latex --shell-escape %O %S" foo.tex - The specification of the contents of the string are the same as + The specification of the contents of the string are the same as + for the $latex configuration variable. Depending on your oper- + ating system and the command-line shell you are using, you may + need to change the single quotes to double quotes (or something + else). + To set the command for running pdflatex (rather than the command + for latex) see the -pdflatex option. - 19 January 2017 9 + -logfilewarninglist + -logfilewarnings After a run of (pdf)latex, give a list of warn- + ings about undefined citations and references (unless silent + mode is on). + See also the $silence_logfile_warnings configuration variable. -LATEXMK(1) General Commands Manual LATEXMK(1) + 20 November 2017 10 - for the $latex configuration variable. Depending on your oper- - ating system and the command-line shell you are using, you may - need to change the single quotes to double quotes (or something - else). - To set the command for running pdflatex (rather than the command - for latex) see the -pdflatex option. - -logfilewarninglist - -logfilewarnings After a run of (pdf)latex, give a list of warn- - ings about undefined citations and references (unless silent - mode is on). - See also the $silence_logfile_warnings configuration variable. +LATEXMK(1) General Commands Manual LATEXMK(1) -logfilewarninglist- - -logfilewarnings- After a run of (pdf)latex, do not give a list + -logfilewarnings- After a run of (pdf)latex, do not give a list of warnings about undefined citations and references. (Default) See also the $silence_logfile_warnings configuration variable. -lualatex - Use lualatex. That is, use lualatex to process the source - file(s) to pdf. The generation of dvi and postscript files is + Use lualatex. That is, use lualatex to process the source + file(s) to pdf. The generation of dvi and postscript files is turned off. This option is equivalent to using the following set of options -pdflua -dvi- -ps- - (Note: Note that the method of implementation of this option, - but not its intended effect, differ from some earlier versions + (Note: Note that the method of implementation of this option, + but not its intended effect, differ from some earlier versions of latexmk.) - -M Show list of dependent files after processing. This is equiva- + -M Show list of dependent files after processing. This is equiva- lent to the -deps option. -MF file - If a list of dependents is made, the -MF specifies the file to + If a list of dependents is made, the -MF specifies the file to write it to. -MP If a list of dependents is made, include a phony target for each - source file. If you use the dependents list in a Makefile, the - dummy rules work around errors the program make gives if you + source file. If you use the dependents list in a Makefile, the + dummy rules work around errors the program make gives if you remove header files without updating the Makefile to match. + -new-viewer + When in continuous-preview mode, always start a new viewer to + view the generated file. By default, latexmk will, in continu- + ous-preview mode, test for a previously running previewer for + the same file and not start a new one if a previous previewer is + running. However, its test sometimes fails (notably if there is + an already-running previewer that is viewing a file of the same + name as the current file, but in a different directory). This + option turns off the default behavior. + -new-viewer- + The inverse of the -new-viewer option. It puts latexmk in its + normal behavior that in preview-continuous mode it checks for an + already-running previewer. - 19 January 2017 10 + 20 November 2017 11 -LATEXMK(1) General Commands Manual LATEXMK(1) - -new-viewer - When in continuous-preview mode, always start a new viewer to - view the generated file. By default, latexmk will, in continu- - ous-preview mode, test for a previously running previewer for - the same file and not start a new one if a previous previewer is - running. However, its test sometimes fails (notably if there is - an already-running previewer that is viewing a file of the same - name as the current file, but in a different directory). This - option turns off the default behavior. - -new-viewer- - The inverse of the -new-viewer option. It puts latexmk in its - normal behavior that in preview-continuous mode it checks for an - already-running previewer. +LATEXMK(1) General Commands Manual LATEXMK(1) -nobibtex @@ -687,71 +736,71 @@ LATEXMK(1) General Commands Manual LATEXMK(1) -norc Turn off the automatic reading of initialization (rc) files. - N.B. Normally the initialization files are read and obeyed, and - then command line options are obeyed in the order they are - encountered. But -norc is an exception to this rule: it is + N.B. Normally the initialization files are read and obeyed, and + then command line options are obeyed in the order they are + encountered. But -norc is an exception to this rule: it is acted on first, no matter where it occurs on the command line. -outdir=FOO or -output-directory=FOO - Sets the directory for the output files of (pdf)latex. This - achieves its effect by the -output-directory option of + Sets the directory for the output files of (pdf)latex. This + achieves its effect by the -output-directory option of (pdf)latex, which currently (Dec. 2011 and later) is implemented - on the common versions of (pdf)latex, i.e., MiKTeX and TeXLive. + on the common versions of (pdf)latex, i.e., MiKTeX and TeXLive. It may not be present in other versions. - See also the -auxdir/-aux-directory options, and the $aux_dir, - $out_dir, and $search_path_separator configuration variables of - latexmk. In particular, see the documentation of $out_dir for + See also the -auxdir/-aux-directory options, and the $aux_dir, + $out_dir, and $search_path_separator configuration variables of + latexmk. In particular, see the documentation of $out_dir for some complications on what directory names are suitable. - If you also use the -cd option, and the specified output direc- - tory is a relative path, then the path is interpreted relative + If you also use the -cd option, and the specified output direc- + tory is a relative path, then the path is interpreted relative to the document directory. - -p Print out the document. By default the file to be printed is - the first in the list postscript, pdf, dvi that is being made. + -p Print out the document. By default the file to be printed is + the first in the list postscript, pdf, dvi that is being made. But you can use the -print=... option to change the type of file to be printed, and you can configure this in a start up file (by setting the $print_type variable). - However, printing is enabled by default only under UNIX/Linux + However, printing is enabled by default only under UNIX/Linux + systems, where the default is to use the lpr command and only on + postscript files. In general, the correct behavior for printing + very much depends on your system's software. In particular, + under MS-Windows you must have suitable program(s) available, + and you must have configured the print commands used by latexmk. + This can be non-trivial. See the documentation on the $lpr, + $lpr_dvi, and $lpr_pdf configuration variables to see how to set + the commands for printing. + This option is incompatible with the -pv and -pvc options, so it + turns them off. - 19 January 2017 11 + -pdf Generate pdf version of document using pdflatex. (If you wish + to use lualatex or xelatex, you can use whichever of the options + -pdflua, -pdfxe, -lualatex or -xelatex applies.) To configure + latexmk to have such behavior by default, see the section on + 20 November 2017 12 -LATEXMK(1) General Commands Manual LATEXMK(1) - systems, where the default is to use the lpr command and only on - postscript files. In general, the correct behavior for printing - very much depends on your system's software. In particular, - under MS-Windows you must have suitable program(s) available, - and you must have configured the print commands used by latexmk. - This can be non-trivial. See the documentation on the $lpr, - $lpr_dvi, and $lpr_pdf configuration variables to see how to set - the commands for printing. - This option is incompatible with the -pv and -pvc options, so it - turns them off. +LATEXMK(1) General Commands Manual LATEXMK(1) - -pdf Generate pdf version of document using pdflatex. (If you wish - to use lualatex or xelatex, you can use whichever of the options - -pdflua, -pdfxe, -lualatex or -xelatex applies.) To configure - latexmk to have such behavior by default, see the section on "Configuration/initialization (rc) files". -pdfdvi - Generate pdf version of document from the dvi file, by default + Generate pdf version of document from the dvi file, by default using dvipdf. @@ -759,68 +808,73 @@ LATEXMK(1) General Commands Manual LATEXMK(1) Generate pdf version of document using lualatex. - -pdfps Generate pdf version of document from the ps file, by default + -pdfps Generate pdf version of document from the ps file, by default using ps2pdf. - -pdfxe Generate pdf version of document using xelatex. Note that to - optimize processing time, latexmk uses xelatex to generate an - xdv file rather than a pdf file directly. Only after possibly - multiple runs to generate a fully up-to-date xdv does latexmk + -pdfxe Generate pdf version of document using xelatex. Note that to + optimize processing time, latexmk uses xelatex to generate an + xdv file rather than a pdf file directly. Only after possibly + multiple runs to generate a fully up-to-date xdv does latexmk then call xdvipdfmx to generate the final pdf file. - (Note: When the document includes large graphics files, espe- - cially png files, the last step can be quite time consuming, - even when the creation of the xdv file by xelatex is fast. So - the use of the intermediate xdv file can result in substantial - gains in procesing time, since the pdf file is produced once + (Note: When the document includes large graphics files, espe- + cially png files, the last step can be quite time consuming, + even when the creation of the xdv file by xelatex is fast. So + the use of the intermediate xdv file can result in substantial + gains in procesing time, since the pdf file is produced once rather than on every run of xelatex.) - -pdf- Turn off generation of pdf version of document. (This can be - used to override a setting in a configuration file. It may get + -pdf- Turn off generation of pdf version of document. (This can be + used to override a setting in a configuration file. It may get overridden if some other option requires the generation of a pdf file.) + If after all options have been processed, pdf generation is + still turned off, then generation of a dvi file will be turned + on, and then the program used to compiled a document will be + latex (or, more precisely, whatever program is configured to be + used in the $latex configuration variable). + -pdflatex="COMMAND" + This sets the string specifying the command to run pdflatex, and + is typically used to add desired options. Since the string nor- + mally contains spaces, it should be quoted, e.g., + latexmk -pdf -pdflatex="pdflatex --shell-escape %O %S" + foo.tex + The specification of the contents of the string are the same as + for the $pdflatex configuration variable. Depending on your + operating system and the command-line shell you are using, you + may need to change the single quotes to double quotes (or - 19 January 2017 12 + 20 November 2017 13 -LATEXMK(1) General Commands Manual LATEXMK(1) - -pdflatex="COMMAND" - This sets the string specifying the command to run pdflatex, and - is typically used to add desired options. Since the string nor- - mally contains spaces, it should be quoted, e.g., +LATEXMK(1) General Commands Manual LATEXMK(1) - latexmk -pdf -pdflatex="pdflatex --shell-escape %O %S" - foo.tex - The specification of the contents of the string are the same as - for the $pdflatex configuration variable. Depending on your - operating system and the command-line shell you are using, you - may need to change the single quotes to double quotes (or some- - thing else). + something else). - To set the command for running latex (rather than the command + To set the command for running latex (rather than the command for pdflatex) see the -latex option. -print=dvi, -print=ps, -print=pdf, -print=auto, - Define which kind of file is printed. This option also ensures + Define which kind of file is printed. This option also ensures that the requisite file is made, and turns on printing. The (default) case -print=auto determines the kind of print file - automatically from the set of files that is being made. The - first in the list postscript, pdf, dvi that is among the files + automatically from the set of files that is being made. The + first in the list postscript, pdf, dvi that is among the files to be made is the one used for print out. @@ -828,13 +882,13 @@ LATEXMK(1) General Commands Manual LATEXMK(1) -ps- Turn off generation of postscript version of document. This can - be used to override a setting in a configuration file. (It may - get overridden by some other option that requires a postscript + be used to override a setting in a configuration file. (It may + get overridden by some other option that requires a postscript file, for example a request for printing.) - -pF Postscript file filtering. The argument to this option is a - filter which will generate a filtered postscript file with the + -pF Postscript file filtering. The argument to this option is a + filter which will generate a filtered postscript file with the extension ".psF". All extra processing (e.g. preview, printing) will then be performed on this filtered postscript file. @@ -847,124 +901,123 @@ LATEXMK(1) General Commands Manual LATEXMK(1) latexmk -ps -pF "psnup -2" foo.tex Whether to use single or double quotes round the "psnup -2" will - depend on your command interpreter, as used by the particular + depend on your command interpreter, as used by the particular version of perl and the operating system on your computer. + -pv Run file previewer. If the -view option is used, this will + select the kind of file to be previewed (dvi, ps or pdf). Oth- + erwise the viewer views the "highest" kind of file selected, by + the -dvi, -ps, -pdf, -pdfps options, in the order dvi, ps, pdf + (low to high). If no file type has been selected, the dvi pre- + viewer will be used. This option is incompatible with the -p + and -pvc options, so it turns them off. - 19 January 2017 13 + -pv- Turn off -pv. + 20 November 2017 14 -LATEXMK(1) General Commands Manual LATEXMK(1) - -pv Run file previewer. If the -view option is used, this will - select the kind of file to be previewed (dvi, ps or pdf). Oth- - erwise the viewer views the "highest" kind of file selected, by - the -dvi, -ps, -pdf, -pdfps options, in the order dvi, ps, pdf - (low to high). If no file type has been selected, the dvi pre- - viewer will be used. This option is incompatible with the -p - and -pvc options, so it turns them off. - -pv- Turn off -pv. +LATEXMK(1) General Commands Manual LATEXMK(1) - -pvc Run a file previewer and continually update the .dvi, .ps, + -pvc Run a file previewer and continually update the .dvi, .ps, and/or .pdf files whenever changes are made to source files (see - the Description above). Which of these files is generated and - which is viewed is governed by the other options, and is the - same as for the -pv option. The preview-continuous option -pvc - can only work with one file. So in this case you will normally - only specify one filename on the command line. It is also - incompatible with the -p and -pv options, so it turns these + the Description above). Which of these files is generated and + which is viewed is governed by the other options, and is the + same as for the -pv option. The preview-continuous option -pvc + can only work with one file. So in this case you will normally + only specify one filename on the command line. It is also + incompatible with the -p and -pv options, so it turns these options off. - The -pvc option also turns off force mode (-f), as is normally - best for continuous preview mode. If you really want force + The -pvc option also turns off force mode (-f), as is normally + best for continuous preview mode. If you really want force mode, use the options in the order -pvc -f. With a good previewer the display will be automatically updated. - (Under some but not all versions of UNIX/Linux "gv -watch" does - this for postscript files; this can be set by a configuration - variable. This would also work for pdf files except for an - apparent bug in gv that causes an error when the newly updated - pdf file is read.) Many other previewers will need a manual + (Under some but not all versions of UNIX/Linux "gv -watch" does + this for postscript files; this can be set by a configuration + variable. This would also work for pdf files except for an + apparent bug in gv that causes an error when the newly updated + pdf file is read.) Many other previewers will need a manual update. Important note: the acroread program on MS-Windows locks the pdf - file, and prevents new versions being written, so it is a bad - idea to use acroread to view pdf files in preview-continuous - mode. It is better to use a different viewer: SumatraPDF and + file, and prevents new versions being written, so it is a bad + idea to use acroread to view pdf files in preview-continuous + mode. It is better to use a different viewer: SumatraPDF and gsview are good possibilities. - There are some other methods for arranging an update, notably - useful for many versions of xdvi and xpdf. These are best set + There are some other methods for arranging an update, notably + useful for many versions of xdvi and xpdf. These are best set in latexmk's configuration; see below. - Note that if latexmk dies or is stopped by the user, the + Note that if latexmk dies or is stopped by the user, the "forked" previewer will continue to run. Successive invocations - with the -pvc option will not fork new previewers, but latexmk - will normally use the existing previewer. (At least this will - happen when latexmk is running under an operating system where - it knows how to determine whether an existing previewer is run- + with the -pvc option will not fork new previewers, but latexmk + will normally use the existing previewer. (At least this will + happen when latexmk is running under an operating system where + it knows how to determine whether an existing previewer is run- ning.) - -pvc- + -pvc- Turn off -pvc. + -quiet Same as -silent - 19 January 2017 14 + -r <rcfile> + Read the specified initialization file ("RC file") before pro- + cessing. + Be careful about the ordering: (1) Standard initialization files + -- see the section below on "Configuration/initialization (RC) + files" -- are read first. (2) Then the options on the command -LATEXMK(1) General Commands Manual LATEXMK(1) + 20 November 2017 15 - Turn off -pvc. - -quiet Same as -silent +LATEXMK(1) General Commands Manual LATEXMK(1) - -r <rcfile> - Read the specified initialization file ("RC file") before pro- - cessing. - Be careful about the ordering: (1) Standard initialization files - -- see the section below on "Configuration/initialization (RC) - files" -- are read first. (2) Then the options on the command - line are acted on in the order they are given. Therefore if an - initialization file is specified by the -r option, it is read - during this second step. Thus an initialization file specified + line are acted on in the order they are given. Therefore if an + initialization file is specified by the -r option, it is read + during this second step. Thus an initialization file specified with the -r option can override both the standard initialization files and previously specified options. But all of these can be overridden by later options. The contents of the RC file just comprise a piece of code in the - Perl programming language (typically a sequence of assignment + Perl programming language (typically a sequence of assignment statements); they are executed when the -r option is encountered during latexmk's parsing of its command line. See the -e option - for a way of giving initialization code directly on latexmk's - command line. An error results in latexmk stopping. Multiple - instances of the -r and -e options can be used, and they are + for a way of giving initialization code directly on latexmk's + command line. An error results in latexmk stopping. Multiple + instances of the -r and -e options can be used, and they are executed in the order they appear on the command line. -recorder - Give the -recorder option with latex and pdflatex. In (most) - modern versions of these programs, this results in a file of - extension .fls containing a list of the files that these pro- + Give the -recorder option with latex and pdflatex. In (most) + modern versions of these programs, this results in a file of + extension .fls containing a list of the files that these pro- grams have read and written. Latexmk will then use this file to - improve its detection of source files and generated files after - a run of latex or pdflatex. This is the default setting of + improve its detection of source files and generated files after + a run of latex or pdflatex. This is the default setting of latexmk, unless overridden in an initialization file. For further information, see the documentation for the $recorder @@ -979,69 +1032,70 @@ LATEXMK(1) General Commands Manual LATEXMK(1) -rules- - Do not show a list of latexmk's rules and dependencies after + Do not show a list of latexmk's rules and dependencies after processing. (This is the default.) + -showextraoptions + Show the list of extra latex and pdflatex options that latexmk + recognizes, but that it simply passes through to the programs + latex, pdflatex, etc when they are run. These options are + (currently) a combination of those allowed by the TeXLive and + MiKTeX implementations. (If a particular option is given to + latexmk but is not handled by the particular implementation of + latex or pdflatex that is being used, that program will probably + give an error message.) These options are very numerous, but + are not listed in this documentation because they have no effect + on latexmk's actions. - 19 January 2017 15 + 20 November 2017 16 -LATEXMK(1) General Commands Manual LATEXMK(1) - -showextraoptions - Show the list of extra latex and pdflatex options that latexmk - recognizes, but that it simply passes through to the programs - latex, pdflatex, etc when they are run. These options are - (currently) a combination of those allowed by the TeXLive and - MiKTeX implementations. (If a particular option is given to - latexmk but is not handled by the particular implementation of - latex or pdflatex that is being used, that program will probably - give an error message.) These options are very numerous, but - are not listed in this documentation because they have no effect - on latexmk's actions. +LATEXMK(1) General Commands Manual LATEXMK(1) + - There are a few options (-includedirectory=dir, -initialize, - -ini) that are not recognized, either because they don't fit + There are a few options (-includedirectory=dir, -initialize, + -ini) that are not recognized, either because they don't fit with latexmk's intended operations, or because they need special - processing by latexmk that isn't implemented (at least, not + processing by latexmk that isn't implemented (at least, not yet). - There are also options that are accepted by latex etc, but + There are also options that are accepted by latex etc, but instead trigger actions by latexmk: -help, -version. Finally, there are certain options for latex and pdflatex (e.g., - -recorder) that trigger special actions or behavior by latexmk - itself as well as being passed in some form to the called latex - and pdflatex program, or that affect other programs as well. - These options do have entries in this documentation. These + -recorder) that trigger special actions or behavior by latexmk + itself as well as being passed in some form to the called latex + and pdflatex program, or that affect other programs as well. + These options do have entries in this documentation. These options are: -jobname=STRING, -aux-directory=dir, -output-direc- tory=DIR, -quiet, and -recorder. -silent Run commands silently, i.e., with options that reduce the amount - of diagnostics generated. For example, with the default set- - tings, the command "latex -interaction=batchmode" is used for + of diagnostics generated. For example, with the default set- + tings, the command "latex -interaction=batchmode" is used for (pdf)latex and friends. - See also the -logfilewarninglist and -logfilewarninglist- + See also the -logfilewarninglist and -logfilewarninglist- options. - Also reduce the number of informational messages that latexmk + Also reduce the number of informational messages that latexmk itself generates. - To change the options used to make the commands run silently, + To change the options used to make the commands run silently, you need to configure latexmk with changed values of its config- - uration variables, the relevant ones being $bib- - tex_silent_switch, $biber_silent_switch, $dvipdf_silent_switch, - $dvips_silent_switch, $latex_silent_switch, $luala- - tex_silent_switch $makeindex_silent_switch, $pdfla- + uration variables, the relevant ones being $bib- + tex_silent_switch, $biber_silent_switch, $dvipdf_silent_switch, + $dvips_silent_switch, $latex_silent_switch, $luala- + tex_silent_switch $makeindex_silent_switch, $pdfla- tex_silent_switch, and $xelatex_silent_switch @@ -1049,42 +1103,43 @@ LATEXMK(1) General Commands Manual LATEXMK(1) $show_time. + -time- Do not show CPU time used. See also the configuration variable + $show_time. - 19 January 2017 16 + -use-make + When after a run of latex or pdflatex, there are warnings about + missing files (e.g., as requested by the LaTeX \input, \include, + and \includgraphics commands), latexmk tries to make them by a + custom dependency. If no relevant custom dependency with an + appropriate source file is found, and if the -use-make option is + set, then as a last resort latexmk will try to use the make + 20 November 2017 17 -LATEXMK(1) General Commands Manual LATEXMK(1) - -time- Do not show CPU time used. See also the configuration variable - $show_time. +LATEXMK(1) General Commands Manual LATEXMK(1) - -use-make - When after a run of latex or pdflatex, there are warnings about - missing files (e.g., as requested by the LaTeX \input, \include, - and \includgraphics commands), latexmk tries to make them by a - custom dependency. If no relevant custom dependency with an - appropriate source file is found, and if the -use-make option is - set, then as a last resort latexmk will try to use the make pro- - gram to try to make the missing files. - Note that the filename may be specified without an extension, - e.g., by \includegraphics{drawing} in a LaTeX file. In that - case, latexmk will try making drawing.ext with ext set in turn - to the possible extensions that are relevant for latex (or as + program to try to make the missing files. + + Note that the filename may be specified without an extension, + e.g., by \includegraphics{drawing} in a LaTeX file. In that + case, latexmk will try making drawing.ext with ext set in turn + to the possible extensions that are relevant for latex (or as appropriate pdflatex). - See also the documentation for the $use_make_for_missing_files + See also the documentation for the $use_make_for_missing_files configuration variable. -use-make- - Do not use the make program to try to make missing files. + Do not use the make program to try to make missing files. (Default.) @@ -1101,52 +1156,53 @@ LATEXMK(1) General Commands Manual LATEXMK(1) the -pv or -pvc switches). The default is to view the "highest" kind of requested file (in the low-to-high order dvi, ps, pdf). - Note the possibility -view=none where no viewer is opened at - all. One example of is use is in conjunction with the -pvc - option, when you want latexmk to do a compilation automatically - whenever source file(s) change, but do not want a previewer to + Note the possibility -view=none where no viewer is opened at + all. One example of is use is in conjunction with the -pvc + option, when you want latexmk to do a compilation automatically + whenever source file(s) change, but do not want a previewer to be opened. -xelatex Use xelatex. That is, use xelatex to process the source file(s) - to pdf. The generation of dvi and postscript files is turned + to pdf. The generation of dvi and postscript files is turned off. This option is equivalent to using the following set of options + -pdfxe -dvi- -ps- + + [Note: Note that the method of implementation of this option, + but not its intended primary effect, differ from some earlier + versions of latexmk. Latexmk first uses xelatex to make an xdv + file, and does all the extra runs needed (including those of + bibtex, etc). Only after that does it make the pdf file from + the xdv file, using xdvipdfmx. This procedure can result in + considerable savings in run time, since the xdv-to-pdf conver- + sion is quite time-consuming when large graphics files are used - 19 January 2017 17 + 20 November 2017 18 -LATEXMK(1) General Commands Manual LATEXMK(1) +LATEXMK(1) General Commands Manual LATEXMK(1) - -pdfxe -dvi- -ps- - [Note: Note that the method of implementation of this option, - but not its intended primary effect, differ from some earlier - versions of latexmk. Latexmk first uses xelatex to make an xdv - file, and does all the extra runs needed (including those of - bibtex, etc). Only after that does it make the pdf file from - the xdv file, using xdvipdfmx. This procedure can result in - considerable savings in run time, since the xdv-to-pdf conver- - sion is quite time-consuming when large graphics files are used in the document.] Compatibility between options - The preview-continuous option -pvc can only work with one file. So in - this case you will normally only specify one filename on the command + The preview-continuous option -pvc can only work with one file. So in + this case you will normally only specify one filename on the command line. - Options -p, -pv and -pvc are mutually exclusive. So each of these + Options -p, -pv and -pvc are mutually exclusive. So each of these options turns the others off. @@ -1174,102 +1230,104 @@ EXAMPLES DEALING WITH ERRORS, PROBLEMS, ETC Some possibilities: - a. If you get a strange error, do look carefully at the output that is - on the screen and in log files. While there is much that is notori- + a. If you get a strange error, do look carefully at the output that is + on the screen and in log files. While there is much that is notori- ously verbose in the output of latex (and that is added to by latexmk), - the verbosity is there for a reason: to enable the user to diagnose - problems. Latexmk does repeat some messages at the end of a run that - it thinks would otherwise be easy to miss in the middle of other + the verbosity is there for a reason: to enable the user to diagnose + problems. Latexmk does repeat some messages at the end of a run that + it thinks would otherwise be easy to miss in the middle of other out- + put. + b. Generally, remember that latexmk does its work by running other pro- + grams. Your first priority in dealing with errors should be to examine + what went wrong with the individual programs. Then you need to correct + the causes of errors in the runs of these programs. (Often these come + from errors in the source document, but they could also be about miss- + ing LaTeX packages, etc.) + c. If latexmk doesn't run the programs the way you would like, then you - 19 January 2017 18 + 20 November 2017 19 -LATEXMK(1) General Commands Manual LATEXMK(1) - output. +LATEXMK(1) General Commands Manual LATEXMK(1) - b. Generally, remember that latexmk does its work by running other pro- - grams. Your first priority in dealing with errors should be to examine - what went wrong with the individual programs. Then you need to correct - the causes of errors in the runs of these programs. (Often these come - from errors in the source document, but they could also be about miss- - ing LaTeX packages, etc.) - c. If latexmk doesn't run the programs the way you would like, then you - need to look in this documentation at the list of command line options - and then at the sections on configuration/initialization files. A lot - of latexmk's behavior is configurable to deal with particular situa- + need to look in this documentation at the list of command line options + and then at the sections on configuration/initialization files. A lot + of latexmk's behavior is configurable to deal with particular situa- tions. (But there is a lot of reading!) - The remainder of these notes consists of ideas for dealing with more + The remainder of these notes consists of ideas for dealing with more difficult situations. - d. Further tricks can involve replacing the standard commands that + d. Further tricks can involve replacing the standard commands that latexmk runs by other commands or scripts. - e. For possible examples of code for use in an RC file, see the direc- - tory example_rcfiles in the distribution of latexmk (e.g., at + e. For possible examples of code for use in an RC file, see the direc- + tory example_rcfiles in the distribution of latexmk (e.g., at http://mirror.ctan.org/support/latexmk/example_rcfiles). Even if these examples don't do what you want, they may provide suitable inspiration. - f. There's a useful trick that can be used when you use lualatex - instead of pdflatex (and in some related situations). The problem is - that latexmk won't notice a dependency on a file, bar.baz say, that is - input by the lua code in your document instead of by the LaTeX part. - (Thus if you change bar.baz and rerun latexmk, then latexmk will think - no files have changed and not rerun lualatex, whereas if you had - '\input{bar.baz}' in the LaTeX part of the document, latexmk would - notice the change.) One solution is just to put the following some- + f. There's a useful trick that can be used when you use lualatex + instead of pdflatex (and in some related situations). The problem is + that latexmk won't notice a dependency on a file, bar.baz say, that is + input by the lua code in your document instead of by the LaTeX part. + (Thus if you change bar.baz and rerun latexmk, then latexmk will think + no files have changed and not rerun lualatex, whereas if you had + '\input{bar.baz}' in the LaTeX part of the document, latexmk would + notice the change.) One solution is just to put the following some- where in the LaTeX part of the document: \typeout{(bar.baz)} - This puts a line in the log file that latexmk will treat as implying - that the file bar.baz was read. (At present I don't know a way of - doing this automatically.) Of course, if the file has a different + This puts a line in the log file that latexmk will treat as implying + that the file bar.baz was read. (At present I don't know a way of + doing this automatically.) Of course, if the file has a different name, change bar.baz to the name of your file. g. See also the section ADVANCED CONFIGURATION: Some extra resources. - h. Look on tex.stackexchange, i.e., at http://tex.stackex- - change.com/questions/tagged/latexmk Someone may have already solved + h. Look on tex.stackexchange, i.e., at http://tex.stackex- + change.com/questions/tagged/latexmk Someone may have already solved your problem. i. Ask a question at tex.stackexchange.com. - j. Or ask me (the author of latexmk). My e-mail is at the end of this + j. Or ask me (the author of latexmk). My e-mail is at the end of this documentation. +CONFIGURATION/INITIALIZATION (RC) FILES + Latexmk can be customized using initialization files, which are read at + startup in the following order: - 19 January 2017 19 + 1) The system RC file, if it exists. + On a UNIX system, latexmk searches for following places for its sys- + tem RC file, in the following order, and reads the first it finds: + "/opt/local/share/latexmk/LatexMk", + 20 November 2017 20 -LATEXMK(1) General Commands Manual LATEXMK(1) -CONFIGURATION/INITIALIZATION (RC) FILES - Latexmk can be customized using initialization files, which are read at - startup in the following order: - 1) The system RC file, if it exists. - On a UNIX system, latexmk searches for following places for its sys- - tem RC file, in the following order, and reads the first it finds: - "/opt/local/share/latexmk/LatexMk", +LATEXMK(1) General Commands Manual LATEXMK(1) + + "/usr/local/share/latexmk/LatexMk", "/usr/local/lib/latexmk/LatexMk". On a MS-Windows system it looks for "C:\latexmk\LatexMk". - On a cygwin system (i.e., a MS-Windows system in which Perl is that + On a cygwin system (i.e., a MS-Windows system in which Perl is that of cygwin), latexmk reads the first it finds of "/cygdrive/c/latexmk/LatexMk", "/opt/local/share/latexmk/LatexMk", @@ -1280,67 +1338,66 @@ CONFIGURATION/INITIALIZATION (RC) FILES name replaced "LatexMk" replaced by "latexmkrc". 2) The user's RC file, if it exists. This can be in one of two places. - The traditional one is ".latexmkrc" in the user's home directory. The - other possibility is "latexmk/latexmkrc" in the user's XDG configura- - tion home directory. The actual file read is the first of "$XDG_CON- - FIG_HOME/latexmk/latexmkrc" or "$HOME/.latexmkrc" which exists. (See + The traditional one is ".latexmkrc" in the user's home directory. The + other possibility is "latexmk/latexmkrc" in the user's XDG configura- + tion home directory. The actual file read is the first of "$XDG_CON- + FIG_HOME/latexmk/latexmkrc" or "$HOME/.latexmkrc" which exists. (See https://specifications.freedesktop.org/basedir-spec/basedir-spec-lat- est.html for details on the XDG Base Directory Specification.) - Here $HOME is the user's home directory. [Latexmk determines the - user's home directory as follows: It is the value of the environment - variable HOME, if this variable exists, which normally is the case on - UNIX-like systems (including Linux and OS-X). Otherwise the environ- - ment variable USERPROFILE is used, if it exists, which normally is the + Here $HOME is the user's home directory. [Latexmk determines the + user's home directory as follows: It is the value of the environment + variable HOME, if this variable exists, which normally is the case on + UNIX-like systems (including Linux and OS-X). Otherwise the environ- + ment variable USERPROFILE is used, if it exists, which normally is the case on MS-Windows systems. Otherwise a blank string is used instead of $HOME, in which case latexmk does not look for an RC file in it.] - $XDG_CONFIG_HOME is the value of the environment variable XDG_CON- - FIG_HOME if it exists. If this environment variable does not exist, - but $HOME is non-blank, then $XDG_CONFIG_HOME is set to the default - value of $HOME/.config. Otherwise $XDG_CONFIG_HOME is blank, and + $XDG_CONFIG_HOME is the value of the environment variable XDG_CON- + FIG_HOME if it exists. If this environment variable does not exist, + but $HOME is non-blank, then $XDG_CONFIG_HOME is set to the default + value of $HOME/.config. Otherwise $XDG_CONFIG_HOME is blank, and latexmk does not look for an RC file under it. - 3) The RC file in the current working directory. This file can be - named either "latexmkrc" or ".latexmkrc", and the first of these to be + 3) The RC file in the current working directory. This file can be + named either "latexmkrc" or ".latexmkrc", and the first of these to be found is used, if any. 4) Any RC file(s) specified on the command line with the -r option. Each RC file is a sequence of Perl commands. Naturally, a user can use - this in creative ways. But for most purposes, one simply uses a - sequence of assignment statements that override some of the built-in - settings of Latexmk. Straightforward cases can be handled without - + this in creative ways. But for most purposes, one simply uses a + sequence of assignment statements that override some of the built-in + settings of Latexmk. Straightforward cases can be handled without + knowledge of the Perl language by using the examples in this document + as templates. Comment lines are introduced by the "#" character. + Note that command line options are obeyed in the order in which they + are written; thus any RC file specified on the command line with the -r + option can override previous options but can be itself overridden by + later options on the command line. There is also the -e option, which + allows initialization code to be specified in latexmk's command line. - 19 January 2017 20 + 20 November 2017 21 -LATEXMK(1) General Commands Manual LATEXMK(1) - knowledge of the Perl language by using the examples in this document - as templates. Comment lines are introduced by the "#" character. +LATEXMK(1) General Commands Manual LATEXMK(1) - Note that command line options are obeyed in the order in which they - are written; thus any RC file specified on the command line with the -r - option can override previous options but can be itself overridden by - later options on the command line. There is also the -e option, which - allows initialization code to be specified in latexmk's command line. - For possible examples of code for in an RC file, see the directory - example_rcfiles in the distribution of latexmk (e.g., at http://mir- + For possible examples of code for in an RC file, see the directory + example_rcfiles in the distribution of latexmk (e.g., at http://mir- ror.ctan.org/support/latexmk/example_rcfiles). HOW TO SET VARIABLES IN INITIALIZATION FILES - The important variables that can be configured are described in the - section "List of configuration variables usable in initialization + The important variables that can be configured are described in the + section "List of configuration variables usable in initialization files". Syntax for setting these variables is of the following forms: $bibtex = 'bibtex %O %B'; @@ -1353,76 +1410,76 @@ HOW TO SET VARIABLES IN INITIALIZATION FILES @default_files = ('paper', 'paper1'); - for the setting of an array of strings. It is possible to append an + for the setting of an array of strings. It is possible to append an item to an array variable as follows: push @default_files, 'paper2'; - Note that simple "scalar" variables have names that begin with a $ + Note that simple "scalar" variables have names that begin with a $ character and array variables have names that begin with a @ character. Each statement ends with a semicolon. - Strings should be enclosed in single quotes. (You could use double - quotes, as in many programming languages. But then the Perl program- - ming language brings into play some special rules for interpolating - variables into strings. People not fluent in Perl will want to avoid + Strings should be enclosed in single quotes. (You could use double + quotes, as in many programming languages. But then the Perl program- + ming language brings into play some special rules for interpolating + variables into strings. People not fluent in Perl will want to avoid these complications.) - You can do much more complicated things, but for this you will need to + You can do much more complicated things, but for this you will need to consult a manual for the Perl programming language. FORMAT OF COMMAND SPECIFICATIONS - Some of the variables set the commands that latexmk uses for carrying - out its work, for example to generate a dvi file from a tex file or to + Some of the variables set the commands that latexmk uses for carrying + out its work, for example to generate a dvi file from a tex file or to view a postscript file. This section describes some important features + of how the commands are specified. (Note that some of the possibili- + ties listed here do not apply to the $kpsewhich variable; see its docu- + mentation.) + Placeholders: Supposed you wanted latexmk to use the command elatex in + place of the regular latex command, and suppose moreover that you + wanted to give it the option "--shell-escape". You could do this by + the following setting: - 19 January 2017 21 + 20 November 2017 22 -LATEXMK(1) General Commands Manual LATEXMK(1) - of how the commands are specified. (Note that some of the possibili- - ties listed here do not apply to the $kpsewhich variable; see its docu- - mentation.) +LATEXMK(1) General Commands Manual LATEXMK(1) - Placeholders: Supposed you wanted latexmk to use the command elatex in - place of the regular latex command, and suppose moreover that you - wanted to give it the option "--shell-escape". You could do this by - the following setting: $latex = 'elatex --shell-escape %O %S'; - The two items starting with the % character are placeholders. These - are substituted by appropriate values before the command is run. Thus - %S will be replaced by the source file that elatex will be applied to, - and %O will be replaced by any options that latexmk has decided to use + The two items starting with the % character are placeholders. These + are substituted by appropriate values before the command is run. Thus + %S will be replaced by the source file that elatex will be applied to, + and %O will be replaced by any options that latexmk has decided to use for this command. (E.g., if you used the -silent option in the invoca- - tion of latexmk, it results in the replacement of %O by "-interac- + tion of latexmk, it results in the replacement of %O by "-interac- tion=batchmode".) The available placeholders are: - %B base of filename for current command. E.g., if a postscript - file document.ps is being made from the dvi file document.dvi, + %B base of filename for current command. E.g., if a postscript + file document.ps is being made from the dvi file document.dvi, then the basename is document. - %D destination file (e.g., the name of the postscript file when + %D destination file (e.g., the name of the postscript file when converting a dvi file to postscript). %O options %R root filename. This is the base name for the main tex file. - %S source file (e.g., the name of the dvi file when converting a + %S source file (e.g., the name of the dvi file when converting a dvi file to ps). %T The name of the primary tex file. @@ -1431,89 +1488,98 @@ LATEXMK(1) General Commands Manual LATEXMK(1) tion variable $aux_dir). A directory separation character ('/') is appended if $aux_dir is non-empty and does not end in a suit- able character, with suitable characters being those appropriate - to UNIX and MS-Windows, i.e., ':', '/' and '\'. Note that if - after initialization, $out_dir is set, but $aux_dir is not set - (i.e., it is blank), then latexmk sets $aux_dir to the same + to UNIX and MS-Windows, i.e., ':', '/' and '\'. Note that if + after initialization, $out_dir is set, but $aux_dir is not set + (i.e., it is blank), then latexmk sets $aux_dir to the same value $out_dir. - %Z Name of directory for output files (see the configuration vari- - able $out_dir). A directory separation character ('/') is + %Z Name of directory for output files (see the configuration vari- + able $out_dir). A directory separation character ('/') is appended if $out_dir is non-empty and does not end in a suitable - character, with suitable characters being those appropriate to + character, with suitable characters being those appropriate to UNIX and MS-Windows, i.e., ':', '/' and '\'. - If for some reason you need a literal % character in your string not + If for some reason you need a literal % character in your string not subject to the above rules, use "%%". + Appropriate quoting will be applied to the filename substitutions, so + you mustn't supply them yourself even if the names of your files have + spaces in them. (But if your TeX filenames have spaces in them, beware + that many versions of the TeX program cannot correctly handle filenames + containing spaces.) In case latexmk's quoting does not work correctly + on your system, you can turn it off -- see the documentation for the + variable $quote_filenames. - 19 January 2017 22 + 20 November 2017 23 -LATEXMK(1) General Commands Manual LATEXMK(1) - Appropriate quoting will be applied to the filename substitutions, so - you mustn't supply them yourself even if the names of your files have - spaces in them. (But if your TeX filenames have spaces in them, beware - that many versions of the TeX program cannot correctly handle filenames - containing spaces.) In case latexmk's quoting does not work correctly - on your system, you can turn it off -- see the documentation for the - variable $quote_filenames. +LATEXMK(1) General Commands Manual LATEXMK(1) + - The distinction between %B and %R needs a bit of care, since they are - often the same, but not always. For example on a simple document, the + The distinction between %B and %R needs a bit of care, since they are + often the same, but not always. For example on a simple document, the basename of a bibtex run is the same as for the texfile. But in a doc- - ument with several bibliographies, the bibliography files will have a - variety of names. Since bibtex is invoked with the basename of the - bibliography file, the setting for the bibtex command should therefore + ument with several bibliographies, the bibliography files will have a + variety of names. Since bibtex is invoked with the basename of the + bibliography file, the setting for the bibtex command should therefore be $bibtex = 'bibtex %O %B'; - Generally, you should use %B rather than %R. Similarly for most pur- + Generally, you should use %B rather than %R. Similarly for most pur- poses, the name %T of the primary texfile is not a useful placeholder. - See the default values in the section "List of configuration variables + See the default values in the section "List of configuration variables usable in initialization files" for what is normally the most appropri- ate usage. If you omit to supply any placeholders whatever in the specification of - a command, latexmk will supply what its author thinks are appropriate + a command, latexmk will supply what its author thinks are appropriate defaults. This gives compatibility with configuration files for previ- ous versions of latexmk, which didn't use placeholders. - "Detaching" a command: Normally when latexmk runs a command, it waits + "Detaching" a command: Normally when latexmk runs a command, it waits for the command to run to completion. This is appropriate for commands like latex, of course. But for previewers, the command should normally - run detached, so that latexmk gets the previewer running and then + run detached, so that latexmk gets the previewer running and then returns to its next task (or exits if there is nothing else to do). To - achieve this effect of detaching a command, you need to precede the + achieve this effect of detaching a command, you need to precede the command name with "start ", as in $dvi_previewer = 'start xdvi %O %S'; - This will be translated to whatever is appropriate for your operating + This will be translated to whatever is appropriate for your operating system. - Notes: (1) In some circumstances, latexmk will always run a command + Notes: (1) In some circumstances, latexmk will always run a command detached. This is the case for a previewer in preview continuous mode, - since otherwise previewing continuously makes no sense. (2) This pre- - cludes the possibility of running a command named start. (3) If the - word start occurs more than once at the beginning of the command - string, that is equivalent to having just one. (4) Under cygwin, some - complications happen, since cygwin amounts to a complicated merging of - UNIX and MS-Windows. See the source code for how I've handled the + since otherwise previewing continuously makes no sense. (2) This pre- + cludes the possibility of running a command named start. (3) If the + word start occurs more than once at the beginning of the command + string, that is equivalent to having just one. (4) Under cygwin, some + complications happen, since cygwin amounts to a complicated merging of + UNIX and MS-Windows. See the source code for how I've handled the problem. Command names containing spaces: Under MS-Windows it is common that the + name of a command includes spaces, since software is often installed in + a subdirectory of "C:\Program Files". Such command names should be + enclosed in double quotes, as in + $lpr_pdf = '"c:/Program Files/Ghostgum/gsview/gsview32.exe" /p + %S'; + $pdf_previewer = 'start "c:/Program Files/SumatraPDF/Suma- + traPDF.exe" %O %S'; - 19 January 2017 23 + + 20 November 2017 24 @@ -1522,43 +1588,35 @@ LATEXMK(1) General Commands Manual LATEXMK(1) LATEXMK(1) General Commands Manual LATEXMK(1) - name of a command includes spaces, since software is often installed in - a subdirectory of "C:\Program Files". Such command names should be - enclosed in double quotes, as in - - $lpr_pdf = '"c:/Program Files/Ghostgum/gsview/gsview32.exe" /p - %S'; - $pdf_previewer = 'start "c:/Program Files/SumatraPDF/Suma- - traPDF.exe" %O %S'; - $pdf_previewer = 'start "c:/Program Files/SumatraPDF (x86)/Suma- + $pdf_previewer = 'start "c:/Program Files/SumatraPDF (x86)/Suma- traPDF.exe" %O %S'; - (Note about the above example: Under MS-Windows forward slashes are + (Note about the above example: Under MS-Windows forward slashes are equivalent to backslashes in a filename under almost all circumstances, - provided that the filename is inside double quotes. It is easier to + provided that the filename is inside double quotes. It is easier to use forward slashes in examples like the one above, since then one does - not have to worry about the rules for dealing with forward slashes in + not have to worry about the rules for dealing with forward slashes in strings in the Perl language.) - Command names under Cygwin: If latexmk is executed by Cygwin's Perl, + Command names under Cygwin: If latexmk is executed by Cygwin's Perl, be particularly certain that pathnames in commands have forward slashes - not the usual backslashes for the separator of pathname components. - See the above examples. Backslashes often get misinterpreted by the + not the usual backslashes for the separator of pathname components. + See the above examples. Backslashes often get misinterpreted by the Unix shell used by Cygwin's Perl to execute external commands. Forward slashes don't suffer from this problem, and (when quoted, as above) are equally acceptable to MS-Windows. - Using MS-Windows file associations: A useful trick under modern ver- + Using MS-Windows file associations: A useful trick under modern ver- sions of MS-Windows (e.g., WinXP) is to use just the command 'start' by itself: $dvi_previewer = 'start %S'; Under MS-Windows, this will cause to be run whatever program the system - has associated with dvi files. (The same applies for a postscript + has associated with dvi files. (The same applies for a postscript viewer and a pdf viewer.) But note that this trick is not always suit- - able for the pdf previwer, if your system has acroread for the default + able for the pdf previwer, if your system has acroread for the default pdf viewer. As explained elsewhere, acroread under MS-Windows does not work well with latex and latexmk, because acroread locks the pdf file. @@ -1567,63 +1625,63 @@ LATEXMK(1) General Commands Manual LATEXMK(1) $lpr = 'NONE lpr'; - This typically is used when an appropriate command does not exist on + This typically is used when an appropriate command does not exist on your system. The string after the "NONE" is effectively a comment. Options to commands: Setting the name of a command can be used not only for changing the name of the command called, but also to add options to - command. Suppose you want latexmk to use latex with source specials - enabled. Then you might use the following line in an initialization + command. Suppose you want latexmk to use latex with source specials + enabled. Then you might use the following line in an initialization file: + $latex = 'latex --src-specials %O %S'; + Running a subroutine instead of an external command: Use a specifica- + tion starting with "internal", as in + $latex = 'internal mylatex %O %S'; + sub mylatex { + my @args = @_; - 19 January 2017 24 + 20 November 2017 25 -LATEXMK(1) General Commands Manual LATEXMK(1) - $latex = 'latex --src-specials %O %S'; +LATEXMK(1) General Commands Manual LATEXMK(1) - Running a subroutine instead of an external command: Use a specifica- - tion starting with "internal", as in - $latex = 'internal mylatex %O %S'; - sub mylatex { - my @args = @_; # Possible preprocessing here return system 'latex', @args; } - For some of the more exotic possibilities that then become available, - see the section "ADVANCED CONFIGURATION: Some extra resources and - advanced tricks". Also see some of the examples in the directory exam- + For some of the more exotic possibilities that then become available, + see the section "ADVANCED CONFIGURATION: Some extra resources and + advanced tricks". Also see some of the examples in the directory exam- ple_rcfiles in the latexmk distribution. - Advanced tricks: Normally one specifies a single command for the com- - mands invoked by latexmk. Naturally, if there is some complicated + Advanced tricks: Normally one specifies a single command for the com- + mands invoked by latexmk. Naturally, if there is some complicated additional processing you need to do in your special situation, you can write a script (or batch file) to do the processing, and then configure latexmk to use your script in place of the standard program. - You can also use a Perl subroutine instead of a script -- see above. + You can also use a Perl subroutine instead of a script -- see above. This is generally the most flexible and portable solution. It is also possible to configure latexmk to run multiple commands. For - example, if when running pdflatex to generate a pdf file from a tex - file you need to run another program after pdflatex to perform some + example, if when running pdflatex to generate a pdf file from a tex + file you need to run another program after pdflatex to perform some extra processing, you could do something like: - $pdflatex = 'pdflatex --shell-escape %O %S; pst2pdf_for_latexmk + $pdflatex = 'pdflatex --shell-escape %O %S; pst2pdf_for_latexmk %B'; - This definition assumes you are using a UNIX-like system (which - includes Linux and OS-X), so that the two commands to be run are sepa- + This definition assumes you are using a UNIX-like system (which + includes Linux and OS-X), so that the two commands to be run are sepa- rated by the semicolon in the middle of the string. If you are using MS-Windows, you would replace the above line by @@ -1631,9 +1689,9 @@ LATEXMK(1) General Commands Manual LATEXMK(1) $pdflatex = 'cmd /c pdflatex --shell-escape %O %S' . '&& pst2pdf_for_latexmk %B'; - Here, the UNIX command separator ; is replaced by &&. In addition, + Here, the UNIX command separator ; is replaced by &&. In addition, there is a problem that some versions of Perl on MS-Windows do not obey - the command separator; this problem is overcome by explicitly invoking + the command separator; this problem is overcome by explicitly invoking the MS-Windows command-line processor cmd.exe. @@ -1642,83 +1700,104 @@ LIST OF CONFIGURATION VARIABLES USABLE IN INITIALIZATION FILES $always_view_file_via_temporary [0] Whether ps and pdf files are initially to be made in a temporary + directory and then moved to the final location. (This applies + to dvips, dvipdf, and ps2pdf operations, and the filtering oper- + ators on dvi and ps files. It does not apply to pdflatex, + unfortunately, since pdflatex provides no way of specifying a + chosen name for the output file.) + This use of a temporary file solves a problem that the making of + these files can occupy a substantial time. If a viewer (notably - 19 January 2017 25 + 20 November 2017 26 -LATEXMK(1) General Commands Manual LATEXMK(1) +LATEXMK(1) General Commands Manual LATEXMK(1) - directory and then moved to the final location. (This applies - to dvips, dvipdf, and ps2pdf operations, and the filtering oper- - ators on dvi and ps files. It does not apply to pdflatex, - unfortunately, since pdflatex provides no way of specifying a - chosen name for the output file.) - This use of a temporary file solves a problem that the making of - these files can occupy a substantial time. If a viewer (notably - gv) sees that the file has changed, it may read the new file - before the program writing the file has not yet finished its + gv) sees that the file has changed, it may read the new file + before the program writing the file has not yet finished its work, which can cause havoc. See the $pvc_view_file_via_temporary variable for a setting that - applies only if preview-continuous mode (-pvc option) is used. + applies only if preview-continuous mode (-pvc option) is used. See $tmpdir for the setting of the directory where the temporary file is created. + $analyze_input_log_always [1] + + After a run of latex (etc), always analyze .log for input files + in the <...> and (...) constructions. Otherwise, only do the + analysis when fls file doesn't exist or is out of date. + + Under normal circumstances, the data in the fls file is reli- + able, and the test of the log file gets lots of false positives; + usually $analyze_input_log_always is best set to zero. But the + test of the log file is needed at least in the following situa- + tion: When a user needs to persuade latexmk that a certain file + is a source file, and latexmk doesn't otherwise find it. Then + the user can write code that causes a line with (...) to be + written to log file. One important case is for lualatex, which + doesn't always generate lines in the .fls file for input lua + files. (The situation with lualatex is HIGHLY version depen- + dent, e.g., there was a big change between TeXLive 2016 and + TeXLive 2017.) + + To keep backward compatibility with older versions of latexmk, + the default is to set $analyze_input_log_always to 1. + + $auto_rc_use [1] - Whether to automatically read the standard initialization (rc) + Whether to automatically read the standard initialization (rc) files, which are the system RC file, the user's RC file, and the RC file in the current directory. The command line option -norc - can be used to turn this setting off. Each RC file could also - turn this setting off, i.e., it could set $auto_rc_use to zero + can be used to turn this setting off. Each RC file could also + turn this setting off, i.e., it could set $auto_rc_use to zero to prevent automatic reading of the later RC files. - This variable does not affect the reading of RC files specified + This variable does not affect the reading of RC files specified on the command line by the -r option. - $aux_dir [""] The directory in which auxiliary files (aux, log, etc) are to be - written by a run of (pdf)latex. If this variable is not set, - but $out_dir is set, then $aux_dir is set to $out_dir, which is + written by a run of (pdf)latex. If this variable is not set, + but $out_dir is set, then $aux_dir is set to $out_dir, which is the directory to which general output files are to be written. - Important note: The effect of $aux_dir, if different from - $out_dir, is achieved by giving (pdf)latex the -aux-directory. - Currently (Dec. 2011 and later) this only works on the MiKTeX + Important note: The effect of $aux_dir, if different from + $out_dir, is achieved by giving (pdf)latex the -aux-directory. + Currently (Dec. 2011 and later) this only works on the MiKTeX version of (pdf)latex. - See also the documentation of $out_dir for some complications on - what directory names are suitable. - If you also use the -cd option, and $out_dir (or $aux_dir) con- - tains a relative path, then the path is interpreted relative to - the document directory. - - $banner [0] - If nonzero, the banner message is printed across each page when - converting the dvi file to postscript. Without modifying the - variable $banner_message, this is equivalent to specifying the - -d option. + 20 November 2017 27 - 19 January 2017 26 +LATEXMK(1) General Commands Manual LATEXMK(1) + See also the documentation of $out_dir for some complications on + what directory names are suitable. -LATEXMK(1) General Commands Manual LATEXMK(1) + If you also use the -cd option, and $out_dir (or $aux_dir) con- + tains a relative path, then the path is interpreted relative to + the document directory. + $banner [0] + If nonzero, the banner message is printed across each page when + converting the dvi file to postscript. Without modifying the + variable $banner_message, this is equivalent to specifying the + -d option. Note that if $banner is nonzero, the $postscript_mode is assumed and the postscript file is always generated, even if it is newer @@ -1726,7 +1805,7 @@ LATEXMK(1) General Commands Manual LATEXMK(1) $banner_intensity [0.95] Equivalent to the -bi option, this is a decimal number between 0 - and 1 that specifies how dark to print the banner message. 0 is + and 1 that specifies how dark to print the banner message. 0 is black, 1 is white. The default is just right if your toner car- tridge isn't running too low. @@ -1735,19 +1814,19 @@ LATEXMK(1) General Commands Manual LATEXMK(1) dvi file to postscript. This is equivalent to the -bm option. $banner_scale [220.0] - A decimal number that specifies how large the banner message - will be printed. Experimentation is necessary to get the right - scale for your message, as a rule of thumb the scale should be - about equal to 1100 divided by the number of characters in the - message. The Default is just right for 5 character messages. + A decimal number that specifies how large the banner message + will be printed. Experimentation is necessary to get the right + scale for your message, as a rule of thumb the scale should be + about equal to 1100 divided by the number of characters in the + message. The Default is just right for 5 character messages. This is equivalent to the -bs option. @BIBINPUTS - This is an array variable, now mostly obsolete, that specifies - directories where latexmk should look for .bib files. By + This is an array variable, now mostly obsolete, that specifies + directories where latexmk should look for .bib files. By default it is set from the BIBINPUTS environment variable of the - operating system. If that environment variable is not set, a - single element list consisting of the current directory is set. + operating system. If that environment variable is not set, a + single element list consisting of the current directory is set. The format of the directory names depends on your operating sys- tem, of course. Examples for setting this variable are: @@ -1757,35 +1836,35 @@ LATEXMK(1) General Commands Manual LATEXMK(1) @BIBINPUTS = ( ".", "//server/bibfiles" ); @BIBINPUTS = ( ".", "/usr/local/texmf/bibtex/bib" ); - Note that under MS Windows, either a forward slash "/" or a - backward slash "\" can be used to separate pathname components, - so the first two and the second two examples are equivalent. - Each backward slash should be doubled to avoid running afoul of - Perl's rules for writing strings. + Note that under MS Windows, either a forward slash "/" or a + backward slash "\" can be used to separate pathname components, + so the first two and the second two examples are equivalent. + Each backward slash should be doubled to avoid running afoul of - Important note: This variable is now mostly obsolete in the cur- - rent version of latexmk, since it has a better method of search- - ing for files using the kpsewhich command. However, if your - system is an unusual one without the kpsewhich command, you may - need to set the variable @BIBINPUTS. - $biber ["biber %O %S"] - The biber processing program. - $biber_silent_switch ["--onlylog"] - Switch(es) for the biber processing program when silent mode is + 20 November 2017 28 - 19 January 2017 27 +LATEXMK(1) General Commands Manual LATEXMK(1) + Perl's rules for writing strings. -LATEXMK(1) General Commands Manual LATEXMK(1) + Important note: This variable is now mostly obsolete in the cur- + rent version of latexmk, since it has a better method of search- + ing for files using the kpsewhich command. However, if your + system is an unusual one without the kpsewhich command, you may + need to set the variable @BIBINPUTS. + $biber ["biber %O %S"] + The biber processing program. + $biber_silent_switch ["--onlylog"] + Switch(es) for the biber processing program when silent mode is on. $bibtex ["bibtex %O %S"] @@ -1797,60 +1876,70 @@ LATEXMK(1) General Commands Manual LATEXMK(1) $bibtex_use [1] Under what conditions to run bibtex or biber. When latexmk dis- - covers from the log file that one (or more) bibtex/biber-gener- - ated bibliographies are used, it can run bibtex or biber when- - ever it appears necessary to regenerate the bbl file(s) from - their source bib database file(s). - - But sometimes, the bib file(s) are not available (e.g., for a - document obtained from an external archive), but the bbl files - are provided. In that case use of bibtex or biber will result - in incorrect overwriting of the precious bbl files. The vari- - able $bibtex_use controls whether this happens. Its possible - values are: 0: never use BibTeX or biber. 1: only use bibtex or - biber if the bib files exist. 2: run bibtex or biber whenever - it appears necessary to update the bbl files, without testing - for the existence of the bib files. + covers from the log file that one (or more) bibtex/biber-gener- + ated bibliographies are used, it can run bibtex or biber when- + ever it appears necessary to regenerate the bbl file(s) from + their source bib database file(s). But sometimes, the bib + file(s) are not available (e.g., for a document obtained from an + external archive), but the bbl files are provided. In that case + use of bibtex or biber will result in incorrect overwriting of + the precious bbl files. The variable $bibtex_use controls + whether this happens, and also controls whether or not .bbl + files are deleted in a cleanup operation. + + The possible values of $bibtex_use are: + 0: never use BibTeX or biber; never delete .bbl files in a + cleanup. + 1: only use bibtex or biber if the bib files exist; never + delete .bbl files in a cleanup. + 1.5: only use bibtex or biber if the bib files exist; condi- + tionally delete .bbl files in a cleanup (i.e., delete them only + when the bib files all exist). + 2: run bibtex or biber whenever it appears necessary to update + the bbl files, without testing for the existence of the bib + files; always delete .bbl files in a cleanup. + $cleanup_includes_cusdep_generated [0] - If nonzero, specifies that cleanup also deletes files that are + If nonzero, specifies that cleanup also deletes files that are generated by custom dependencies. (When doing a clean up, e.g., by use of the -C option, custom dependencies are those listed in the .fdb_latexmk file from a previous run.) - $cleanup_includes_generated [0] - If nonzero, specifies that cleanup also deletes files that are - detected in log file as being generated (see the \openout lines - in the log file). It will also include files made from these - first generation generated files. - $cleanup_mode [0] - If nonzero, specifies cleanup mode: 1 for full cleanup, 2 for - cleanup except for dvi, ps and pdf files, 3 for cleanup except - for dep and aux files. (There is also extra cleaning as speci- - fied by the $clean_ext, $clean_full_ext and @generated_exts - variables.) - This variable is equivalent to specifying one of the -c or -C - options. But there should be no need to set this variable from - an RC file. - $clean_ext [""] - Extra extensions of files for latexmk to remove when any of the - clean-up options (-c or -C) is selected. The value of this - variable is a string containing the extensions separated by spa- - ces. + 20 November 2017 29 - 19 January 2017 28 +LATEXMK(1) General Commands Manual LATEXMK(1) + $cleanup_includes_generated [0] + If nonzero, specifies that cleanup also deletes files that are + detected in log file as being generated (see the \openout lines + in the log file). It will also include files made from these + first generation generated files. -LATEXMK(1) General Commands Manual LATEXMK(1) + $cleanup_mode [0] + If nonzero, specifies cleanup mode: 1 for full cleanup, 2 for + cleanup except for dvi, ps and pdf files, 3 for cleanup except + for dep and aux files. (There is also extra cleaning as speci- + fied by the $clean_ext, $clean_full_ext and @generated_exts + variables.) + This variable is equivalent to specifying one of the -c or -C + options. But there should be no need to set this variable from + an RC file. + + $clean_ext [""] + Extra extensions of files for latexmk to remove when any of the + clean-up options (-c or -C) is selected. The value of this + variable is a string containing the extensions separated by spa- + ces. It is also possible to specify a more general pattern of file to be deleted, by using the place holder %R, as in commands, and it @@ -1859,88 +1948,85 @@ LATEXMK(1) General Commands Manual LATEXMK(1) $clean_ext = "out %R-blx.bib %R-figures*.log"; in an initialization file will imply that when a clean-up opera- - tion is specified, not only is the standard set of files - deleted, but also files of the form FOO.out, FOO-blx.bib, and - %R-figures*.log, where FOO stands for the basename of the file + tion is specified, not only is the standard set of files + deleted, but also files of the form FOO.out, FOO-blx.bib, and + %R-figures*.log, where FOO stands for the basename of the file being processed (as in FOO.tex). - $clean_full_ext [""] - Extra extensions of files for latexmk to remove when the -C + Extra extensions of files for latexmk to remove when the -C option is selected, i.e., extensions of files to remove when the .dvi, etc files are to be cleaned-up. More general patterns are allowed, as for $clean_ext. - - $compiling_cmd [undefined], $failure_cmd [undefined], $success_cmd + $compiling_cmd [undefined], $failure_cmd [undefined], $success_cmd [undefined] - These variables specify commands that are executed at certain - points of compilations during preview-continuous mode. One - motivation for their existance is to allow convenient visual + These variables specify commands that are executed at certain + points of compilations during preview-continuous mode. One + motivation for their existance is to allow convenient visual indications of compilation status even when the window receiving the screen output of the compilation is hidden. - The commands are executed at the following points: $compil- - ing_cmd at the start of compilation, $success_cmd at the end of - a successful compilation, and $failure_cmd at the end of an - unsuccessful compilation. If any of above variables is unde- - fined (the default situation) or blank, then the corresponding - command is not executed. + The commands are executed at the following points: $compil- + ing_cmd at the start of compilation, $success_cmd at the end of + a successful compilation, and $failure_cmd at the end of an - An example of a typical setting of these variables is as follows - $compiling_cmd = "xdotool search --name \"%D\" set_window - --name \"%D compiling\""; - $success_cmd = "xdotool search --name \"%D\" set_window - --name \"%D OK\""; - $failure_cmd = "xdotool search --name \"%D\" set_window - --name \"%D FAILURE\""; - These assume that the program xdotool is installed, that the - previewer is using an X-Window system for display, and that the - title of the window contains the name of the displayed file, as - it normally does. When the commands are executed, the place- - holder string %D is replaced by the name of the destination - file, which is the previewed file. The above commands result in - an appropriate string being appended to the filename in the win- - dow title: " compiling", " OK", or " FAILURE". + 20 November 2017 30 - 19 January 2017 29 +LATEXMK(1) General Commands Manual LATEXMK(1) + unsuccessful compilation. If any of above variables is unde- + fined (the default situation) or blank, then the corresponding + command is not executed. -LATEXMK(1) General Commands Manual LATEXMK(1) + An example of a typical setting of these variables is as follows + $compiling_cmd = "xdotool search --name \"%D\" set_window + --name \"%D compiling\""; + $success_cmd = "xdotool search --name \"%D\" set_window + --name \"%D OK\""; + $failure_cmd = "xdotool search --name \"%D\" set_window + --name \"%D FAILURE\""; - Other placeholders that can be used are %S, %T, and %R, with %S - and %T normally being identical. These can be useful for a com- - mand changing the title of the edit window. The visual indica- - tion in a window title can useful, since the user does not have - to keep shifting attention to the (possibly hidden) compilation - window to know the status of the compilation. + These assume that the program xdotool is installed, that the + previewer is using an X-Window system for display, and that the + title of the window contains the name of the displayed file, as + it normally does. When the commands are executed, the place- + holder string %D is replaced by the name of the destination + file, which is the previewed file. The above commands result in + an appropriate string being appended to the filename in the win- + dow title: " compiling", " OK", or " FAILURE". + Other placeholders that can be used are %S, %T, and %R, with %S + and %T normally being identical. These can be useful for a com- + mand changing the title of the edit window. The visual indica- + tion in a window title can useful, since the user does not have + to keep shifting attention to the (possibly hidden) compilation + window to know the status of the compilation. @cus_dep_list [()] Custom dependency list -- see section on "Custom Dependencies". - @default_excluded_files [()] - When latexmk is invoked with no files specified on the command + When latexmk is invoked with no files specified on the command line, then, by default, it will process all files in the current directory with the extension .tex. (In general, it will process the files specified in the @default_files variable.) - But sometimes you want to exclude particular files from this - default list. In that case you can specify the excluded files + But sometimes you want to exclude particular files from this + default list. In that case you can specify the excluded files in the array @default_excluded_files. For example if you wanted - to process all .tex files with the exception of common.tex, - which is a not a standard alone LaTeX file but a file input by + to process all .tex files with the exception of common.tex, + which is a not a standard alone LaTeX file but a file input by some or all of the others, you could do @default_files = ("*.tex"); @@ -1948,41 +2034,40 @@ LATEXMK(1) General Commands Manual LATEXMK(1) @default_excluded_files = ("common.tex"); If you have a variable or large number of files to be processed, - this method saves you from having to list them in detail in - @default_files and having to update the list every time you + this method saves you from having to list them in detail in + @default_files and having to update the list every time you change the set of files to be processed. - Notes: 1. This variable has no effect except when no files are - specified on the latexmk command line. 2. Wildcards are allowed - in @default_excluded_files. - @default_files [("*.tex")] - Default list of files to be processed. - - If no filenames are specified on the command line, latexmk pro- - cesses all tex files specified in the @default_files variable, - which by default is set to all tex files ("*.tex") in the cur- - rent directory. This is a convenience: just run latexmk and it - will process an appropriate set of files. But sometimes you - want only some of these files to be processed. In this case you - can list the files to be processed by setting @default_files in - an initialization file (e.g., the file "latexmkrc" in the cur- - rent directory). Then if no files are specified on the command - line then the files you specify by setting @default_files are - processed. + 20 November 2017 31 - 19 January 2017 30 +LATEXMK(1) General Commands Manual LATEXMK(1) + Notes: 1. This variable has no effect except when no files are + specified on the latexmk command line. 2. Wildcards are allowed + in @default_excluded_files. -LATEXMK(1) General Commands Manual LATEXMK(1) + @default_files [("*.tex")] + Default list of files to be processed. + If no filenames are specified on the command line, latexmk pro- + cesses all tex files specified in the @default_files variable, + which by default is set to all tex files ("*.tex") in the cur- + rent directory. This is a convenience: just run latexmk and it + will process an appropriate set of files. But sometimes you + want only some of these files to be processed. In this case you + can list the files to be processed by setting @default_files in + an initialization file (e.g., the file "latexmkrc" in the cur- + rent directory). Then if no files are specified on the command + line then the files you specify by setting @default_files are + processed. Three examples: @@ -1992,406 +2077,398 @@ LATEXMK(1) General Commands Manual LATEXMK(1) @default_files = ("*.tex", "*.dtx"); - Note that more than file may be given, and that the default - extension is ".tex". Wild cards are allowed. The parentheses + Note that more than file may be given, and that the default + extension is ".tex". Wild cards are allowed. The parentheses are because @default_files is an array variable, i.e., a sequence of filename specifications is possible. - If you want latexmk to process all .tex files with a few excep- + If you want latexmk to process all .tex files with a few excep- tions, see the @default_excluded_files array variable. - $dependents_phony [0] - If a list of dependencies is output, this variable determines - whether to include a phony target for each source file. If you - use the dependents list in a Makefile, the dummy rules work - around errors make gives if you remove header files without + If a list of dependencies is output, this variable determines + whether to include a phony target for each source file. If you + use the dependents list in a Makefile, the dummy rules work + around errors make gives if you remove header files without updating the Makefile to match. $dependents_list [0] - Whether to display a list(s) of dependencies at the end of a + Whether to display a list(s) of dependencies at the end of a run. $deps_file ["-"] - Name of file to receive list(s) of dependencies at the end of a - run, to be used if $dependesnt_list is set. If the filename is - "-", then the dependency list is set to stdout (i.e., normally + Name of file to receive list(s) of dependencies at the end of a + run, to be used if $dependesnt_list is set. If the filename is + "-", then the dependency list is set to stdout (i.e., normally the screen). $do_cd [0] - Whether to change working directory to the directory specified - for the main source file before processing it. The default - behavior is not to do this, which is the same as the behavior of - latex and pdflatex programs. This variable is set by the -cd - and -cd- options on latexmk's command line. + Whether to change working directory to the directory specified - $dvi_filter [empty] - The dvi file filter to be run on the newly produced dvi file - before other processing. Equivalent to specifying the -dF - option. - $dvi_mode [See below for default] - If nonzero, generate a dvi version of the document. Equivalent - to the -dvi option. - The variable $dvi_mode defaults to 0, but if no explicit - requests are made for other types of file (postscript, pdf), - then $dvi_mode will be set to 1. In addition, if a request for - a file for which a .dvi file is a prerequisite, then $dvi_mode + 20 November 2017 32 - 19 January 2017 31 +LATEXMK(1) General Commands Manual LATEXMK(1) + for the main source file before processing it. The default + behavior is not to do this, which is the same as the behavior of + latex and pdflatex programs. This variable is set by the -cd + and -cd- options on latexmk's command line. -LATEXMK(1) General Commands Manual LATEXMK(1) + $dvi_filter [empty] + The dvi file filter to be run on the newly produced dvi file + before other processing. Equivalent to specifying the -dF + option. + $dvi_mode [See below for default] + If nonzero, generate a dvi version of the document. Equivalent + to the -dvi option. + The variable $dvi_mode defaults to 0, but if no explicit + requests are made for other types of file (postscript, pdf), + then $dvi_mode will be set to 1. In addition, if a request for + a file for which a .dvi file is a prerequisite, then $dvi_mode will be set to 1. $dvi_previewer ["start xdvi %O %S" under UNIX] - The command to invoke a dvi-previewer. [Under MS-Windows the - default is "start"; then latexmk arranges to use the MS-Windows - start program, which will cause to be run whatever command the + The command to invoke a dvi-previewer. [Under MS-Windows the + default is "start"; then latexmk arranges to use the MS-Windows + start program, which will cause to be run whatever command the system has associated with .dvi files.] - Important note: Normally you will want to have a previewer run + Important note: Normally you will want to have a previewer run detached, so that latexmk doesn't wait for the previewer to ter- - minate before continuing its work. So normally you should pre- - fix the command by "start ", which flags to latexmk that it - should do the detaching of the previewer itself (by whatever - method is appropriate to the operating system). But sometimes + minate before continuing its work. So normally you should pre- + fix the command by "start ", which flags to latexmk that it + should do the detaching of the previewer itself (by whatever + method is appropriate to the operating system). But sometimes letting latexmk do the detaching is not appropriate (for a vari- - ety of non-trivial reasons), so you should put the "start " bit + ety of non-trivial reasons), so you should put the "start " bit in yourself, whenever it is needed. - $dvi_previewer_landscape ["start xdvi %O %S"] The command to invoke a dvi-previewer in landscape mode. [Under - MS-Windows the default is "start"; then latexmk arranges to use - the MS-Windows start program, which will cause to be run what- + MS-Windows the default is "start"; then latexmk arranges to use + the MS-Windows start program, which will cause to be run what- ever command the system has associated with .dvi files.] - $dvipdf ["dvipdf %O %S %D"] Command to convert dvi to pdf file. A common reconfiguration is - to use the dvipdfm command, which needs its arguments in a dif- + to use the dvipdfm command, which needs its arguments in a dif- ferent order: $dvipdf = "dvipdfm %O -o %D %S"; - WARNING: The default dvipdf script generates pdf files with + WARNING: The default dvipdf script generates pdf files with bitmapped fonts, which do not look good when viewed by acroread. - That script should be modified to give dvips the options "-P + That script should be modified to give dvips the options "-P pdf" to ensure that type 1 fonts are used in the pdf file. - $dvipdf_silent_switch ["-q"] - Switch(es) for dvipdf program when silent mode is on. - N.B. The standard dvipdf program runs silently, so adding the - silent switch has no effect, but is actually innocuous. But if - an alternative program is used, e.g., dvipdfmx, then the silent - switch has an effect. The default setting is correct for - dvipdfm and dvipdfmx. - - $dvips ["dvips %O -o %D %S"] - The program to used as a filter to convert a .dvi file to a .ps - file. If pdf is going to be generated from pdf, then the value - of the $dvips_pdf_switch variable -- see below -- will be - included in the options substituted for "%O". + 20 November 2017 33 - 19 January 2017 32 +LATEXMK(1) General Commands Manual LATEXMK(1) + $dvipdf_silent_switch ["-q"] + Switch(es) for dvipdf program when silent mode is on. -LATEXMK(1) General Commands Manual LATEXMK(1) + N.B. The standard dvipdf program runs silently, so adding the + silent switch has no effect, but is actually innocuous. But if + an alternative program is used, e.g., dvipdfmx, then the silent + switch has an effect. The default setting is correct for + dvipdfm and dvipdfmx. + $dvips ["dvips %O -o %D %S"] + The program to used as a filter to convert a .dvi file to a .ps + file. If pdf is going to be generated from pdf, then the value + of the $dvips_pdf_switch variable -- see below -- will be + included in the options substituted for "%O". $dvips_landscape ["dvips -tlandscape %O -o %D %S"] - The program to used as a filter to convert a .dvi file to a .ps + The program to used as a filter to convert a .dvi file to a .ps file in landscape mode. $dvips_pdf_switch ["-P pdf"] - Switch(es) for dvips program when pdf file is to be generated + Switch(es) for dvips program when pdf file is to be generated from ps file. $dvips_silent_switch ["-q"] Switch(es) for dvips program when silent mode is on. $dvi_update_command [""] - When the dvi previewer is set to be updated by running a com- - mand, this is the command that is run. See the information for + When the dvi previewer is set to be updated by running a com- + mand, this is the command that is run. See the information for the variable $dvi_update_method for further information, and see - information on the variable $pdf_update_method for an example + information on the variable $pdf_update_method for an example for the analogous case of a pdf previewer. $dvi_update_method [2 under UNIX, 1 under MS-Windows] - How the dvi viewer updates its display when the dvi file has - changed. The values here apply equally to the + How the dvi viewer updates its display when the dvi file has + changed. The values here apply equally to the $pdf_update_method and to the $ps_update_method variables. 0 => update is automatic, 1=> manual update by user, which may only mean a mouse click on the viewer's window or may mean a more serious action. - 2 => Send the signal, whose number is in the variable - $dvi_update_signal. The default value under UNIX is suitable + 2 => Send the signal, whose number is in the variable + $dvi_update_signal. The default value under UNIX is suitable for xdvi. - 3 => Viewer cannot do an update, because it locks the file. + 3 => Viewer cannot do an update, because it locks the file. (As with acroread under MS-Windows.) - 4 => run a command to do the update. The command is speci- + 4 => run a command to do the update. The command is speci- fied by the variable $dvi_update_command. - See information on the variable $pdf_update_method for an exam- + See information on the variable $pdf_update_method for an exam- ple of updating by command. - $dvi_update_signal [Under UNIX: SIGUSR1, which is a system-dependent + $dvi_update_signal [Under UNIX: SIGUSR1, which is a system-dependent value] - The number of the signal that is sent to the dvi viewer when it - is updated by sending a signal -- see the information on the - variable $dvi_update_method. The default value is the one - appropriate for xdvi on a UNIX system. + The number of the signal that is sent to the dvi viewer when it - $failure_cmd [undefined] - See the documentation for $compiling_cmd. - $fdb_ext ["fdb_latexmk"] - The extension of the file which latexmk generates to contain a - database of information on source files. You will not normally - need to change this. - $force_mode [0] - If nonzero, continue processing past minor latex errors includ- - ing unrecognized cross references. Equivalent to specifying the + 20 November 2017 34 - 19 January 2017 33 +LATEXMK(1) General Commands Manual LATEXMK(1) + is updated by sending a signal -- see the information on the + variable $dvi_update_method. The default value is the one + appropriate for xdvi on a UNIX system. -LATEXMK(1) General Commands Manual LATEXMK(1) + $failure_cmd [undefined] + See the documentation for $compiling_cmd. + $fdb_ext ["fdb_latexmk"] + The extension of the file which latexmk generates to contain a + database of information on source files. You will not normally + need to change this. + $force_mode [0] + If nonzero, continue processing past minor latex errors includ- + ing unrecognized cross references. Equivalent to specifying the -f option. - @generated_exts [( aux , bbl , idx , ind , lof , lot , out , toc , + @generated_exts [( aux , bbl , idx , ind , lof , lot , out , toc , $fdb_ext )] - This contains a list of extensions for files that are generated - during a LaTeX run and that are read in by LaTeX in later runs, + This contains a list of extensions for files that are generated + during a LaTeX run and that are read in by LaTeX in later runs, either directly or indirectly. - This list has two uses: (a) to set the kinds of file to be + This list has two uses: (a) to set the kinds of file to be deleted in a cleanup operation (with the -c, -C, -CA, -g and -gg - options), and (b) in the determination of whether a rerun of + options), and (b) in the determination of whether a rerun of (pdf)LaTeX is needed after a run that gives an error. (Normally, a change of a source file during a run should provoke - a rerun. This includes a file generated by LaTeX, e.g., an aux - file, that is read in on subsequent runs. But after a run that - results in an error, a new run should occur until the user has - made a change in the files. But the user may have corrected an + a rerun. This includes a file generated by LaTeX, e.g., an aux + file, that is read in on subsequent runs. But after a run that + results in an error, a new run should occur until the user has + made a change in the files. But the user may have corrected an error in a source .tex file during the run. So latexmk needs to distinguish user-generated and automatically generated files; it - determines the automatically generated files as those with + determines the automatically generated files as those with extensions in the list in @generated_exts.) - A convenient way to add an extra extension to the list, without - losing the already defined ones is to use a push command in the + A convenient way to add an extra extension to the list, without + losing the already defined ones is to use a push command in the line in an RC file. E.g., push @generated_exts, "end"; - adds the extension "end" to the list of predefined generated - extensions. (This extension is used by the RevTeX package, for + adds the extension "end" to the list of predefined generated + extensions. (This extension is used by the RevTeX package, for example.) $go_mode [0] - If nonzero, process files regardless of timestamps, and is then + If nonzero, process files regardless of timestamps, and is then equivalent to the -g option. %hash_calc_ignore_pattern !!!This variable is for experts only!!! - The general rule latexmk uses for determining when an extra run - of some program is needed is that one of the source files has - changed. But consider for example a latex package that causes - an encapsulated postscript file (an "eps" file) to be made that - is to be read in on the next run. The file contains a comment - line giving its creation date and time. On the next run the - time changes, latex sees that the eps file has changed, and - therefore reruns latex. This causes an infinite loop, that is - only terminated because latexmk has a limit on the number of - runs to guard against pathological situations. - - But the changing line has no real effect, since it is a comment. - You can instruct latex to ignore the offending line as follows: + 20 November 2017 35 - 19 January 2017 34 +LATEXMK(1) General Commands Manual LATEXMK(1) -LATEXMK(1) General Commands Manual LATEXMK(1) + The general rule latexmk uses for determining when an extra run + of some program is needed is that one of the source files has + changed. But consider for example a latex package that causes + an encapsulated postscript file (an "eps" file) to be made that + is to be read in on the next run. The file contains a comment + line giving its creation date and time. On the next run the + time changes, latex sees that the eps file has changed, and + therefore reruns latex. This causes an infinite loop, that is + only terminated because latexmk has a limit on the number of + runs to guard against pathological situations. + But the changing line has no real effect, since it is a comment. + You can instruct latex to ignore the offending line as follows: $hash_calc_ignore_pattern{'eps'} = '^%%CreationDate: '; This creates a rule for files with extension .eps about lines to - ignore. The left-hand side is a Perl idiom for setting an item - in a hash. Note that the file extension is specified without a + ignore. The left-hand side is a Perl idiom for setting an item + in a hash. Note that the file extension is specified without a period. The value, on the right-hand side, is a string contain- - ing a regular expresssion. (See documentation on Perl for how - they are to be specified in general.) This particular regular - expression specifies that lines beginning with "%%CreationDate: - " are to be ignored in deciding whether a file of the given + ing a regular expresssion. (See documentation on Perl for how + they are to be specified in general.) This particular regular + expression specifies that lines beginning with "%%CreationDate: + " are to be ignored in deciding whether a file of the given extension .eps has changed. - There is only one regular expression available for each exten- - sion. If you need more one pattern to specify lines to ignore, - then you need to combine the patterns into a single regular - expression. The simplest method is separate the different sim- - ple patterns by a vertical bar character (indicating "alterna- + There is only one regular expression available for each exten- + sion. If you need more one pattern to specify lines to ignore, + then you need to combine the patterns into a single regular + expression. The simplest method is separate the different sim- + ple patterns by a vertical bar character (indicating "alterna- tion" in the jargon of regular expressions). For example, - $hash_calc_ignore_pattern{'eps'} = '^%%CreationDate: + $hash_calc_ignore_pattern{'eps'} = '^%%CreationDate: |^%%Title: '; - causes lines starting with either "^%%CreationDate: " or + causes lines starting with either "^%%CreationDate: " or "^%%Title: " to be ignored. - It may happen that a pattern to be ignored is specified in, for - example, in a system or user initialization file, and you wish - to remove this in a file that is read later. To do this, you + It may happen that a pattern to be ignored is specified in, for + example, in a system or user initialization file, and you wish + to remove this in a file that is read later. To do this, you use Perl's delete function, e.g., delete $hash_calc_ignore_pattern{'eps'}; $kpsewhich ["kpsewhich %S"] - The program called to locate a source file when the name alone - is not sufficient. Most filenames used by latexmk have suffi- - cient path information to be found directly. But sometimes, + The program called to locate a source file when the name alone + is not sufficient. Most filenames used by latexmk have suffi- + cient path information to be found directly. But sometimes, notably when a .bib or a .bst file is found from the log file of - a bibtex or biber run, only the base name of the file is known, + a bibtex or biber run, only the base name of the file is known, but not its path. The program specified by $kpsewhich is used to - find it. - (For advanced users: Because of the different way in which - latexmk uses the command specified in $kpsewhich, some of the - possibilities listed in the FORMAT OF COMMAND SPECIFICATIONS do - not apply. The internal and start keywords are not available. A - simple command specification with possible options and then "%S" - is all that is guaranteed to work. Note that for other com- - mands, "%S" is substituted by a single source file. In contrast, - for $kpsewhich, "%S" may be substituted by a long list of space- - separated filenames, each of which is quoted. The result on - STDOUT of running the command is then piped to latexmk.) - See also the @BIBINPUTS variable for another way that latexmk + 20 November 2017 36 - 19 January 2017 35 +LATEXMK(1) General Commands Manual LATEXMK(1) -LATEXMK(1) General Commands Manual LATEXMK(1) + find it. + (For advanced users: Because of the different way in which + latexmk uses the command specified in $kpsewhich, some of the + possibilities listed in the FORMAT OF COMMAND SPECIFICATIONS do + not apply. The internal and start keywords are not available. A + simple command specification with possible options and then "%S" + is all that is guaranteed to work. Note that for other com- + mands, "%S" is substituted by a single source file. In contrast, + for $kpsewhich, "%S" may be substituted by a long list of space- + separated filenames, each of which is quoted. The result on + STDOUT of running the command is then piped to latexmk.) + See also the @BIBINPUTS variable for another way that latexmk also uses to try to locate files; it applies only in the case of .bib files. - $kpsewhich_show [0] - Whether to show diagnostics about invocations of kpsewhich: the - command line use to invoke it and the results. These diagnos- - tics are shown if $kpsewhich_show is non-zero or if diagnostics - mode is on. (But in the second case, lots of other diagnostics - are also shown.) Without these diagnostics there is nothing - visible in latexmk's screen output about invocations of kpse- + Whether to show diagnostics about invocations of kpsewhich: the + command line use to invoke it and the results. These diagnos- + tics are shown if $kpsewhich_show is non-zero or if diagnostics + mode is on. (But in the second case, lots of other diagnostics + are also shown.) Without these diagnostics there is nothing + visible in latexmk's screen output about invocations of kpse- which. - $landscape_mode [0] If nonzero, run in landscape mode, using the landscape mode pre- - viewers and dvi to postscript converters. Equivalent to the -l + viewers and dvi to postscript converters. Equivalent to the -l option. Normally not needed with current previewers. $latex ["latex %O %S"] The LaTeX processing program. Note that as with other programs, - you can use this variable not just to change the name of the + you can use this variable not just to change the name of the program used, but also specify options to the program. E.g., $latex = "latex --src-specials"; %latex_input_extensions - This variable specifies the extensions tried by latexmk when it - finds that a LaTeX run resulted in an error that a file has not - been found, and the file is given without an extension. This - typically happens when LaTeX commands of the form \input{file} - or \includegraphics{figure}, when the relevant source file does + This variable specifies the extensions tried by latexmk when it + finds that a LaTeX run resulted in an error that a file has not + been found, and the file is given without an extension. This + typically happens when LaTeX commands of the form \input{file} + or \includegraphics{figure}, when the relevant source file does not exist. - In this situation, latexmk searches for custom dependencies to - make the missing file(s), but restricts it to the extensions - specified by the variable %latex_input_extensions. The default + In this situation, latexmk searches for custom dependencies to + make the missing file(s), but restricts it to the extensions + specified by the variable %latex_input_extensions. The default extensions are 'tex' and 'eps'. - (For Perl experts: %latex_input_extensions is a hash whose keys - are the extensions. The values are irrelevant.) Two subrou- - tines are provided for manipulating this and the related vari- - able %pdflatex_input_extensions, add_input_ext and - remove_input_ext. They are used as in the following examples - are possible lines in an initialization file: - - remove_input_ext( 'latex', 'tex' ); + (For Perl experts: %latex_input_extensions is a hash whose keys + are the extensions. The values are irrelevant.) Two subrou- + tines are provided for manipulating this and the related - removes the extension 'tex' from latex_input_extensions - add_input_ext( 'latex', 'asdf' ); - add the extension 'asdf to latex_input_extensions. (Naturally - with such an extension, you should have made an appropriate + 20 November 2017 37 - 19 January 2017 36 +LATEXMK(1) General Commands Manual LATEXMK(1) + variable %pdflatex_input_extensions, add_input_ext and + remove_input_ext. They are used as in the following examples + are possible lines in an initialization file: -LATEXMK(1) General Commands Manual LATEXMK(1) + remove_input_ext( 'latex', 'tex' ); + removes the extension 'tex' from latex_input_extensions - custom dependency for latexmk, and should also have done the - appropriate programming in the LaTeX source file to enable the - file to be read. The standard extensions are handled by LaTeX - and its graphics/graphicx packages. + add_input_ext( 'latex', 'asdf' ); + add the extension 'asdf to latex_input_extensions. (Naturally + with such an extension, you should have made an appropriate cus- + tom dependency for latexmk, and should also have done the appro- + priate programming in the LaTeX source file to enable the file + to be read. The standard extensions are handled by LaTeX and + its graphics/graphicx packages. $latex_silent_switch ["-interaction=batchmode"] - Switch(es) for the LaTeX processing program when silent mode is + Switch(es) for the LaTeX processing program when silent mode is on. - If you use MikTeX, you may prefer the results if you configure - the options to include -c-style-errors, e.g., by the following + If you use MikTeX, you may prefer the results if you configure + the options to include -c-style-errors, e.g., by the following line in an initialization file $latex_silent_switch = "-interaction=batchmode -c-style- @@ -2401,19 +2478,19 @@ LATEXMK(1) General Commands Manual LATEXMK(1) $lpr ["lpr %O %S" under UNIX/Linux, "NONE lpr" under MS-Windows] The command to print postscript files. - Under MS-Windows (unlike UNIX/Linux), there is no standard pro- + Under MS-Windows (unlike UNIX/Linux), there is no standard pro- gram for printing files. But there are ways you can do it. For example, if you have gsview installed, you could use it with the option "/p": $lpr = '"c:/Program Files/Ghostgum/gsview/gsview32.exe" /p'; - If gsview is installed in a different directory, you will need - to make the appropriate change. Note the combination of single - and double quotes around the name. The single quotes specify - that this is a string to be assigned to the configuration vari- - able $lpr. The double quotes are part of the string passed to - the operating system to get the command obeyed; this is neces- + If gsview is installed in a different directory, you will need + to make the appropriate change. Note the combination of single + and double quotes around the name. The single quotes specify + that this is a string to be assigned to the configuration vari- + able $lpr. The double quotes are part of the string passed to + the operating system to get the command obeyed; this is neces- sary because one part of the command name ("Program Files") con- tains a space which would otherwise be misinterpreted. @@ -2423,87 +2500,76 @@ LATEXMK(1) General Commands Manual LATEXMK(1) $lpr_pdf ["NONE lpr_pdf"] The printing program to print pdf files. - Under MS-Windows you could set this to use gsview, if it is - installed, e.g., - $lpr = '"c:/Program Files/Ghostgum/gsview/gsview32.exe" /p'; - If gsview is installed in a different directory, you will need - to make the appropriate change. Note the double quotes around - the name: this is necessary because one part of the command name - ("Program Files") contains a space which would otherwise be mis- - interpreted. + 20 November 2017 38 - 19 January 2017 37 +LATEXMK(1) General Commands Manual LATEXMK(1) + Under MS-Windows you could set this to use gsview, if it is + installed, e.g., -LATEXMK(1) General Commands Manual LATEXMK(1) + $lpr = '"c:/Program Files/Ghostgum/gsview/gsview32.exe" /p'; + If gsview is installed in a different directory, you will need + to make the appropriate change. Note the double quotes around + the name: this is necessary because one part of the command name + ("Program Files") contains a space which would otherwise be mis- + interpreted. $lualatex ["lualatex %O %S"] - The LaTeX processing program that is to be used when the luala- + The LaTeX processing program that is to be used when the luala- tex program is called for (e.g., by the option -lualatex. - %lualatex_input_extensions - This variable specifies the extensions tried by latexmk when it - finds that a lualatex run resulted in an error that a file has - not been found, and the file is given without an extension. - This typically happens when LaTeX commands of the form + This variable specifies the extensions tried by latexmk when it + finds that a lualatex run resulted in an error that a file has + not been found, and the file is given without an extension. + This typically happens when LaTeX commands of the form \input{file} or \includegraphics{figure}, when the relevant source file does not exist. - In this situation, latexmk searches for custom dependencies to - make the missing file(s), but restricts it to the extensions - specified by the variable %pdflatex_input_extensions. The + In this situation, latexmk searches for custom dependencies to + make the missing file(s), but restricts it to the extensions + specified by the variable %pdflatex_input_extensions. The default extensions are 'tex', 'pdf', 'jpg, and 'png'. See details of the %latex_input_extensions for other information that equally applies to %lualatex_input_extensions. - $lualatex_silent_switch ["-interaction=batchmode"] - Switch(es) for the lualatex program (specified in the variable + Switch(es) for the lualatex program (specified in the variable $lualatex) when silent mode is on. - See details of the $latex_silent_switch for other information + See details of the $latex_silent_switch for other information that equally applies to $lualatex_silent_switch. - $make ["make"] The make processing program. - $makeindex ["makeindex %O -o %D %S"] The index processing program. $makeindex_silent_switch ["-q"] - Switch(es) for the index processing program when silent mode is + Switch(es) for the index processing program when silent mode is on. $max_repeat [5] - The maximum number of times latexmk will run latex/pdflatex - before deciding that there may be an infinite loop and that it + The maximum number of times latexmk will run latex/pdflatex + before deciding that there may be an infinite loop and that it needs to bail out, rather than rerunning latex/pdflatex again to - resolve cross-references, etc. The default value covers all + resolve cross-references, etc. The default value covers all normal cases. - (Note that the "etc" covers a lot of cases where one run of - latex/pdflatex generates files to be read in on a later run.) - - $MSWin_back_slash [1] - This configuration variable only has an effect when latexmk is - running under MS-Windows. It determines whether, when a command - - 19 January 2017 38 + 20 November 2017 39 @@ -2512,64 +2578,64 @@ LATEXMK(1) General Commands Manual LATEXMK(1) LATEXMK(1) General Commands Manual LATEXMK(1) - is executed under MS-Windows, there should be substituted "\" - for the separator character between components of a directory - name. Internally, latexmk uses "/" for the directory separator + (Note that the "etc" covers a lot of cases where one run of + latex/pdflatex generates files to be read in on a later run.) + + $MSWin_back_slash [1] + This configuration variable only has an effect when latexmk is + running under MS-Windows. It determines whether, when a command + is executed under MS-Windows, there should be substituted "\" + for the separator character between components of a directory + name. Internally, latexmk uses "/" for the directory separator character, which is the character used by Unix-like systems. For many programs under MS-Windows, both "\" and "/" are accept- - able as the directory separator character. But some programs - only accept "\" on the command line. So for safety latexmk - makes a translation, by default. It is conceivable that under + able as the directory separator character. But some programs + only accept "\" on the command line. So for safety latexmk + makes a translation, by default. It is conceivable that under certain situations this is undesirable, so the configuration can be changed. (A possible example might be when some of the soft- - ware is implemented using Cygwin, which provides a Unix-like + ware is implemented using Cygwin, which provides a Unix-like environment inside MS-Windows.) - $new_viewer_always [0] - This variable applies to latexmk only in continuous-preview + This variable applies to latexmk only in continuous-preview mode. If $new_viewer_always is 0, latexmk will check for a pre- - viously running previewer on the same file, and if one is run- - ning will not start a new one. If $new_viewer_always is non- - zero, this check will be skipped, and latexmk will behave as if + viously running previewer on the same file, and if one is run- + ning will not start a new one. If $new_viewer_always is non- + zero, this check will be skipped, and latexmk will behave as if no viewer is running. - $out_dir [""] - If non-blank, this variable specifies the directory in which + If non-blank, this variable specifies the directory in which output files are to be written by a run of (pdf)latex. See also the variable $aux_dir. - The effect of this variable (when non-blank) is achieved by - using the -output-directory option of (pdf)latex. This exists - in the usual current (Dec. 2011 and later) implementations of - TeX, i.e., MiKTeX and TeXLive. But it may not be present in + The effect of this variable (when non-blank) is achieved by + using the -output-directory option of (pdf)latex. This exists + in the usual current (Dec. 2011 and later) implementations of + TeX, i.e., MiKTeX and TeXLive. But it may not be present in other versions. - If you also use the -cd option, and $out_dir (or $aux_dir) con- - tains a relative path, then the path is interpreted relative to + If you also use the -cd option, and $out_dir (or $aux_dir) con- + tains a relative path, then the path is interpreted relative to the document directory. - Commonly, the directory specified for output files is a subdi- + Commonly, the directory specified for output files is a subdi- rectory of the current working directory. However, if you spec- - ify some other directory, e.g., "/tmp/foo" or "../output", be - aware that this could cause problems, e.g., with makeindex or - bibtex. This is because modern versions of these programs, by - default, will refuse to work when they find that they are asked - to write to a file in a directory that appears not to be the + ify some other directory, e.g., "/tmp/foo" or "../output", be + aware that this could cause problems, e.g., with makeindex or + bibtex. This is because modern versions of these programs, by + default, will refuse to work when they find that they are asked + to write to a file in a directory that appears not to be the current working directory or one of its subdirectories. This is - part of security measures by the whole TeX system that try to + part of security measures by the whole TeX system that try to prevent malicious or errant TeX documents from incorrectly mess- ing with a user's files. If for $out_dir or $aux_dir you really - do need to specify an absolute pathname (e.g., "/tmp/foo") or a - path (e.g., "../output") that includes a higher-level directory, - and you need to use makeindex or bibtex, then you need to dis- - able the security measures (and assume any risks). One way of - 19 January 2017 39 + 20 November 2017 40 @@ -2578,33 +2644,34 @@ LATEXMK(1) General Commands Manual LATEXMK(1) LATEXMK(1) General Commands Manual LATEXMK(1) + do need to specify an absolute pathname (e.g., "/tmp/foo") or a + path (e.g., "../output") that includes a higher-level directory, + and you need to use makeindex or bibtex, then you need to dis- + able the security measures (and assume any risks). One way of doing this is to temporarily set an operating system environment - variable openout_any to "a" (as in "all"), to override the + variable openout_any to "a" (as in "all"), to override the default "paranoid" setting. - $pdf_mode [0] - If zero, do NOT generate a pdf version of the document. If - equal to 1, generate a pdf version of the document using pdfla- - tex, using the command specified by the $pdflatex variable. If - equal to 2, generate a pdf version of the document from the ps - file, by using the command specified by the $ps2pdf variable. - If equal to 3, generate a pdf version of the document from the - dvi file, by using the command specified by the $dvipdf vari- - able. If equal to 4, generate a pdf version of the document - using lualatex, using the command specified by the $lualatex - variable. If equal to 5, generate a pdf version (and an xdv + If zero, do NOT generate a pdf version of the document. If + equal to 1, generate a pdf version of the document using pdfla- + tex, using the command specified by the $pdflatex variable. If + equal to 2, generate a pdf version of the document from the ps + file, by using the command specified by the $ps2pdf variable. + If equal to 3, generate a pdf version of the document from the + dvi file, by using the command specified by the $dvipdf vari- + able. If equal to 4, generate a pdf version of the document + using lualatex, using the command specified by the $lualatex + variable. If equal to 5, generate a pdf version (and an xdv version) of the document using xelatex, using the commands spec- ified by the $xelatex and xdvipdfmx variables. - In $pdf_mode=2, it is ensured that dvi and ps files are also - made. In $pdf_mode=3, it is ensured that a dvi file is also + In $pdf_mode=2, it is ensured that dvi and ps files are also + made. In $pdf_mode=3, it is ensured that a dvi file is also made. - - $pdflatex ["pdflatex %O %S"] - The LaTeX processing program in a version that makes a pdf file + The LaTeX processing program in a version that makes a pdf file instead of a dvi file. An example use of this variable is to add certain options to the @@ -2612,30 +2679,29 @@ LATEXMK(1) General Commands Manual LATEXMK(1) $pdflatex = "pdflatex --shell-escape %O %S"; - (In some earlier versions of latexmk, you needed to use an - assignment to $pdflatex to allow the use of lualatex or xelatex + (In some earlier versions of latexmk, you needed to use an + assignment to $pdflatex to allow the use of lualatex or xelatex instead of pdflatex. There are now separate configuration vari- - ables for the use of lualatex or xelatex. See $lualatex and + ables for the use of lualatex or xelatex. See $lualatex and $xelatex.) - %pdflatex_input_extensions - This variable specifies the extensions tried by latexmk when it - finds that a pdflatex run resulted in an error that a file has - not been found, and the file is given without an extension. - This typically happens when LaTeX commands of the form + This variable specifies the extensions tried by latexmk when it + finds that a pdflatex run resulted in an error that a file has + not been found, and the file is given without an extension. + This typically happens when LaTeX commands of the form \input{file} or \includegraphics{figure}, when the relevant source file does not exist. - In this situation, latexmk searches for custom dependencies to - make the missing file(s), but restricts it to the extensions - specified by the variable %pdflatex_input_extensions. The + In this situation, latexmk searches for custom dependencies to + make the missing file(s), but restricts it to the extensions + specified by the variable %pdflatex_input_extensions. The default extensions are 'tex', 'pdf', 'jpg, and 'png'. - 19 January 2017 40 + 20 November 2017 41 @@ -2647,61 +2713,61 @@ LATEXMK(1) General Commands Manual LATEXMK(1) See details of the %latex_input_extensions for other information that equally applies to %pdflatex_input_extensions. - $pdflatex_silent_switch ["-interaction=batchmode"] - Switch(es) for the pdflatex program (specified in the variable + Switch(es) for the pdflatex program (specified in the variable $pdflatex) when silent mode is on. - See details of the $latex_silent_switch for other information + See details of the $latex_silent_switch for other information that equally applies to $pdflatex_silent_switch. - $pdf_previewer ["start acroread %O %S"] The command to invoke a pdf-previewer. - On MS-Windows, the default is changed to "cmd /c start """; + On MS-Windows, the default is changed to "cmd /c start """; under more recent versions of Windows, this will cause to be run whatever command the system has associated with .pdf files. But - this may be undesirable if this association is to acroread -- + this may be undesirable if this association is to acroread -- see the notes in the explanation of the -pvc option.] - On OS-X the default is changed to "open %S", which results in - OS-X starting up (and detaching) the viewer associated with the - file. By default, for pdf files this association is to OS-X's + On OS-X the default is changed to "open %S", which results in + OS-X starting up (and detaching) the viewer associated with the + file. By default, for pdf files this association is to OS-X's preview, which is quite satisfactory. - WARNING: Problem under MS-Windows: if acroread is used as the - pdf previewer, and it is actually viewing a pdf file, the pdf - file cannot be updated. Thus makes acroread a bad choice of - previewer if you use latexmk's previous-continuous mode (option - -pvc) under MS-windows. This problem does not occur if, for + WARNING: Problem under MS-Windows: if acroread is used as the + pdf previewer, and it is actually viewing a pdf file, the pdf + file cannot be updated. Thus makes acroread a bad choice of + previewer if you use latexmk's previous-continuous mode (option + -pvc) under MS-windows. This problem does not occur if, for example, SumatraPDF or gsview is used to view pdf files. - Important note: Normally you will want to have a previewer run + Important note: Normally you will want to have a previewer run detached, so that latexmk doesn't wait for the previewer to ter- - minate before continuing its work. So normally you should pre- - fix the command by "start ", which flags to latexmk that it - should do the detaching of the previewer itself (by whatever - method is appropriate to the operating system). But sometimes + minate before continuing its work. So normally you should pre- + fix the command by "start ", which flags to latexmk that it + should do the detaching of the previewer itself (by whatever + method is appropriate to the operating system). But sometimes letting latexmk do the detaching is not appropriate (for a vari- - ety of non-trivial reasons), so you should put the "start " bit + ety of non-trivial reasons), so you should put the "start " bit in yourself, whenever it is needed. - $pdf_update_command [""] - When the pdf previewer is set to be updated by running a com- - mand, this is the command that is run. See the information for + When the pdf previewer is set to be updated by running a com- + mand, this is the command that is run. See the information for the variable $pdf_update_method. $pdf_update_method [1 under UNIX, 3 under MS-Windows] - How the pdf viewer updates its display when the pdf file has - changed. See the information on the variable $dvi_update_method + How the pdf viewer updates its display when the pdf file has + changed. See the information on the variable $dvi_update_method for the codes. (Note that information needs be changed slightly - so that for the value 4, to run a command to do the update, the + so that for the value 4, to run a command to do the update, the + command is specified by the variable $pdf_update_command, and + for the value 2, to specify update by signal, the signal is + specified by $pdf_update_signal.) - 19 January 2017 41 + 20 November 2017 42 @@ -2710,10 +2776,6 @@ LATEXMK(1) General Commands Manual LATEXMK(1) LATEXMK(1) General Commands Manual LATEXMK(1) - command is specified by the variable $pdf_update_command, and - for the value 2, to specify update by signal, the signal is - specified by $pdf_update_signal.) - Note that acroread under MS-Windows (but not UNIX) locks the pdf file, so the default value is then 3. @@ -2724,50 +2786,54 @@ LATEXMK(1) General Commands Manual LATEXMK(1) $pdf_update_method = 4; $pdf_update_command = "xpdf -remote %R -reload"; - The first setting arranges for the xpdf program to be used in - its "remote server mode", with the server name specified as the - rootname of the TeX file. The second setting arranges for + The first setting arranges for the xpdf program to be used in + its "remote server mode", with the server name specified as the + rootname of the TeX file. The second setting arranges for updating to be done in response to a command, and the third set- ting sets the update command. - - $pdf_update_signal [Under UNIX: SIGHUP, which is a system-dependent + $pdf_update_signal [Under UNIX: SIGHUP, which is a system-dependent value] - The number of the signal that is sent to the pdf viewer when it - is updated by sending a signal -- see the information on the - variable $pdf_update_method. The default value is the one + The number of the signal that is sent to the pdf viewer when it + is updated by sending a signal -- see the information on the + variable $pdf_update_method. The default value is the one appropriate for gv on a UNIX system. $pid_position[1 under UNIX, -1 under MS-Windows] - The variable $pid_position is used to specify which word in - lines of the output from $pscmd corresponds to the process ID. - The first word in the line is numbered 0. The default value of + The variable $pid_position is used to specify which word in + lines of the output from $pscmd corresponds to the process ID. + The first word in the line is numbered 0. The default value of 1 (2nd word in line) is correct for Solaris 2.6, Linux, and OS-X with their default settings of $pscmd. - Setting the variable to -1 is used to indicate that $pscmd is + Setting the variable to -1 is used to indicate that $pscmd is not to be used. $postscript_mode [0] - If nonzero, generate a postscript version of the document. + If nonzero, generate a postscript version of the document. Equivalent to the -ps option. - If some other request is made for which a postscript file is + If some other request is made for which a postscript file is needed, then $postscript_mode will be set to 1. $preview_continuous_mode [0] - If nonzero, run a previewer to view the document, and continue + If nonzero, run a previewer to view the document, and continue running latexmk to keep .dvi up-to-date. Equivalent to the -pvc - option. Which previewer is run depends on the other settings, + option. Which previewer is run depends on the other settings, see the command line options -view=, and the variable $view. $preview_mode [0] If nonzero, run a previewer to preview the document. Equivalent - to the -pv option. Which previewer is run depends on the other + to the -pv option. Which previewer is run depends on the other + settings, see the command line options -view=, and the variable + $view. + + $printout_mode [0] + If nonzero, print the document using the command specified in - 19 January 2017 42 + 20 November 2017 43 @@ -2776,33 +2842,28 @@ LATEXMK(1) General Commands Manual LATEXMK(1) LATEXMK(1) General Commands Manual LATEXMK(1) - settings, see the command line options -view=, and the variable - $view. - - $printout_mode [0] - If nonzero, print the document using the command specified in the $lpr variable. Equivalent to the -p option. This is recom- - mended not to be set from an RC file, otherwise you could waste + mended not to be set from an RC file, otherwise you could waste lots of paper. $print_type = ["auto"] - Type of file to printout: possibilities are "auto", "dvi", + Type of file to printout: possibilities are "auto", "dvi", "none", "pdf", or "ps". See the option -print= for the meaning of the "auto" value. $pscmd Command used to get all the processes currently run by the user. - The -pvc option uses the command specified by the variable - $pscmd to determine if there is an already running previewer, - and to find the process ID (needed if latexmk needs to signal + The -pvc option uses the command specified by the variable + $pscmd to determine if there is an already running previewer, + and to find the process ID (needed if latexmk needs to signal the previewer about file changes). Each line of the output of this command is assumed to correspond - to one process. See the $pid_position variable for how the + to one process. See the $pid_position variable for how the process number is determined. - The default for pscmd is "NONE" under MS-Windows and cygwin - (i.e., the command is not used), "ps -ww -u $ENV{USER}" under - OS-X, and "ps -f -u $ENV{USER}" under other operating systems + The default for pscmd is "NONE" under MS-Windows and cygwin + (i.e., the command is not used), "ps -ww -u $ENV{USER}" under + OS-X, and "ps -f -u $ENV{USER}" under other operating systems (including Linux). In these specifications "$ENV{USER}" is sub- stituted by the username. @@ -2811,29 +2872,34 @@ LATEXMK(1) General Commands Manual LATEXMK(1) $ps_filter [empty] The postscript file filter to be run on the newly produced post- - script file before other processing. Equivalent to specifying + script file before other processing. Equivalent to specifying the -pF option. $ps_previewer ["start gv %O %S", but start %O %S under MS-Windows] - The command to invoke a ps-previewer. (The default under MS- - Windows will cause to be run whatever command the system has + The command to invoke a ps-previewer. (The default under MS- + Windows will cause to be run whatever command the system has associated with .ps files.) - Note that gv could be used with the -watch option updates its - display whenever the postscript file changes, whereas ghostview - does not. However, different versions of gv have slightly dif- - ferent ways of writing this option. You can configure this + Note that gv could be used with the -watch option updates its + display whenever the postscript file changes, whereas ghostview + does not. However, different versions of gv have slightly dif- + ferent ways of writing this option. You can configure this variable appropriately. WARNING: Linux systems may have installed one (or more) versions - of gv under different names, e.g., ggv, kghostview, etc, but + of gv under different names, e.g., ggv, kghostview, etc, but perhaps not one actually called gv. - Important note: Normally you will want to have a previewer run + Important note: Normally you will want to have a previewer run + detached, so that latexmk doesn't wait for the previewer to ter- + minate before continuing its work. So normally you should pre- + fix the command by "start ", which flags to latexmk that it + should do the detaching of the previewer itself (by whatever + method is appropriate to the operating system). But sometimes - 19 January 2017 43 + 20 November 2017 44 @@ -2842,64 +2908,64 @@ LATEXMK(1) General Commands Manual LATEXMK(1) LATEXMK(1) General Commands Manual LATEXMK(1) - detached, so that latexmk doesn't wait for the previewer to ter- - minate before continuing its work. So normally you should pre- - fix the command by "start ", which flags to latexmk that it - should do the detaching of the previewer itself (by whatever - method is appropriate to the operating system). But sometimes letting latexmk do the detaching is not appropriate (for a vari- - ety of non-trivial reasons), so you should put the "start " bit + ety of non-trivial reasons), so you should put the "start " bit in yourself, whenever it is needed. - $ps_previewer_landscape ["start gv -swap %O %S", but start %O %S under + $ps_previewer_landscape ["start gv -swap %O %S", but start %O %S under MS-Windows] The command to invoke a ps-previewer in landscape mode. $ps_update_command [""] - When the postscript previewer is set to be updated by running a - command, this is the command that is run. See the information + When the postscript previewer is set to be updated by running a + command, this is the command that is run. See the information for the variable $ps_update_method. $ps_update_method [0 under UNIX, 1 under MS-Windows] - How the postscript viewer updates its display when the ps file - has changed. See the information on the variable - $dvi_update_method for the codes. (Note that information needs + How the postscript viewer updates its display when the ps file + has changed. See the information on the variable + $dvi_update_method for the codes. (Note that information needs be changed slightly so that for the value 4, to run a command to do the update, the command is specified by the variable - $ps_update_command, and for the value 2, to specify update by + $ps_update_command, and for the value 2, to specify update by signal, the signal is specified by $ps_update_signal.) - - $ps_update_signal [Under UNIX: SIGHUP, which is a system-dependent + $ps_update_signal [Under UNIX: SIGHUP, which is a system-dependent value] - The number of the signal that is sent to the pdf viewer when it - is updated by sending a signal -- see $ps_update_method. The + The number of the signal that is sent to the pdf viewer when it + is updated by sending a signal -- see $ps_update_method. The default value is the one appropriate for gv on a UNIX system. - $pvc_view_file_via_temporary [1] The same as $always_view_file_via_temporary, except that it only applies in preview-continuous mode (-pvc option). - $quote_filenames [1] This specifies whether substitutions for placeholders in command specifications (as in $pdflatex) are surrounded by double - quotes. If this variable is 1 (or any other value Perl regards + quotes. If this variable is 1 (or any other value Perl regards as true), then quoting is done. Otherwise quoting is omitted. - The quoting method used by latexmk is tested to work correctly - under UNIX systems (including Linux and Mac OS-X) and under MS- - Windows. It allows the use of filenames containing special - characters, notably spaces. (But note that many versions of - latex and pdflatex cannot correctly deal with TeX files whose - names contain spaces. Latexmk's quoting only ensures that such - filenames are correctly treated by the operating system in + The quoting method used by latexmk is tested to work correctly + under UNIX systems (including Linux and Mac OS-X) and under MS- + Windows. It allows the use of filenames containing special + characters, notably spaces. (But note that many versions of + latex and pdflatex cannot correctly deal with TeX files whose + names contain spaces. Latexmk's quoting only ensures that such + filenames are correctly treated by the operating system in pass- + ing arguments to programs.) + + $recorder [1] + Whether to use the -recorder option to latex and pdflatex. Use + of this option results in a file of extension .fls containing a + list of the files that these programs have read and written. + Latexmk will then use this file to improve its detection of + source files and generated files after a run of latex or - 19 January 2017 44 + 20 November 2017 45 @@ -2908,64 +2974,64 @@ LATEXMK(1) General Commands Manual LATEXMK(1) LATEXMK(1) General Commands Manual LATEXMK(1) - passing arguments to programs.) + pdflatex. - $recorder [1] - Whether to use the -recorder option to latex and pdflatex. Use - of this option results in a file of extension .fls containing a - list of the files that these programs have read and written. - Latexmk will then use this file to improve its detection of - source files and generated files after a run of latex or pdfla- - tex. - - It is generally recommended to use this option (or to configure - the $recorder variable to be on.) But it only works if + It is generally recommended to use this option (or to configure + the $recorder variable to be on.) But it only works if (pdf)latex supports the -recorder option, which is true for most current implementations - Note about the name of the .fls file: Most implementations of - (pdf)latex produce an .fls file with the same basename as the - main document's LaTeX, e.g., for Document.tex, the .fls file is - Document.fls. However, some implementations instead produce - files named for the program, i.e., latex.fls or pdflatex.fls. - In this second case, latexmk copies the latex.fls or pdfla- - tex.fls to a file with the basename of the main LaTeX document, + Note about the name of the .fls file: Most implementations of + (pdf)latex produce an .fls file with the same basename as the + main document's LaTeX, e.g., for Document.tex, the .fls file is + Document.fls. However, some implementations instead produce + files named for the program, i.e., latex.fls or pdflatex.fls. + In this second case, latexmk copies the latex.fls or pdfla- + tex.fls to a file with the basename of the main LaTeX document, e.g., Document.fls. - $search_path_separator [See below for default] The character separating paths in the environment variables TEX- - INPUTS, BIBINPUTS, and BSTINPUTS. This variable is mainly used - by latexmk when the -outdir, -output-directory, -auxdir, and/or - -aux-directory options are used. In that case latexmk needs to + INPUTS, BIBINPUTS, and BSTINPUTS. This variable is mainly used + by latexmk when the -outdir, -output-directory, -auxdir, and/or + -aux-directory options are used. In that case latexmk needs to communicate appropriately modified search paths to bibtex, dvipdf, dvips, and (pdf)latex. - [Comment to technically savvy readers: (pdf)latex doesn't actu- - ally need the modified search path. But, surprisingly, dvipdf - and dvips do, because sometimes graphics files get generated in + [Comment to technically savvy readers: (pdf)latex doesn't actu- + ally need the modified search path. But, surprisingly, dvipdf + and dvips do, because sometimes graphics files get generated in the output or aux directories.] - The default under MSWin and Cygwin is ';' and under UNIX-like - operating systems (including Linux and OS-X) is ':'. Normally - the defaults give correct behavior. But there can be difficul- - ties if your operating system is of one kind, but some of your - software is running under an emulator for the other kind of - operating system; in that case you'll need to find out what is - needed, and set $search_path_separator explicitly. (The same - goes, of course, for unusual operating systems that are not in + The default under MSWin and Cygwin is ';' and under UNIX-like + operating systems (including Linux and OS-X) is ':'. Normally + the defaults give correct behavior. But there can be difficul- + ties if your operating system is of one kind, but some of your + software is running under an emulator for the other kind of + operating system; in that case you'll need to find out what is + needed, and set $search_path_separator explicitly. (The same + goes, of course, for unusual operating systems that are not in the MSWin, Linux, OS-X, Unix collection.) - $show_time [0] Whether to show CPU time used. + $silence_logfile_warnings [0] + Whether after a run of (pdf)latex to summarize warnings in the + log file about undefined citations and references. Setting + $silence_logfile_warnings=0 gives the summary of warnings (pro- + vided silent mode isn't also set), and this is useful to locate + undefined citations and references without searching through the + much more verbose log file or the screen output of (pdf)latex. + But the summary can also be excessively annoying. The default + is not to give these warnings. The command line options + -silence_logfile_warning_list and -silence_logfile_warning_list- + also set this variable. - - 19 January 2017 45 + 20 November 2017 46 @@ -2974,196 +3040,196 @@ LATEXMK(1) General Commands Manual LATEXMK(1) LATEXMK(1) General Commands Manual LATEXMK(1) - $silence_logfile_warnings [0] - Whether after a run of (pdf)latex to summarize warnings in the - log file about undefined citations and references. Setting - $silence_logfile_warnings=0 gives the summary of warnings (pro- - vided silent mode isn't also set), and this is useful to locate - undefined citations and references without searching through the - much more verbose log file or the screen output of (pdf)latex. - But the summary can also be excessively annoying. The default - is not to give these warnings. The command line options - -silence_logfile_warning_list and -silence_logfile_warning_list- - also set this variable. - - Note that multiple occurrences for the same undefined object on + Note that multiple occurrences for the same undefined object on the same page and same line will be compressed to a single warn- ing. - $silent [0] - Whether to run silently. Setting $silent to 1 has the same + Whether to run silently. Setting $silent to 1 has the same effect as the -quiet of -silent options on the command line. - $sleep_time [2] - The time to sleep (in seconds) between checking for source file + The time to sleep (in seconds) between checking for source file changes when running with the -pvc option. This is subject to a - minimum of one second delay, except that zero delay is also + minimum of one second delay, except that zero delay is also allowed. - A value of exactly 0 gives no delay, and typically results in + A value of exactly 0 gives no delay, and typically results in 100% CPU usage, which may not be desirable. $texfile_search [""] - This is an obsolete variable, replaced by the @default_files + This is an obsolete variable, replaced by the @default_files variable. - For backward compatibility, if you choose to set $tex- - file_search, it is a string of space-separated filenames, and + For backward compatibility, if you choose to set $tex- + file_search, it is a string of space-separated filenames, and then latexmk replaces @default_files with the filenames in $tex- file_search to which is added "*.tex". - $success_cmd [undefined] See the documentation for $compiling_cmd. - $tmpdir [See below for default] - Directory to store temporary files that latexmk may generate + Directory to store temporary files that latexmk may generate while running. - The default under MSWindows (including cygwin), is to set - $tmpdir to the value of the first of whichever of the system - environment variables TMPDIR or TEMP exists, otherwise to the - current directory. Under other operating systems (expected to - be UNIX/Linux, including OS-X), the default is the value of the - + The default under MSWindows (including cygwin), is to set + $tmpdir to the value of the first of whichever of the system + environment variables TMPDIR or TEMP exists, otherwise to the + current directory. Under other operating systems (expected to + be UNIX/Linux, including OS-X), the default is the value of the + system environment variable TMPDIR if it exists, otherwise + "/tmp". + $use_make_for_missing_files [0] + Whether to use make to try and make files that are missing after + a run of latex or pdflatex, and for which a custom dependency + has not been found. This is generally useful only when latexmk + is used as part of a bigger project which is built by using the + make program. - 19 January 2017 46 + Note that once a missing file has been made, no further calls to + make will be made on a subsequent run of latexmk to update the + file. Handling this problem is the job of a suitably defined + Makefile. See the section "USING latexmk WITH make" for how to + do this. The intent of calling make from latexmk is merely to + detect dependencies. + 20 November 2017 47 -LATEXMK(1) General Commands Manual LATEXMK(1) - system environment variable TMPDIR if it exists, otherwise - "/tmp". - $use_make_for_missing_files [0] - Whether to use make to try and make files that are missing after - a run of latex or pdflatex, and for which a custom dependency - has not been found. This is generally useful only when latexmk - is used as part of a bigger project which is built by using the - make program. +LATEXMK(1) General Commands Manual LATEXMK(1) - Note that once a missing file has been made, no further calls to - make will be made on a subsequent run of latexmk to update the - file. Handling this problem is the job of a suitably defined - Makefile. See the section "USING latexmk WITH make" for how to - do this. The intent of calling make from latexmk is merely to - detect dependencies. $view ["default"] - Which kind of file is to be previewed if a previewer is used. - The possible values are "default", "dvi", "ps", "pdf". The + Which kind of file is to be previewed if a previewer is used. + The possible values are "default", "dvi", "ps", "pdf". The value of "default" means that the "highest" of the kinds of file generated is to be used (among dvi, ps and pdf). - $xdvipdfmx ["xdvipdfmx -o %D %O %S"] - The program to make a pdf file from an xdv file (used in con- + The program to make a pdf file from an xdv file (used in con- junction with xelatex when $pdf_mode=5). - $xdvipdfmx_silent_switch ["-q"] Switch(es) for the xdvipdfmx program when silent mode is on. - $xelatex ["xelatex %O %S"] - The LaTeX processing program of in a version that makes a pdf - file instead of a dvi file, when the xelatex program is called + The LaTeX processing program of in a version that makes a pdf + file instead of a dvi file, when the xelatex program is called for. See the documentation of the -xelatex option for some spe- cial properties of latexmk's use of xelatex. - %xelatex_input_extensions - This variable specifies the extensions tried by latexmk when it - finds that an xelatex run resulted in an error that a file has - not been found, and the file is given without an extension. - This typically happens when LaTeX commands of the form + This variable specifies the extensions tried by latexmk when it + finds that an xelatex run resulted in an error that a file has + not been found, and the file is given without an extension. + This typically happens when LaTeX commands of the form \input{file} or \includegraphics{figure}, when the relevant source file does not exist. - In this situation, latexmk searches for custom dependencies to - make the missing file(s), but restricts it to the extensions - specified by the variable %xelatex_input_extensions. The + In this situation, latexmk searches for custom dependencies to + make the missing file(s), but restricts it to the extensions + specified by the variable %xelatex_input_extensions. The default extensions are 'tex', 'pdf', 'jpg, and 'png'. + See details of the %latex_input_extensions for other information + that equally applies to %xelatex_input_extensions. + $xelatex_silent_switch ["-interaction=batchmode"] + Switch(es) for the xelatex program (specified in the variable + $xelatex) when silent mode is on. + See details of the $latex_silent_switch for other information + that equally applies to $xelatex_silent_switch. - 19 January 2017 47 +CUSTOM DEPENDENCIES + In any RC file a set of custom dependencies can be set up to convert a + file with one extension to a file with another. An example use of this + would be to allow latexmk to convert a .fig file to .eps to be included + in the .tex file. -LATEXMK(1) General Commands Manual LATEXMK(1) - See details of the %latex_input_extensions for other information - that equally applies to %xelatex_input_extensions. - $xelatex_silent_switch ["-interaction=batchmode"] - Switch(es) for the xelatex program (specified in the variable - $xelatex) when silent mode is on. + 20 November 2017 48 - See details of the $latex_silent_switch for other information - that equally applies to $xelatex_silent_switch. -CUSTOM DEPENDENCIES - In any RC file a set of custom dependencies can be set up to convert a - file with one extension to a file with another. An example use of this - would be to allow latexmk to convert a .fig file to .eps to be included - in the .tex file. +LATEXMK(1) General Commands Manual LATEXMK(1) - The old method of configuring latexmk was to directly manipulate the - @cus_dep_list array that contains information defining the custom - dependencies. This method still works. But now there are subroutines - that allow convenient manipulations of the custom dependency list. - These are + + Defining a custom dependency: + The old method of configuring latexmk to use a custom dependency was to + directly manipulate the @cus_dep_list array that contains information + defining the custom dependencies. (See the section "Old Method of + Defining Custom Dependencies" for details.) This method still works, + but is no longer preferred. + + A better method is to use the subroutines that allow convenient manipu- + lations of the custom dependency list. These are add_cus_dep( fromextension, toextension, must, subroutine ) remove_cus_dep( fromextension, toextension ) show_cus_dep() - The custom dependency is a list of rules, each of which is specified as - follow: + The arguments are as follows: from extension: - The extension of the file we are converting from (e.g. "fig"). + The extension of the file we are converting from (e.g. "fig"). It is specified without a period. to extension: The extension of the file we are converting to (e.g. "eps"). It is specified without a period. - must: If non-zero, the file from which we are converting must exist, - if it doesn't exist latexmk will give an error message and exit + must: If non-zero, the file from which we are converting must exist, + if it doesn't exist latexmk will give an error message and exit unless the -f option is specified. If must is zero and the file we are converting from doesn't exist, then no action is taken. function: - The name of the subroutine that latexmk should call to perform - the file conversion. The first argument to the subroutine is + The name of the subroutine that latexmk should call to perform + the file conversion. The first argument to the subroutine is the base name of the file to be converted without any extension. - The subroutines are declared in the syntax of Perl. The func- - tion should return 0 if it was successful and a nonzero number + The subroutines are declared in the syntax of Perl. The func- + tion should return 0 if it was successful and a nonzero number if it failed. + Naturally add_cus_dep adds a custom dependency with the specified from + and to extensions. If a custom dependency has been previously defined + (e.g., in an rcfile that was read earlier), then it is replaced by the + new one. + The subroutine remove_cus_dep removes the specified custom dependency. + The subroutine show_cus_dep causes a list of the currently defined cus- + tom dependencies to be sent to the screen output. + + + How custom dependencies are used: + A custom dependency rule is invoked whenever latexmk detects that a run + of latex/pdflatex needs to read a file, like a graphics file, whose + extension is the to-extension of a custom dependency. Then latexmk + examines whether a file exists with the same name, but with the corre- + sponding from-extension, as specified in the custom-dependency rule. - 19 January 2017 48 + + + 20 November 2017 49 @@ -3172,14 +3238,9 @@ CUSTOM DEPENDENCIES LATEXMK(1) General Commands Manual LATEXMK(1) - A custom dependency rule is invoked whenever latexmk detects that a run - of latex/pdflatex needs to read a file, like a graphics file, whose - extension is the to-extension of a custom dependency. Then latexmk - examines whether a file exists with the same name, but with the corre- - sponding from-extension, as specified in the custom-dependency rule. - If it does, then the rule whenever the destination file (the one with - the to-extension) is out-of-date with respect to the corresponding - source file. + If it does, then the rule is invoked whenever the destination file (the + one with the to-extension) is out-of-date with respect to the corre- + sponding source file. To make the new destination file, the Perl subroutine specified in the rule is invoked, with an argument that is the base name of the files in @@ -3188,15 +3249,23 @@ LATEXMK(1) General Commands Manual LATEXMK(1) those without knowledge of the Perl programming language. Of course, experts could do something much more elaborate. - One other item in each custom-dependency rule, labeled "must" above, - specifies how the rule should be applied when the source file fails to - exist. + One other item in the specification of each custom-dependency rule, + labeled "must" above, specifies how the rule should be applied when the + source file fails to exist. + - A simple and typical example of code in an initialization rcfile is + Function to implement custom dependency, traditional method: + The function that implements a custom dependency gets the information + on the files to be processed in two ways. The first is through its one + argument; the argument contains the base name of the source and desti- + nation files. The second way is described later. + + A simple and typical example of code in an initialization rcfile using + the first method is: add_cus_dep( 'fig', 'eps', 0, 'fig2eps' ); sub fig2eps { - return system( "fig2dev -Leps \"$_[0].fig\" \"$_[0].eps\"" ); + system( "fig2dev -Leps \"$_[0].fig\" \"$_[0].eps\"" ); } The first line adds a custom dependency that converts a file with @@ -3223,13 +3292,10 @@ LATEXMK(1) General Commands Manual LATEXMK(1) return value is the value returned by the last (and only) statement, i.e., the invocation of system, which returns the value 0 on success. - If you use pdflatex instead of latex, then you will probably prefer to - convert your graphics files to pdf format, in which case you would - replace the above code in an initialization file by - 19 January 2017 49 + 20 November 2017 50 @@ -3238,9 +3304,13 @@ LATEXMK(1) General Commands Manual LATEXMK(1) LATEXMK(1) General Commands Manual LATEXMK(1) + If you use pdflatex instead of latex, then you will probably prefer to + convert your graphics files to pdf format, in which case you would + replace the above code in an initialization file by + add_cus_dep( 'fig', 'pdf, 0, 'fig2pdf' ); sub fig2pdf { - return system( "fig2dev -Lpdf \"$_[0].fig\" \"$_[0].pdf\"" ); + system( "fig2dev -Lpdf \"$_[0].fig\" \"$_[0].pdf\"" ); } Note 1: In the command lines given in the system commands in the above @@ -3263,10 +3333,22 @@ LATEXMK(1) General Commands Manual LATEXMK(1) run of MiKTeX (at least in v. 2.9) for an example of the use of both directory separators.) + Note 3: The subroutines implementing custom dependencies in the exam- + ples given just have a single line invoking an external program. + That's the usual situation. But since the subroutines are in the Perl + language, you can implement much more complicated processing if you + need it. + + + Removing custom dependencies, and when you might need to do this: If you have some general custom dependencies defined in the system or user initialization file, you may find that for a particular project they are undesirable. So you might want to delete the unneeded ones. - For example, you remove any "fig" to "eps" rule by the line + A situation where this would be desirable is where there are multiple + custom dependencies with the same from-extension or the same to-exten- + sion. In that case, latexmk might choose a different one from the one + you want for a specific project. As an example, to remove any "fig" to + "eps" rule you would use: remove_cus_dep( 'fig', 'eps' ); @@ -3276,26 +3358,76 @@ LATEXMK(1) General Commands Manual LATEXMK(1) show_cus_dep(); + + + + 20 November 2017 51 + + + + + +LATEXMK(1) General Commands Manual LATEXMK(1) + + in an initialization file. - Another example of a custom dependency overcomes a limitation of - latexmk concerning index files. The only index-file conversion built- - in to latexmk is from an ".idx" file written on one run of latex/pdfla- - tex to an ".ind" file to be read in on a subsequent run. But with the - index.sty package you can create extra indexes with extensions that you - configure. Latexmk does not know how to deduce the extensions from the - information it has. But you can easily write a custom dependency. For - example if your latex file uses the command "\newindex{spe- - cial}{ndx}{nnd}{Special index}" you will need to convert files with the - extension .ndx to .nnd. The following lines in an initialization RC - file will cause this to happen: - add_cus_dep('ndx', 'nnd', 0, 'makendx2nnd'); - sub makendx2nnd { + Function implementing custom dependency, alternative methods: + So far the examples for functions to implement custom dependencies have + used the argument of the function to specify the base name of converted + file. This method has been available since very old versions of + latexmk, and many examples can be found, e.g., on the web. + + However in later versions of latexmk the internal structure of the + implementation of its "rules" for the steps of processing, including + custom dependencies, became much more powerful. The function imple- + menting a custom dependency is executed within a special context where + a number of extra variables and subroutines are defined. Publicly doc- + umented ones, intended to be long-term stable, are listed below, under + the heading "Variables and subroutines for processing a rule". + + Examples of their use is given in the following examples, concerning + multiple index files and glossaries. + + The only index-file conversion built-in to latexmk is from an ".idx" + file written on one run of latex/pdflatex to an ".ind" file to be read + in on a subsequent run. But with the index.sty package, for example, + you can create extra indexes with extensions that you configure. + Latexmk does not know how to deduce the extensions from the information + it has. But you can easily write a custom dependency. For example if + your latex file uses the command "\newindex{special}{ndx}{nnd}{Special + index}" you will need to get latexmk to convert files with the exten- + sion .ndx to .nnd. The most elementary method is to define a custom + dependency as follows: + + add_cus_dep( 'ndx', 'nnd', 0, 'ndx2nnd' ); + sub ndx2nnd { + return system( "makeindex -o \"$_[0].nnd\" \"$_[0].ndx\"" ); + } + push @generated_exts, 'ndx', 'nnd'; + + Notice the added line compared with earlier examples. The extra line + gets the extensions "ndx" and "nnd" added to the list of extensions for + generated files; then the extra index files will be deleted by clean-up + operations + + But if you have yet more indexes with yet different extensions, e.g., + "adx" and "and", then you will need a separate function for each pair + of extensions. This is quite annoying. You can use the Run_subst + function to simplify the definitions to use a single function: + + add_cus_dep( 'ndx', 'nnd', 0, 'dx2nd' ); + add_cus_dep( 'adx', 'and', 0, 'dx2nd' ); + sub dx2nd { + return Run_subst( "makeindex -o %D %S" ); + } + push @generated_exts, 'ndx', 'nnd', 'adx', 'and'; + - 19 January 2017 50 + 20 November 2017 52 @@ -3304,29 +3436,37 @@ LATEXMK(1) General Commands Manual LATEXMK(1) LATEXMK(1) General Commands Manual LATEXMK(1) - return system( "makeindex -o \"$_[0].nnd\" \"$_[0].ndx\"" ); + You could also instead use + + add_cus_dep( 'ndx', 'nnd', 0, 'dx2nd' ); + add_cus_dep( 'adx', 'and', 0, 'dx2nd' ); + sub dx2nd { + return Run_subst( $makeindex ); } + push @generated_exts, 'ndx', 'nnd', 'adx', 'and'; + + This last example uses the command specification in $makeindex, and so + any customization you have made for the standard index also applies to + your extra indexes. - Those of you with experience with Makefiles, will undoubtedly be con- - cerned that the .ndx file is written during a run of latex/pdflatex and - is always later than the .nnd last read in. Thus the .nnd appears to - be perpetually out-of-date. This situation, of circular dependencies, - is endemic to latex, and latexmk in its current version works correctly - with circular dependencies. It examines the contents of the files (by - use of an md5 checksum), and only does a remake when the file contents - have actually changed. + Similar techniques can be applied for glossaries. + + Those of you with experience with Makefiles, may get concerned that the + .ndx file is written during a run of latex/pdflatex and is always later + than the .nnd last read in. Thus the .nnd appears to be perpetually + out-of-date. This situation, of circular dependencies, is endemic to + latex, and is one of the issues that latexmk is programmed to overcome. + It examines the contents of the files (by use of a checksum), and only + does a remake when the file contents have actually changed. Of course if you choose to write random data to the .nnd (or the .aux file, etc) that changes on each new run, then you will have a problem. For real experts: See the %hash_cal_ignore_pattern if you have to deal with such problems. - Glossaries can be dealt with similarly. - - -OLD METHOD OF DEFINING CUSTOM DEPENDENCIES - In previous versions of latexmk, the only method of defining custom + Old Method of Defining Custom Dependencies: + In much older versions of latexmk, the only method of defining custom dependencies was to directly manipulate the table of custom dependen- cies. This is contained in the @cus_dep_list array. It is an array of strings, and each string in the array has four items in it, each sepa- @@ -3343,25 +3483,17 @@ OLD METHOD OF DEFINING CUSTOM DEPENDENCIES return system( "fig2dev -Lps \"$_[0].fig\" \"$_[0].eps\"" ); } - This method still works, and is equivalent to the earlier code using - the add_cus_dep subroutine, except that it doesn't delete any previous - custom-dependency for the same conversion. So the new method is - preferable. + This method still works, and is almost equivalent to the code given + earlier that used the add_cus_dep subroutine. However, the old method + doesn't delete any previous custom-dependency for the same conversion. + So the new method is preferable. -ADVANCED CONFIGURATION: Some extra resources and advanced tricks - For most purposes, simple configuration for latexmk along the lines of - the examples given is sufficient. But sometimes you need something - harder. In this section, I indicate some extra possibilities. Gener- - ally to use these, you need to be fluent in the Perl language, since - this is what is used in the rc files. - - See also the section DEALING WITH ERRORS, PROBLEMS, ETC. See also the - 19 January 2017 51 + 20 November 2017 53 @@ -3370,64 +3502,64 @@ ADVANCED CONFIGURATION: Some extra resources and advanced tricks LATEXMK(1) General Commands Manual LATEXMK(1) +ADVANCED CONFIGURATION: Some extra resources and advanced tricks + For most purposes, simple configuration for latexmk along the lines of + the examples given is sufficient. But sometimes you need something + harder. In this section, I indicate some extra possibilities. Gener- + ally to use these, you need to be fluent in the Perl language, since + this is what is used in the rc files. + + See also the section DEALING WITH ERRORS, PROBLEMS, ETC. See also the examples in the directory example_rcfiles in the latexmk distributions. - Even if none of the examples apply to your case, they may give ideas + Even if none of the examples apply to your case, they may give you use- + ful ideas Variables and subroutines for processing a rule A step in the processing is called a rule. One possibility to implement - the processing of a rule is by a Perl subroutine. This is always the - case for custom dependencies. Also, for any other rule, you can use a - subroutine by prefixing the command specification by the word "inter- + the processing of a rule is by a Perl subroutine. This is always the + case for custom dependencies. Also, for any other rule, you can use a + subroutine by prefixing the command specification by the word "inter- nal" -- see the section FORMAT OF COMMAND SPECIFICATIONS. - When you use a subroutine for processing a rule, all the possibilities - of Perl programming are available, of course. In addition, some of - latexmk's internal variables and subroutines are available. The ones - listed below are intended to be available to (advanced) users, and + When you use a subroutine for processing a rule, all the possibilities + of Perl programming are available, of course. In addition, some of + latexmk's internal variables and subroutines are available. The ones + listed below are intended to be available to (advanced) users, and their specifications will generally have stability under upgrades. Gen- - erally, the variables should be treated as read-only: Changing their - values can have bad consequences, since it is liable to mess up the + erally, the variables should be treated as read-only: Changing their + values can have bad consequences, since it is liable to mess up the consistency of what latexmk is doing. - - $rule This variable has the name of the rule, as known to latexmk. - Note that the exact contents of this variable for a given rule + $rule This variable has the name of the rule, as known to latexmk. + Note that the exact contents of this variable for a given rule may be dependent on the version of latexmk - $$Psource This gives the name of the primary source file. Note the double dollar signs. - $$Pdest - This gives the name of the main output file if any. Note the + This gives the name of the main output file if any. Note the double dollar signs. - rdb_ensure_file( $rule, file ) - This a subroutine that ensures that the given file is among the + This a subroutine that ensures that the given file is among the source files for the specified rule. It is typically used when, - during the processing of a rule, it is known that a particular - extra file is among the dependencies that latexmk should know, + during the processing of a rule, it is known that a particular + extra file is among the dependencies that latexmk should know, but its default methods don't find the dependency. Almost always - the first argument is the name of the rule currently being pro- + the first argument is the name of the rule currently being pro- cessed, so it is then appropriate to specify it by $rule. - For examples of its use, see some of the files in the directory - example_rcfiles of latexmk's distribution. Currently the cases - that use this subroutine are exceltex_latexmkrc and texinfo- - latexmkrc. These illustrate typical cases where latexmk's nor- - mal processing fails to detect certain extra source files. + For examples of its use, see some of the files in the directory + example_rcfiles of latexmk's distribution. Currently the cases + that use this subroutine are bib2gls-latexmkrc, excel- + tex_latexmkrc and texinfo-latexmkrc. These illustrate typical - rdb_remove_files( $rule, file, ... ) - This subroutine removes one or more files from the dependency - - - 19 January 2017 52 + 20 November 2017 54 @@ -3436,72 +3568,85 @@ LATEXMK(1) General Commands Manual LATEXMK(1) LATEXMK(1) General Commands Manual LATEXMK(1) - list for the given rule. + cases where latexmk's normal processing fails to detect certain + extra source files. + rdb_remove_files( $rule, file, ... ) + This subroutine removes one or more files from the dependency + list for the given rule. rdb_list_source( $rule ) This subroutine returns the list of source files (i.e., the dependency list) for the given rule. - rdb_set_source( $rule, file, ... ) - rdb_set_source( $rule, @files ) This subroutine sets the depen- - dency list for the given rule to be the specified files. Files - that are already in the list have unchanged information. Files - that were not in the list are added to it. Files in the previ- - ous dependency list that are not in the newly specified list of - files are removed from the dependency list. + rdb_set_source( $rule, @files ) + This subroutine sets the dependency list for the given rule to + be the specified files. Files that are already in the list have + unchanged information. Files that were not in the list are + added to it. Files in the previous dependency list that are not + in the newly specified list of files are removed from the depen- + dency list. + + Run_subst( command_spec ) + This subroutine runs the command specified by command_spec. The + specification is a string in the format listed in the section + "Format of Command Specifications". An important action of the + Run_subst is to make substitutions of placeholders, e.g., %S and + %D for source and destination files; these get substituted + before the command is run. In addition, the command after sub- + stitution is printed to the screen unless latexmk is running in + silent mode. Advanced configuration: Using latexmk with make - This section is targeted only at advanced users who use the make pro- + This section is targeted only at advanced users who use the make pro- gram for complex projects, as for software development, with the depen- dencies specified by a Makefile. - Now the basic task of latexmk is to run the appropriate programs to - make a viewable version of a LaTeX document. However, the usual make - program is not suited to this purpose for at least two reasons. First + Now the basic task of latexmk is to run the appropriate programs to + make a viewable version of a LaTeX document. However, the usual make + program is not suited to this purpose for at least two reasons. First is that the use of LaTeX involves circular dependencies (e.g., via .aux files), and these cannot be handled by the standard make program. Sec- - ond is that in a large document the set of source files can change - quite frequently, particularly with included graphics files; in this - situation keeping a Makefile manually updated is inappropriate and - error-prone, especially when the dependencies can be determined auto- + ond is that in a large document the set of source files can change + quite frequently, particularly with included graphics files; in this + situation keeping a Makefile manually updated is inappropriate and + error-prone, especially when the dependencies can be determined auto- matically. Latexmk solves both of these problems robustly. - Thus for many standard LaTeX documents latexmk can be used by itself - without the make program. In a complex project it simply needs to be - suitably configured. A standard configuration would be to define cus- - tom dependencies to make graphics files from their source files (e.g., - as created by the xfig program). Custom dependencies are latexmk's + Thus for many standard LaTeX documents latexmk can be used by itself + without the make program. In a complex project it simply needs to be + suitably configured. A standard configuration would be to define cus- + tom dependencies to make graphics files from their source files (e.g., + as created by the xfig program). Custom dependencies are latexmk's equivalent of pattern rules in Makefiles. - Nevertheless there are projects for which a Makefile is appropriate, - and it is useful to know how to use latexmk from a Makefile. A typical - example would be to generate documentation for a software project. - Potentially the interaction with the rest of the rules in the Makefile - could be quite complicated, for example if some of the source files for - a LaTeX document are generated by the project's software. - In this section, I give a couple of examples of how latexmk can be use- - fully invoked from a Makefile. The examples use specific features of - current versions of GNU make, which is the default on both linux and - OS-X systems. They may need modifications for other versions of make. - The simplest method is simply to delegate all the relevant tasks to + 20 November 2017 55 - 19 January 2017 53 - +LATEXMK(1) General Commands Manual LATEXMK(1) -LATEXMK(1) General Commands Manual LATEXMK(1) + Nevertheless there are projects for which a Makefile is appropriate, + and it is useful to know how to use latexmk from a Makefile. A typical + example would be to generate documentation for a software project. + Potentially the interaction with the rest of the rules in the Makefile + could be quite complicated, for example if some of the source files for + a LaTeX document are generated by the project's software. + In this section, I give a couple of examples of how latexmk can be use- + fully invoked from a Makefile. The examples use specific features of + current versions of GNU make, which is the default on both linux and + OS-X systems. They may need modifications for other versions of make. + The simplest method is simply to delegate all the relevant tasks to latexmk, as is suitable for a straightforward LaTeX document. For this a suitable Makefile is like @@ -3510,39 +3655,51 @@ LATEXMK(1) General Commands Manual LATEXMK(1) %.pdf : %.tex FORCE_MAKE latexmk -pdf -dvi- -ps- $< - (Note: the last line must be introduced by a tab for the Makefile to - function correctly!) Naturally, if making try.pdf from its associated - LaTeX file try.tex were the only task to be performed, a direct use of - latexmk without a Makefile would normally be better. The benefit of - using a Makefile for a LaTeX document would be in a larger project, + (Note: the last line must be introduced by a tab for the Makefile to + function correctly!) Naturally, if making try.pdf from its associated + LaTeX file try.tex were the only task to be performed, a direct use of + latexmk without a Makefile would normally be better. The benefit of + using a Makefile for a LaTeX document would be in a larger project, where lines such as the above would be only be a small part of a larger Makefile. The above example has a pattern rule for making a .pdf file from a .tex - file, and it is defined to use latexmk in the obvious way. There is a + file, and it is defined to use latexmk in the obvious way. There is a conventional default target named "all", with a prerequisite of - try.pdf. So when make is invoked, by default it makes try.pdf. The - only complication is that there may be many source files beyond + try.pdf. So when make is invoked, by default it makes try.pdf. The + only complication is that there may be many source files beyond try.tex, but these aren't specified in the Makefile, so changes in them - will not by themselves cause latexmk to be invoked. Instead, the pat- - tern rule is equipped with a "phony" prerequisite FORCE_MAKE; this has - the effect of causing the rule to be always out-of-date, so that - latexmk is always run. It is latexmk that decides whether any action - is needed, e.g., a rerun of pdflatex. Effectively the Makefile dele- + will not by themselves cause latexmk to be invoked. Instead, the pat- + tern rule is equipped with a "phony" prerequisite FORCE_MAKE; this has + the effect of causing the rule to be always out-of-date, so that + latexmk is always run. It is latexmk that decides whether any action + is needed, e.g., a rerun of pdflatex. Effectively the Makefile dele- gates all decisions to latexmk, while make has no knowledge of the list - of source files except for primary LaTeX file for the document. If - there are, for example, graphics files to be made, these must be made + of source files except for primary LaTeX file for the document. If + there are, for example, graphics files to be made, these must be made by custom dependencies configured in latexmk. - But something better is needed in more complicated situations, for - example, when the making of graphics files needs to be specified by - rules in the Makefile. To do this, one can use a Makefile like the + But something better is needed in more complicated situations, for + example, when the making of graphics files needs to be specified by + rules in the Makefile. To do this, one can use a Makefile like the following: TARGETS = document1.pdf document2.pdf DEPS_DIR = .deps LATEXMK = latexmk -recorder -use-make -deps \ -e 'warn qq(In Makefile, turn off custom dependencies\n);' \ + + + + 20 November 2017 56 + + + + + +LATEXMK(1) General Commands Manual LATEXMK(1) + + -e '@cus_dep_list = ();' \ -e 'show_cus_dep();' all : $(TARGETS) @@ -3555,77 +3712,52 @@ LATEXMK(1) General Commands Manual LATEXMK(1) %.pdf : %.fig fig2dev -Lpdf $< $@ - (Again, the lines containing the commands for the rules should be - - - - 19 January 2017 54 - - - - - -LATEXMK(1) General Commands Manual LATEXMK(1) - - + (Again, the lines containing the commands for the rules should be started with tabs.) This example was inspired by how GNU automake han- dles automatic dependency tracking of C source files. - After each run of latexmk, dependency information is put in a file in - the .deps subdirectory. The Makefile causes these dependency files to + After each run of latexmk, dependency information is put in a file in + the .deps subdirectory. The Makefile causes these dependency files to be read by make, which now has the full dependency information for each - target .pdf file. To make things less trivial it is specificed that - two files document1.pdf and document2.pdf are the targets. The depen- + target .pdf file. To make things less trivial it is specificed that + two files document1.pdf and document2.pdf are the targets. The depen- dency files are .deps/document1.pdfP and .deps/document2.pdfP. - There is now no need for the phony prerequisite for the rule to make + There is now no need for the phony prerequisite for the rule to make .pdf files from .tex files. But I have added a rule to make .pdf files - from .fig files produced by the xfig program; these are commonly used - for graphics insertions in LaTeX documents. Latexmk is arranged to - output a dependency file after each run. It is given the -recorder + from .fig files produced by the xfig program; these are commonly used + for graphics insertions in LaTeX documents. Latexmk is arranged to + output a dependency file after each run. It is given the -recorder option, which improves its detection of files generated during a run of - pdflatex; such files should not be in the dependency list. The -e - options are used to turn off all custom dependencies, and to document - this. Instead the -use-make is used to delegate the making of missing + pdflatex; such files should not be in the dependency list. The -e + options are used to turn off all custom dependencies, and to document + this. Instead the -use-make is used to delegate the making of missing files to make itself. - Suppose in the LaTeX file there is a command \includegraphics{graph}, - and an xfig file "graph.fig" exists. On a first run, pdflatex reports - a missing file, named "graph". Latexmk succeeds in making "graph.pdf" + Suppose in the LaTeX file there is a command \includegraphics{graph}, + and an xfig file "graph.fig" exists. On a first run, pdflatex reports + a missing file, named "graph". Latexmk succeeds in making "graph.pdf" by calling "make graph.pdf", and after completion of its work, it lists "fig.pdf" among the dependents of the file latexmk is making. Then let - "fig.fig" be updated, and then let make be run. Make first remakes + "fig.fig" be updated, and then let make be run. Make first remakes "fig.pdf", and only then reruns latexmk. - Thus we now have a method by which all the subsidiary processing is + Thus we now have a method by which all the subsidiary processing is delegated to make. SEE ALSO - latex(1), bibtex(1). + latex(1), bibtex(1), lualatex(1), pdflatex(1), xelatex(1). BUGS Sometimes a viewer (gv) tries to read an updated .ps or .pdf file after - its creation is started but before the file is complete. Work around: + its creation is started but before the file is complete. Work around: manually refresh (or reopen) display. Or use one of the other preview- ers and update methods. - (The following isn't really a bug, but concerns features of preview- - ers.) Preview continuous mode only works perfectly with certain pre- - viewers: Xdvi on UNIX/Linux works for dvi files. Gv on UNIX/Linux - works for both postscript and pdf. Ghostview on UNIX/Linux needs a - manual update (reopen); it views postscript and pdf. Gsview under MS- - Windows works for both postscript and pdf, but only reads the updated - file when its screen is refreshed. Acroread under UNIX/Linux views - pdf, but the file needs to be closed and reopened to view an updated - version. Under MS-Windows, acroread locks its input file and so the - pdf file cannot be updated. (Remedy: configure latexmk to use suma- - trapdf instead.) - - - 19 January 2017 55 + 20 November 2017 57 @@ -3634,19 +3766,31 @@ BUGS LATEXMK(1) General Commands Manual LATEXMK(1) + (The following isn't really a bug, but concerns features of preview- + ers.) Preview continuous mode only works perfectly with certain pre- + viewers: Xdvi on UNIX/Linux works for dvi files. Gv on UNIX/Linux + works for both postscript and pdf. Ghostview on UNIX/Linux needs a + manual update (reopen); it views postscript and pdf. Gsview under MS- + Windows works for both postscript and pdf, but only reads the updated + file when its screen is refreshed. Acroread under UNIX/Linux views + pdf, but the file needs to be closed and reopened to view an updated + version. Under MS-Windows, acroread locks its input file and so the + pdf file cannot be updated. (Remedy: configure latexmk to use suma- + trapdf instead.) + THANKS TO - Authors of previous versions. Many users with their feedback, and - especially David Coppit (username david at node coppit.org) who made - many useful suggestions that contributed to version 3, and Herbert - Schulz. (Please note that the e-mail addresses are not written in - their standard form to avoid being harvested by worms and viruses.) + Authors of previous versions. Many users with their feedback, and + especially David Coppit (username david at node coppit.org) who made + many useful suggestions that contributed to version 3, and Herbert + Schulz. (Please note that the e-mail addresses are not written in + their standard form to avoid being harvested too easily.) AUTHOR - Current version, by John Collins (username jcc8 at node psu.edu). - (Version 4.52c). + Current version, by John Collins (username jcc8 at node psu.edu). + (Version 4.54). - Released version can be obtained from CTAN: - <http://www.ctan.org/pkg/latexmk/>, and from the author's website + Released version can be obtained from CTAN: + <http://www.ctan.org/pkg/latexmk/>, and from the author's website <http://www.personal.psu.edu/jcc8/latexmk/>. Modifications and enhancements by Evan McLean (Version 2.0) Original script called "go" by David J. Musliner (RCS Version 3.2) @@ -3679,18 +3823,6 @@ AUTHOR - - - - - - - - - - - - - 19 January 2017 56 + 20 November 2017 58 diff --git a/Master/texmf-dist/scripts/latexmk/latexmk.pl b/Master/texmf-dist/scripts/latexmk/latexmk.pl index 0a84e0e647a..343fc01dc6e 100755 --- a/Master/texmf-dist/scripts/latexmk/latexmk.pl +++ b/Master/texmf-dist/scripts/latexmk/latexmk.pl @@ -1,5 +1,7 @@ #!/usr/bin/env perl +# SEE "POSSIBLE BUG" aournd line 2221 + # ?? Still need to fix bcf error issue. # Don't keep looping after error # pvc: Only re-run on USER FILE CHANGE. @@ -121,13 +123,13 @@ use warnings; $my_name = 'latexmk'; $My_name = 'Latexmk'; -$version_num = '4.52c'; -$version_details = "$My_name, John Collins, 19 Jan. 2017"; +$version_num = '4.54'; +$version_details = "$My_name, John Collins, 20 Nov. 2017"; use Config; use File::Basename; use File::Copy; -use File::Glob ':glob'; # Better glob. Does not use space as item separator. +use File::Glob ':bsd_glob'; # Better glob. Does not use space as item separator. use File::Path 2.08 qw( make_path ); use FileHandle; use File::Find; @@ -195,9 +197,43 @@ else { ## ## 12 Jan 2012 STILL NEED TO DOCUMENT some items below ## +## 20 Nov 2017 John Collins Ver. 4.54 +## 18 Nov 2017 John Collins Add item to @file_not_found for generic +## package warning about "No file", as produced +## by glossaries-extra. +## In run_bibtex, make change in environment +## be local, not global. +## 4 Sep 2017 John Collins Restore default of $analyze_input_log_always +## to 1. This restores the default detection +## of certain constructs for dependencies for +## input files in the .log file. See the +## comments on this variable. This corrects +## a problem caused by a change in the +## behavior of lualatex in TeXLive 2017. +## 2 Sep 2017 John Collins Remove insertion of name of deps file in +## list of targets in deps file. +## Don't print deps info in deps mode (unless +## diagnostics on). +## 1 Sep 2017 John Collins Customized default previewers for MSys +## 14 Jul 2017 John Collins Correct collection of timing information so +## that it works even in silent mode +## 14 Jun 2017 John Collins Extra value for $bibtex_use +## 12 Jun 2017 John Collins Change glob to bsd_glob, since +## File::Glob's glob is now deprecated. +## Remove unused glob_list. +## 16 May 2017 John Collins Optimize away current directory string in +## $out_dir and $aux_dir. +## 15 May 2017 John Collins Fix incorrect deletion of non-generated +## aux files. +## 13 May 2017 John Collins Correct ordering of list of options given +## by -help +## 6 Apr 2017 John Collins In deps_list, correct bug in identifying +## generated files. Otherwise, generated files +## may be identified as true source files. ## 19 Jan 2017 John Collins Make -jobname work with -pdfxe and -pdflua -## (v. 4.53c) -## 17 Jan 2017 John Collins Fix bbl file detection bug. +## 18 Jan 2017 John Collins Update to v. 4.53. +## 17 Jan 2017 John Collins Update to v. 4.52b (official release). +## Fix bbl file detection bug. ## Bbl files were previously only identified ## from occurrence as input files in log ## file rather than from fls as well. @@ -299,6 +335,7 @@ $log_wrap = 79; '.*?:\\d*: LaTeX Error: File `([^\\\']*)\\\' not found\\.', '^LaTeX Warning: File `([^\\\']*)\\\' not found', '^Package .* [fF]ile `([^\\\']*)\\\' not found', + '^Package .* No file `([^\\\']*)\\\'', 'Error: pdflatex \(file ([^\)]*)\): cannot find image file', ': File (.*) not found:\s*$', '! Unable to load picture or PDF file \\\'([^\\\']+)\\\'.', @@ -527,12 +564,22 @@ $bibtex = 'bibtex %O %B'; # Switch(es) to make biber & bibtex silent: $biber_silent_switch = '--onlylog'; $bibtex_silent_switch = '-terse'; -$bibtex_use = 1; # Whether to actually run bibtex to update bbl files - # 0: Never run bibtex +$bibtex_use = 1; # Whether to actually run bibtex to update bbl files. + # This variable is also used in deciding whether to + # delete bbl files in clean up operations. + # 0: Never run bibtex. + # Do NOT delete bbl files on clean up. # 1: Run bibtex only if the bibfiles exists # according to kpsewhich, and the bbl files - # appear to be out-of-date + # appear to be out-of-date. + # Do NOT delete bbl files on clean up. + # 1.5: Run bibtex only if the bibfiles exists + # according to kpsewhich, and the bbl files + # appear to be out-of-date. + # Only delete bbl files on clean up if bibfiles exist. # 2: Run bibtex when the bbl files are out-of-date + # Delete bbl files on clean up. + # # In any event bibtex is only run if the log file # indicates that the document uses bbl files. @@ -661,8 +708,8 @@ $MSWin_fudge_break = 1; # Give special treatment to ctrl/C and ctrl/break # System-dependent overrides: # Currently, the cases I have tests for are: MSWin32, cygwin, linux and -# darwin, with the main complications being for MSWin32 and cygwin. -# Special treatment may also be useful for MSYS (for which $^O reports +# darwin, msys, with the main complications being for MSWin32 and cygwin. +# Further special treatment may also be useful for MSYS (for which $^O reports # "msys"). This is another *nix-emulation/system for MSWindows. At # present it is treated as unix-like, but the environment variables # are those of Windows. (The test for USERNAME as well as USER was @@ -846,6 +893,13 @@ elsif ( $^O eq "cygwin" ) { $pid_position = -1; # offset of PID in output of pscmd. # Negative means I cannot use ps } +elsif ( $^O eq "msys" ) { + $pdf_previewer = q[sh -c 'start %S']; + $ps_previewer = q[sh -c 'start %S']; + $dvi_previewer = q[sh -c 'start %S']; + $ps_previewer_landscape = $ps_previewer; + $dvi_previewer_landscape = "$dvi_previewer"; +} else { # Assume anything else is UNIX or clone @@ -1049,10 +1103,26 @@ $silent = 0; # Silence latex's messages? $silence_logfile_warnings = 0; # Do list warnings in log file $kpsewhich_show = 0; # Show calls to and results from kpsewhich $landscape_mode = 0; # default to portrait mode -$analyze_input_log_always = 0; # Always analyze .log for input files in the +$analyze_input_log_always = 1; # Always analyze .log for input files in the # <...> and (...) constructions. Otherwise, only # do the analysis when fls file doesn't exist or is # out of date. + # Under normal circumstances, the data in the fls file + # is reliable, and the test of the log file gets lots + # of false positives; usually $analyze_input_log_always + # is best set to zero. But the test of the log file + # is needed at least in the following situation: + # When a user needs to persuade latexmk that a certain + # file is a source file, and latexmk doesn't otherwise + # find it. User code causes line with (...) to be + # written to log file. One important case is for + # lualatex, which doesn't always generate lines in the + # .fls file for input lua files. (The situation with + # lualatex is HIGHLY version dependent, e.g., between + # 2016 and 2017.) + # To keep backward compatibility with older versions + # of latexmk, the default is to set + # $analyze_input_log_always to 1. # The following two arrays contain lists of extensions (without # period) for files that are read in during a (pdf)LaTeX run but that @@ -1522,6 +1592,7 @@ while ($_ = $ARGV[0]) elsif (/^-bibtex-$/) { $bibtex_use = 0; } elsif (/^-nobibtex$/) { $bibtex_use = 0; } elsif (/^-bibtex-cond$/) { $bibtex_use = 1; } + elsif (/^-bibtex-cond1$/) { $bibtex_use = 1.5; } elsif (/^-c$/) { $cleanup_mode = 2; $cleanup_fdb = 1; $cleanup_only = 1; } elsif (/^-C$/ || /^-CA$/ ) { $cleanup_mode = 1; $cleanup_fdb = 1; $cleanup_only = 1; } elsif (/^-CF$/) { $cleanup_fdb = 1; } @@ -1753,17 +1824,20 @@ if ( $bad_options > 0 ) { warn "$My_name: This is $version_details, version: $version_num.\n", unless $silent; + if ( ($out_dir ne '') && ($aux_dir eq '') ){ $aux_dir = $out_dir; } -# Versions terminating in directory/path separator +# Normalize versions terminating in directory/path separator +# and versions referring to current directory $out_dir1 = $out_dir; $aux_dir1 = $aux_dir; foreach ( $aux_dir1, $out_dir1 ) { if ( ($_ ne '') && ! m([\\/\:]$) ) { $_ .= '/'; } + while ( s[^\.\/][] ) {} } # At least one widely package (revtex4-1) generates a bib file @@ -2190,6 +2264,8 @@ foreach $filename ( @file_list ) my %other_generated = (); my @index_bibtex_generated = (); my @aux_files = (); + my @missing_bib_files = (); + my $bibs_all_exist = 0; $have_fdb = 0; if ( -e $fdb_name ) { print "$My_name: Examining fdb file '$fdb_name' for rules ...\n" @@ -2207,15 +2283,29 @@ foreach $filename ( @file_list ) elsif ( $rule =~ /^(bibtex|biber)/ ) { push @index_bibtex_generated, $$Pdest, "$base.blg"; push @aux_files, $$Psource; - } + if ( $bibtex_use == 1.5) { + foreach ( keys %$PHsource ) { + if ( ( /\.bib$/ ) && (! -e $_) ) { + push @missing_bib_files, $_; + } + } + } + } elsif ( exists $other_generated{$$Psource} ) { - $other_generated{$$Pdest}; +# print "=========== CHECKING: source file of rule '$rule', '$$Psource'\n", +# " is a generated file.\n"; + ## OLD with apparent bug: + #$other_generated{$$Pdest}; } + foreach my $key (keys %$PHdest) { + $other_generated{$key} = 1; + } }, sub { # Find generated files at source file level if ( $file =~ /\.aux$/ ) { push @aux_files, $file; } } - ); + ); + if ($#missing_bib_files == -1) { $bibs_all_exist = 1; } } elsif ( -e $log_name ) { # No fdb file, but log file exists, so do inferior job by parse_log @@ -2242,21 +2332,34 @@ foreach $filename ( @file_list ) if ( ($go_mode == 2) && !$silent ) { warn "$My_name: Removing all generated files\n" unless $silent; } - if ($bibtex_use < 2) { - delete $generated_exts_all{'bbl'}; + my $keep_bbl = 1; + if ( ($bibtex_use > 1.6) + || + ( ($bibtex_use == 1.5) && ($bibs_all_exist) ) + ) { + $keep_bbl = 0; + } + if ($keep_bbl) { + delete $generated_exts_all{'bbl'}; } # Convert two arrays to hashes: my %index_bibtex_generated = (); my %aux_files = (); + my %aux_files_to_save = (); foreach (@index_bibtex_generated) { $index_bibtex_generated{$_} = 1 - unless ( /\.bbl$/ && ($bibtex_use < 2) ); + unless ( /\.bbl$/ && ($keep_bbl) ); delete( $other_generated{$_} ); } foreach (@aux_files) { - $aux_files{$_} = 1; - delete( $other_generated{$_} ); + if (exists $other_generated{$_} ) { + $aux_files{$_} = 1; + } + else { + $aux_files_to_save{$_} = 1; + } } + if ($diagnostics) { show_array( "For deletion, the following were determined from fdb file or log file:\n" ." Generated (from makeindex and bibtex):", @@ -2265,9 +2368,12 @@ foreach $filename ( @file_list ) show_array( " Other generated files:\n" ." (only deleted if \$cleanup_includes_generated is set): ", keys %other_generated ); - show_array( " Yet other generated files:\n", + show_array( " Yet other generated files are specified by patterns:\n". + " Explicit pattern with %R or root-filename.extension:", keys %generated_exts_all ); + show_array( " Aux files to SAVE and not delete:", keys %aux_files_to_save ); } + &cleanup1( $aux_dir1, $fdb_ext, 'blg', 'ilg', 'log', 'aux.bak', 'idx.bak', split('\s+',$clean_ext), keys %generated_exts_all @@ -3249,8 +3355,8 @@ sub cleanup1 { my $dir = fix_pattern( shift ); my $root_fixed = fix_pattern( $root_filename ); foreach (@_) { - (my $name = /%R/ ? $_ : "%R.$_") =~ s/%R/$dir$root_fixed/; - unlink_or_move( glob( "$name" ) ); + (my $name = /%R/ ? $_ : "%R.$_") =~ s/%R/${dir}${root_fixed}/; + unlink_or_move( bsd_glob( "$name" ) ); } } #END cleanup1 @@ -3370,7 +3476,9 @@ sub print_help " - Currently this only works with MiKTeX\n", " -bibtex - use bibtex when needed (default)\n", " -bibtex- - never use bibtex\n", - " -bibtex-cond - use bibtex when needed, but only if the bib files exist\n", + " -bibtex-cond - use bibtex when needed, but only if the bib file exists\n", + " -bibtex-cond1 - use bibtex when needed, but only if the bib file exists;\n", + " on cleanup delete bbl file only if bib file exists\n", " -bm <message> - Print message across the page when converting to postscript\n", " -bi <intensity> - Set contrast or intensity of banner\n", " -bs <scale> - Set scale for banner\n", @@ -3416,6 +3524,8 @@ sub print_help " give list of warnings after run of (pdf)latex\n", " -logfilewarninglist- or -logfilewarnings- \n", " do not give list of warnings after run of (pdf)latex\n", + " -lualatex - use lualatex for processing files to pdf\n", + " and turn dvi/ps modes off\n", " -M - Show list of dependent files after processing\n", " -MF file - Specifies name of file to receives list dependent files\n", " -MP - List of dependent files includes phony target for each source file.\n", @@ -3472,8 +3582,6 @@ sub print_help " -view=none - no viewer is used\n", " -view=ps - viewer is for ps\n", " -view=pdf - viewer is for pdf\n", - " -lualatex - use lualatex for processing files to pdf\n", - " and turn dvi/ps modes off\n", " -xelatex - use xelatex for processing files to pdf\n", " and turn dvi/ps modes off\n", "\n", @@ -3665,6 +3773,8 @@ sub check_biber_log { sub run_bibtex { my $return = 999; + # Prevent changes we make to environment becoming global: + local %ENV = %ENV; if ( $aux_dir ) { # Use \Q and \E round directory name in regex to avoid interpretation # of metacharacters in directory name: @@ -5919,7 +6029,7 @@ sub deps_list { # Call: deps_list(fh) # List dependent files to file open on fh my $fh = $_[0]; - print $fh "#===Dependents for $filename:\n"; + print $fh "#===Dependents, and related info, for $filename:\n"; my @dest_exts = (); if ($pdf_mode) {push @dest_exts, '.pdf';} if ($dvi_mode) {push @dest_exts, '.dvi';} @@ -5929,25 +6039,35 @@ sub deps_list { my @accessible_all = rdb_accessible( keys %requested_filerules ); rdb_for_some( \@accessible_all, - sub{ + sub{ # foreach (keys %$PHdest) { print "----- $_\n"; } push @generated, keys %$PHdest; }, sub{ $source{$file} = 1; } ); foreach (keys %generated_exts_all) { - (my $name = /%R/ ? $_ : "%R.$_") =~ s/%R/$root_filename/; + (my $name = /%R/ ? $_ : "%R.$_") =~ s/%R/${aux_dir1}${root_filename}/; push @generated, $name; } + show_array( "Generated:", @generated ) if $diagnostics; foreach (@generated) { delete $source{$_}; } + show_array( "Sources:", keys %source ) if $diagnostics; foreach my $ext (@dest_exts) { - if ($deps_file eq '-' ) { - print $fh "${out_dir1}${root_filename}${ext} :"; - } else { - print $fh "${out_dir1}${root_filename}${ext} $deps_file :"; - } + # Don't insert name of deps file in targets. + # The previous behavior of inserting the name of the deps file + # matched the method recommended by GNU make for automatically + # generated prerequisites -- see Sec. "Generating Prerequisites + # Automatically" of GNU make manual (v. 4.2). But this can + # cause problems in complicated cases, and as far as I can see, + # it doesn't actually help, despite the reasoning given. + # The only purpose of the deps file is to to determine source + # files for a particular rule. The files whose changes make the + # deps file out-of-date are the same as those that make the real + # target file (e.g., .pdf) out-of-date. So the GNU method seems + # completely unnecessary. + print $fh "${out_dir1}${root_filename}${ext} :"; foreach (sort keys %source) { print $fh "\\\n $_"; } @@ -6328,7 +6448,7 @@ sub rdb_make1 { if ($bibtex_use == 0) { $bibtex_not_run = 2; } - elsif ($bibtex_use == 1) { + elsif ( ($bibtex_use == 1) || ($bibtex_use == 1.5) ) { foreach ( keys %$PHsource ) { if ( ( /\.bib$/ ) && (! -e $_) ) { push @missing_bib_files, $_; @@ -6474,7 +6594,7 @@ sub rdb_make1 { # Missing output file was reported to be NOT an error $$Pout_of_date = 0; } - elsif ( ($bibtex_use <= 1) && ($bibtex_not_run > 0) ) { + elsif ( ($bibtex_use <= 1.5) && ($bibtex_not_run > 0) ) { # Lack of destination file is not to be treated as an error # for a bibtex rule when latexmk is configured not to treat # this as an error, and the lack of a destination file is the @@ -7769,18 +7889,6 @@ sub Parray { #************************************************************ -sub glob_list { - # Glob a collection of filenames. Sort and eliminate duplicates - # Usage: e.g., @globbed = glob_list(string, ...); - my @globbed = (); - foreach (@_) { - push @globbed, glob; - } - return uniqs( @globbed ); -} - -#================================================== - sub glob_list1 { # Glob a collection of filenames. # But no sorting or elimination of duplicates @@ -7803,7 +7911,7 @@ sub glob_list1 { } else { # This glob fails to work as desired, if the pattern contains spaces. - push @globbed, glob( "$file_spec" ); + push @globbed, bsd_glob( "$file_spec" ); } } return @globbed; @@ -8463,8 +8571,15 @@ sub tempfile1 { sub Run_msg { # Same as Run, but give message about my running warn_running( "Running '$_[0]'" ); + return Run($_[0]); +} #END Run_msg + +#================== + +sub Run { + # This is wrapper around Run_no_time to capture timing information my $time1 = processing_time(); - my ($pid, $return) = Run($_[0]); + my ($pid, $return) = Run_no_time($_[0]); my $time = processing_time() - $time1; push @timings, "'$_[0]': time = $time\n"; return ($pid, $return); @@ -8472,9 +8587,9 @@ sub Run_msg { #================== -sub Run { -# Usage: Run ("command string"); -# or Run ("one-or-more keywords command string"); +sub Run_no_time { +# Usage: Run_no_time ("command string"); +# or Run_no_time ("one-or-more keywords command string"); # Possible keywords: internal, NONE, start, nostart. # # A command string not started by keywords just gives a call to system with diff --git a/Master/texmf-dist/source/support/latexmk/latexmk.bat b/Master/texmf-dist/source/support/latexmk/latexmk.bat index 48e01d6e5e1..f119082adac 100755 --- a/Master/texmf-dist/source/support/latexmk/latexmk.bat +++ b/Master/texmf-dist/source/support/latexmk/latexmk.bat @@ -1,5 +1,5 @@ -Rem Execute latexmk.pl, searching for it in the PATH -Rem Assume perl is in the PATH. If not, you should replace 'perl' by -Rem the full pathname of the perl executable, e.g., 'C:\perl\bin\perl.exe' - -perl -S latexmk.pl %1 %2 %3 %4 %5 %6 %7 %8 %9 +Rem Execute latexmk.pl, searching for it in the PATH
+Rem Assume perl is in the PATH. If not, you should replace 'perl' by
+Rem the full pathname of the perl executable, e.g., 'C:\perl\bin\perl.exe'
+
+perl -S latexmk.pl %1 %2 %3 %4 %5 %6 %7 %8 %9
|