texlive[54786] trunk: latexmk (18apr20)
commits+karl at tug.org
commits+karl at tug.org
Sat Apr 18 22:56:26 CEST 2020
Revision: 54786
http://tug.org/svn/texlive?view=revision&revision=54786
Author: karl
Date: 2020-04-18 22:56:25 +0200 (Sat, 18 Apr 2020)
Log Message:
-----------
latexmk (18apr20)
Modified Paths:
--------------
trunk/Build/source/texk/texlive/linked_scripts/latexmk/latexmk.pl
trunk/Master/texmf-dist/doc/man/man1/latexmk.1
trunk/Master/texmf-dist/doc/man/man1/latexmk.man1.pdf
trunk/Master/texmf-dist/doc/support/latexmk/CHANGES
trunk/Master/texmf-dist/doc/support/latexmk/INSTALL
trunk/Master/texmf-dist/doc/support/latexmk/README
trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/glossary_latexmkrc
trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/sweave_latexmkrc
trunk/Master/texmf-dist/doc/support/latexmk/latexmk.pdf
trunk/Master/texmf-dist/doc/support/latexmk/latexmk.txt
trunk/Master/texmf-dist/scripts/latexmk/latexmk.pl
Added Paths:
-----------
trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/knitr-latexmkrc
trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/pweave-latexmkrc
Modified: trunk/Build/source/texk/texlive/linked_scripts/latexmk/latexmk.pl
===================================================================
--- trunk/Build/source/texk/texlive/linked_scripts/latexmk/latexmk.pl 2020-04-18 20:56:01 UTC (rev 54785)
+++ trunk/Build/source/texk/texlive/linked_scripts/latexmk/latexmk.pl 2020-04-18 20:56:25 UTC (rev 54786)
@@ -124,7 +124,7 @@
# Test for already running previewer gets wrong answer if another
# process has the viewed file in its command line
-## Copyright John Collins 1998-2019
+## Copyright John Collins 1998-2020
## (username jcc8 at node psu.edu)
## (and thanks to David Coppit (username david at node coppit.org)
## for suggestions)
@@ -162,6 +162,32 @@
##
## 12 Jan 2012 STILL NEED TO DOCUMENT some items below
##
+## 16 Apr 2020 John Collins Correct contents of "All targets (...) are up-to-date" message
+## V. 4.69a.
+## 12 Mar 2020 John Collins Version is 4.69
+## 7 Feb 2020 John Collins Report rc files read
+## 6 Feb 2020 John Collins Fix bug when -cd and -outdir are used, and outdir is
+## same as document directory. (Bug is caused by
+## problem in perl module Cwd.)
+## 2,3 Feb 2020 John Collins Correction in find_basename.
+## 31 Jan 2020 John Collins Cleanup sub exit_msg1: incorrect comment etc.
+## Extra @file_not_found entry for message from
+## \input on not-found-file
+## Remove use of $extension_treatment: Too hard to
+## check. Always use what was called 'unix' method.
+## When command-line-specified tex file not found,
+## test for cusdep to make it, then try kpsewhich,
+## and only if all 3 fail report an error.
+## 15 Jan 2020 John Collins Add -MSWinBackSlash -MSWinBackSlash- options to
+## control whether directory separator '\' is
+## used for filenames on command line for
+## called programs under MSWin.
+## 3 Jan 2020 John Collins Add -E option to default command for xdvipdfmx, to
+## match call made by xetex (see XeTeX_ext.c in
+## xetex source). This forces xdvipdfmx to always
+## try to embed fonts, ignoring licensing flags, etc.
+##
+## Current version (4.67, 26 Dec 2019) to CTAN
## 26 Dec 2019 John Collins Change place of setting of $view_file
## Make fully consistent set of options for engines:
## -latex, -latex=...,
@@ -254,8 +280,8 @@
$my_name = 'latexmk';
$My_name = 'Latexmk';
-$version_num = '4.67';
-$version_details = "$My_name, John Collins, 26 Dec. 2019";
+$version_num = '4.69a';
+$version_details = "$My_name, John Collins, 17 Apr. 2020";
use Config;
use File::Basename;
@@ -293,7 +319,7 @@
use File::Find;
use List::Util qw( max );
use Cwd; # To be able to change cwd
-use Cwd "chdir"; # Ensure $ENV{PWD} tracks cwd
+#use Cwd "chdir"; # Ensure $ENV{PWD} tracks cwd. NO NEED, and it messes up -cd -outdir=
use Digest::MD5;
#use strict;
@@ -337,6 +363,7 @@
@file_not_found = (
'^No file\\s*(.*)\\.$',
'^\\! LaTeX Error: File `([^\\\']*)\\\' not found\\.',
+ '^\\! I can\\\'t find file `([^\\\']*)\\\'\\.',
'.*?:\\d*: LaTeX Error: File `([^\\\']*)\\\' not found\\.',
'^LaTeX Warning: File `([^\\\']*)\\\' not found',
'^Package .* [fF]ile `([^\\\']*)\\\' not found',
@@ -653,7 +680,7 @@
$ps2pdf = 'ps2pdf %O %S %D';
## Command to convert xdv file to pdf file
-$xdvipdfmx = 'xdvipdfmx -o %D %O %S';
+$xdvipdfmx = 'xdvipdfmx -E -o %D %O %S';
$xdvipdfmx_silent_switch = '-q';
@@ -669,13 +696,6 @@
# 'auto' ==> set print type according to the printable
# file(s) being made: priority 'ps', 'pdf', 'dvi'
-## Which treatment of default extensions and filenames with
-## multiple extensions is used, for given filename on
-## tex/latex's command line? See sub find_basename for the
-## possibilities.
-## Current tex's treat extensions like UNIX teTeX:
-$extension_treatment = 'unix';
-
# Viewers. These are system dependent, so default to none:
$pdf_previewer = $ps_previewer = $ps_previewer_landscape = $dvi_previewer = $dvi_previewer_landscape = "NONE";
@@ -914,6 +934,8 @@
# NT executables.
$tmpdir = $ENV{TMPDIR} || $ENV{TEMP} || '.';
+ # Which rc files did I read?
+ @rc_files_read = ();
## List of possibilities for the system-wide initialization file.
## The first one found (if any) is used.
## We could stay with MSWin files here, since cygwin perl understands them
@@ -1676,7 +1698,6 @@
" and in that case it should be a regular text file, not a directory.\n";
}
elsif ( -e $rc_file ) {
- #print "===Reading rc file \"$rc_file\" ...\n";
process_rc_file( $rc_file );
return;
}
@@ -1801,6 +1822,8 @@
shift;
}
elsif ( /^-MP$/ ) { $dependents_phony = 1; }
+ elsif ( /-MSWinBackSlash$/ ) { $MSWin_back_slash = 1; }
+ elsif ( /-MSWinBackSlash-$/ ) { $MSWin_back_slash = 0; }
elsif (/^-new-viewer$/) {
$new_viewer_always = 1;
}
@@ -1990,6 +2013,9 @@
}
}
+show_array( "Rc files read:", @rc_files_read )
+ unless ( $silent && ! $diagnostics );
+
if ( $bad_options > 0 ) {
&exit_help( "Bad options specified" );
}
@@ -2413,7 +2439,7 @@
($filename, $path) = fileparse( $filename );
warn "$My_name: Changing directory to '$path'\n"
if !$silent;
- pushd( $path );
+ pushd( dirname_no_tail( $path ) );
}
else {
$path = '';
@@ -2880,6 +2906,8 @@
# Normalize versions terminating in directory/path separator
# and versions referring to current directory
# These actions in a subroutine so they can be used elsewhere.
+ $out_dir = dirname_no_tail( $out_dir );
+ $aux_dir = dirname_no_tail( $aux_dir );
$out_dir1 = $out_dir;
$aux_dir1 = $aux_dir;
foreach ( $aux_dir1, $out_dir1 ) {
@@ -3410,84 +3438,76 @@
# 2 - Where to place base file
# 3 - Where to place tex file
# Returns non-zero if tex file does not exist
- #
- # The rules for determining this depend on the implementation of TeX.
- # The variable $extension_treatment determines which rules are used.
- # !!!!!!!! I still need to implement use of kpsewhich to match behavior
- # of (pdf)latex correctly.
+ my $fail = 0;
+ local ( $given_name, $base_name, $ext, $path, $tex_name, $source_name );
+ $given_name = $_[0];
+ $source_name = '';
+ $tex_name = $given_name; # Default name if I don't find the tex file
+ ($base_name, $path, $ext) = fileparseB( $given_name );
- local($given_name, $base_name, $ext, $path, $tex_name);
- $given_name = $_[0];
- if ( "$extension_treatment" eq "miktex_old" ) {
- # Miktex v. 1.20d:
- # 1. If the filename has an extension, then use it.
- # 2. Else append ".tex".
- # 3. The basename is obtained from the filename by
- # removing the path component, and the extension, if it
- # exists. If a filename has a multiple extension, then
- # all parts of the extension are removed.
- # 4. The names of generated files (log, aux) are obtained by
- # appending .log, .aux, etc to the basename. Note that
- # these are all in the CURRENT directory, and the drive/path
- # part of the originally given filename is ignored.
- #
- # Thus when the given filename is "\tmp\a.b.c", the tex
- # filename is the same, and the basename is "a".
+ # Treatment of extensions (in TeXLive 2019), with omission of path search:
+ # Exists: always means exists as a file, i.e., not as a directory.
+ # A. Finding of tex file:
+ # 1. If extension is .tex and given_name.tex exists, use it.
+ # 2. Else if given_name.tex exists, use it.
+ # 3. Else if givne_name exists, use it.
+ # B. The base filename is obtained by deleting the path
+ # component and the extension.
+ # C. The names of generated files (log, aux) are obtained by appending
+ # .log, .aux, etc to the basename. Note that these are all in the
+ # CURRENT directory (or the output or aux directory, as appropriate).
+ # The drive/path part of the originally given filename is ignored.
- ($base_name, $path, $ext) = fileparse( $given_name, '\..*' );
- if ( "$ext" eq "") { $tex_name = "$given_name.tex"; }
- else { $tex_name = $given_name; }
- $_[1] = $base_name;
- $_[2] = $tex_name;
- }
- elsif ( "$extension_treatment" eq "unix" ) {
- # unix (at least TeXLive 2016) =>
- # A. Finding of tex file:
- # 1. If filename.tex exists, use it,
- # 2. else if kpsewhich finds filename.tex, use it
- # 3. else if filename exists, use it,
- # 4. else if kpsewhich finds filename, use it.
- # (Probably can unify the above by
- # 1'. If kpsewhich finds filename.tex, use result.
- # 2'. else if kpsewhich finds filename, use result.
- # 3'. else report file not found.
- # B. The base filename is obtained by deleting the path
- # component and, if an extension exists, the last
- # component of the extension, even if the extension is
- # null. (A name ending in "." has a null extension.)
- # C. The names of generated files (log, aux) are obtained by
- # appending .log, .aux, etc to the basename. Note that
- # these are all in the CURRENT directory, and the drive/path
- # part of the originally given filename is ignored.
- #
- # Thus when the given filename is "/tmp/a.b.c", there are two
- # cases:
- # a. /tmp/a.b.c.tex exists. Then this is the tex file,
- # and the basename is "a.b.c".
- # b. /tmp/a.b.c.tex does not exist. Then the tex file is
- # "/tmp/a.b.c", and the basename is "a.b".
- # But there are also modifications of this when a file can be
- # found by kpsewhich.
+ # Here we'll do:
+ # 1. Find the tex file by the above method, if possible.
+ # 2. If not, find a custom dependency with a source file that exists to
+ # make the tex file so that after the tex file is made, the above
+ # rules find the tex file.
+ # 3. If that also fails, use kpsewhich on given_name to find the tex
+ # file
+ # 4. If that also fails, report non-existent tex file.
- if ( -f "$given_name.tex" ) {
- $tex_name = "$given_name.tex";
- }
- else {
- $tex_name = "$given_name";
- }
- ($base_name, $path, $ext) = fileparse( $tex_name, '\.[^\.]*' );
- $_[1] = $base_name;
- $_[2] = $tex_name;
- }
- else {
- die "$My_name: Incorrect configuration gives \$extension_treatment=",
- "'$extension_treatment'\n";
- }
- if ($diagnostics) {
- print "Given='$given_name', tex='$tex_name', base='$base_name'\n";
- }
- return ! -e $tex_name;
+
+ if ( ($ext eq '.tex') && (-f $given_name) ) {
+ $tex_name = "$given_name";
+ }
+ elsif ( -f "$given_name.tex" ) {
+ $tex_name = "$given_name.tex";
+ $base_name .= $ext;
+ }
+ elsif ( -f $given_name ) {
+ $tex_name = $given_name;
+ }
+ elsif ( ($ext eq '.tex') && find_cus_dep( $given_name, $source_name ) ) {
+ $tex_name = $given_name;
+ }
+ elsif ( find_cus_dep( "$given_name.tex", \$source_name ) ) {
+ $tex_name = "$given_name.tex";
+ $base_name .= $ext;
+ }
+ elsif ( ($ext =~ /^\..+/) && find_cus_dep( $given_name, $source_name ) ) {
+ $tex_name = $given_name;
+ }
+ else {
+ my @kpse_result = kpsewhich( $given_name );
+ if ($#kpse_result < 0) {
+ $fail = 1;
+ }
+ else {
+ $tex_name = $kpse_result[0];
+ ($base_name) = fileparseB( $tex_name );
+ }
+ }
+
+ $_[1] = $base_name;
+ $_[2] = $tex_name;
+
+ if ($diagnostics) {
+ print "Given='$given_name', tex='$tex_name', base='$base_name', ext= $ext, source='$source_name'\n";
+ }
+ return $fail;
+
} #END find_basename
#************************************************************
@@ -3728,8 +3748,8 @@
# Exit with code 2 if is a syntax error or other problem.
my $rc_file = $_[0];
my $ret_code = 0;
- warn "$My_name: Executing Perl code in file '$rc_file'...\n"
- if $diagnostics;
+ push @rc_files_read, $rc_file;
+
# I could use the do command of perl, but the preceeding -r test
# to get good diagnostics gets the wrong result under cygwin
# (e.g., on /cygdrive/c/latexmk/LatexMk)
@@ -3878,10 +3898,9 @@
sub exit_msg1
{
- # exit_msg1( error_message, retcode [, action])
+ # exit_msg1( error_message, retcode )
# 1. display error message
- # 2. if action set, then restore aux file
- # 3. exit with retcode
+ # 2. exit with retcode
warn "\n------------\n";
warn "$My_name: $_[0].\n";
warn "-- Use the -f option to force complete processing.\n";
@@ -3985,6 +4004,10 @@
" -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",
+ " -MSWinBackSlash under MSWin use backslash (\\) for directory separators\n",
+ " for filenames given to called programs\n",
+ " -MSWinBackSlash- under MSWin use forward slash (/) for directory separators\n",
+ " for filenames given to called programs\n",
" -new-viewer - in -pvc mode, always start a new viewer\n",
" -new-viewer- - in -pvc mode, start a new viewer only if needed\n",
" -nobibtex - never use bibtex\n",
@@ -5396,6 +5419,30 @@
#************************************************************
+sub dirname_no_tail {
+ my $dirname = $_[0];
+# print "DNT1 = '$dirname'\n";
+ foreach ($dirname) {
+ # Normalize name to use / to separate directory components:
+ # (Note both / and \ are allowed under MSWin.)
+ s(\\)(/)g;
+ # Change multiple trailing / to single /
+ # (Note internal // or \\ can have special meaning on MSWin)
+ s(/+$)(/);
+ # Remove trailing /,
+ # BUT **not** if that changes the semantics, i.e., if name is "/" or "C:/".
+ if ( m(/$) ) {
+ if ( ( ! m(^/+$) ) && ( ! m(:/+$) ) ) {
+ s(/$)();
+ }
+ }
+ }
+# print "DNT2 = '$dirname'\n";
+ return $dirname;
+}
+
+#************************************************************
+
sub clean_filename {
# Convert quoted filename as found in log file to filename without quotes
# Allows arbitrarily embedded double-quoted substrings, includes the
@@ -5427,13 +5474,17 @@
# (Note both / and \ are allowed under MSWin.)
foreach ($cwd, $file, @dirs) {
s(\\)(/)g;
+ $_ = dirname_no_tail( $_ );
}
# Remove initial component equal to current working directory.
# Use \Q and \E round directory name in regex to avoid interpretation
# of metacharacters in directory name:
foreach my $dir ( @dirs, '.', $cwd ) {
- if ( $file =~ s(^\Q$dir\E/)() ) {
- last;
+ if ( $dir =~ /^\s*$/ ) {
+ next;
+ }
+ if ( $file =~ s(^\Q$dir\E/)() ) {
+ last;
}
}
return $file;
@@ -6172,6 +6223,7 @@
}
&parse_log;
+
my $missing_dirs = 'none'; # Status of missing directories
if (@missing_subdirs) {
$missing_dirs = 'success';
@@ -6639,7 +6691,7 @@
foreach my $dep (@cus_dep_list){
my ($fromext,$toext) = split('\s+',$dep);
if ( ( "$ext" eq "$toext" )
- && ( -e "$path$base.$fromext" )
+ && ( -f "$path$base.$fromext" )
) {
# Source file for the missing file exists
# So we have a real include file, and it will be made
@@ -6657,7 +6709,7 @@
# and $_ doesn't have an extension
foreach my $dep (@cus_dep_list){
my ($fromext,$toext) = split('\s+',$dep);
- if ( -e "$path$base.$fromext" ) {
+ if ( -f "$path$base.$fromext" ) {
# Source file for the missing file exists
# So we have a real include file, and it will be made
# next time by &rdb__dependents
@@ -6664,7 +6716,7 @@
$new_includes{"$path$base.$toext"} = 1;
# next MISSING_FILE;
}
- if ( -e "$path$base.$toext" ) {
+ if ( -f "$path$base.$toext" ) {
# We've found the extension for the missing file,
# and the file exists
$new_includes{"$path$base.$toext"} = 1;
@@ -7265,8 +7317,10 @@
print "$My_name: Errors, so I did not complete making targets\n";
}
else {
+# local @dests = ( keys %current_primaries, @pre_primary, @post_primary, @unusual_one_time );
+ local @rules = ( keys %current_primaries, @post_primary, @unusual_one_time );
local @dests = ();
- rdb_for_some( [@_], sub{ push @dests, $$Pdest if ($$Pdest); } );
+ rdb_for_some( [@rules], sub{ push @dests, $$Pdest if ($$Pdest); } );
print "$My_name: All targets (@dests) are up-to-date\n";
}
}
@@ -7440,7 +7494,7 @@
$rules_applied{$rule} = 1;
$runs++;
- $pass{$rule}++;
+ $pass{$rule}++;
if ($bibtex_not_run > 0) {
if ($bibtex_not_run == 1 ) {
show_array ("$My_name: I WON'T RUN '$rule' because I don't find the following files:",
@@ -7449,7 +7503,7 @@
elsif ($bibtex_not_run == 2 ) {
warn "$My_name: I AM CONFIGURED/INVOKED NOT TO RUN '$rule'\n";
}
- $return = &rdb_dummy_run1;
+ $return = &rdb_dummy_run0;
}
else {
warn_running( "Run number $pass{$rule} of rule '$rule'" );
@@ -7822,7 +7876,7 @@
#-----------------
-sub rdb_dummy_run1 {
+sub rdb_dummy_run0 {
# Assumes contexts for: rule.
# Update rule state as if the rule ran successfully,
# but don't run the rule.
@@ -7844,7 +7898,7 @@
$$Pout_of_date = $$Pout_of_date_user = 0;
return 0;
-} # END rdb_dummy_run1
+} # END rdb_dummy_run0
#-----------------
@@ -9211,8 +9265,6 @@
#************************************************************
sub find_file1 {
-#?? Need to use kpsewhich, if possible
-
# Usage: find_file1(name, ref_to_array_search_path)
# Modified find_file, which doesn't die.
# Given filename and path, return array of:
@@ -9407,6 +9459,29 @@
####################################################
+sub find_cus_dep {
+ # Usage find_cus_dep( dest, source )
+ # Given dest, if a cus_dep to make it is found, set source.
+ # Return 1 or 0 on success or failure.
+ #
+ my $dest = $_[0];
+ my ($base, $path, $ext) = fileparseB( $dest );
+ $ext =~ s/^\.//;
+ if (! $ext ) { return 0; }
+ foreach my $dep ( @cus_dep_list ) {
+ my ($fromext, $toext) = split( '\s+', $dep );
+ if ( ( "$ext" eq "$toext" ) && ( -f "$path$base.$fromext" ) ) {
+ # We have a way of making $dest
+ $_[1] = "$path$base.$fromext";
+ return 1
+ }
+ }
+ return 0;
+}
+
+####################################################
+####################################################
+
sub add_aux_hook {
# Usage: add_aux_hook( sub_name )
# Add the name subroutine to the array of hooks for
@@ -9975,7 +10050,7 @@
sub pushd {
push @dir_stack, [cwd(), $cache{cwd}];
if ( $#_ > -1) {
- chdir $_[0];
+ chdir dirname_no_tail( $_[0] );
&cache_good_cwd;
}
}
Modified: trunk/Master/texmf-dist/doc/man/man1/latexmk.1
===================================================================
--- trunk/Master/texmf-dist/doc/man/man1/latexmk.1 2020-04-18 20:56:01 UTC (rev 54785)
+++ trunk/Master/texmf-dist/doc/man/man1/latexmk.1 2020-04-18 20:56:25 UTC (rev 54786)
@@ -1,4 +1,4 @@
-.TH LATEXMK 1 "26 December 2019" ""
+.TH LATEXMK 1 "17 April 2020" ""
.SH NAME
latexmk \- generate LaTeX document
.SH SYNOPSIS
@@ -694,6 +694,32 @@
files without updating the Makefile to match.
.TP
+.B -MSWinBackSlash
+This option only has an effect when \fIlatexmk\fR is running under
+MS-Windows. This is that when \fIlatexmk\fR runs a command under
+MS-Windows, the Windows standard directory separator "\\" is used to
+separate directory components in a file name. Internally, \fIlatexmk\fR
+uses "/" for the directory separator character, which is the character used
+by Unix-like systems.
+
+This is the default behavior. However the default may have been overridden
+by a configuration file (latexmkrc file) which sets
+\fI$MSWin_back_slash=0\fR.
+
+.TP
+.B -MSWinBackSlash-
+This option only has an effect when \fIlatexmk\fR is running under
+MS-Windows. This is that when \fIlatexmk\fR runs a command under
+MS-Windows, the substitution of "\\" for the separator character between
+directory components of a file name is \fInot\fR done. Instead the forward
+slash "/" is used, the same as on Unix-like systems. This is acceptable in
+most situations under MS-Windows, provided that filenames are properly
+quoted, as \fIlatexmk\fR does by default.
+
+See the documentation for the configuration variable
+\fI$MSWin_back_slash\fR for more details.
+
+.TP
.B -new-viewer
When in continuous-preview mode, always start a new viewer to view the
generated file. By default, \fIlatexmk\fR will, in continuous-preview
@@ -2677,20 +2703,26 @@
.TP
.B $MSWin_back_slash [1]
This configuration variable only has an effect when \fIlatexmk\fR 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, \fIlatexmk\fR uses "/" for the directory separator
-character, which is the character used by Unix-like systems.
+running under MS-Windows. With the default value of 1 for this variable,
+when a command is executed under MS-Windows, \fIlatexmk\fR substitutes "\\"
+for the separator character between components of a directory name.
+Internally, \fIlatexmk\fR uses "/" for the directory separator character,
+which is the character used by Unix-like systems.
-For many programs under MS-Windows, both "\\" and "/" are acceptable
-as the directory separator character. But some programs only accept
-"\\" on the command line. So for safety \fIlatexmk\fR 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 software is implemented using Cygwin, which provides
-a Unix-like environment inside MS-Windows.)
+For almost all programs and for almost all filenames under MS-Windows, both
+"\\" and "/" are acceptable as the directory separator character, provided
+at least that filenames are properly quoted. But it is possible that
+programs exist that only accept "\\" on the command line, since that is the
+standard directory separator for MS-Windows. So for safety \fIlatexmk\fR
+makes the substitution from "/" to "\\", by default.
+
+However there are also programs on MS-Windows for which a back slash "\\"
+is interpreted differently than as a directory separator; for these the
+directory separator should be "/". Programs with this behavior include all
+the *latex programs in the TeXLive implementation (but not the MiKTeX
+implementation). Hence if you use TeXLive on MS-Windows, then
+\fI$MSWin_back_slash\fR should be set to zero.
+
.TP
.B $new_viewer_always [0]
This variable applies to \fIlatexmk\fR \fBonly\fR in
@@ -3181,7 +3213,7 @@
commands isn't set.)
.TP
-.B $xdvipdfmx ["xdvipdfmx -o %D %O %S"]
+.B $xdvipdfmx ["xdvipdfmx -E -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).
@@ -3842,7 +3874,7 @@
harvested too easily.)
.SH AUTHOR
Current version, by John Collins (username jcc8 at node psu.edu).
-(Version 4.67).
+(Version 4.69a).
Released version can be obtained from CTAN:
<http://www.ctan.org/pkg/latexmk/>, and from the
Modified: trunk/Master/texmf-dist/doc/man/man1/latexmk.man1.pdf
===================================================================
(Binary files differ)
Modified: trunk/Master/texmf-dist/doc/support/latexmk/CHANGES
===================================================================
--- trunk/Master/texmf-dist/doc/support/latexmk/CHANGES 2020-04-18 20:56:01 UTC (rev 54785)
+++ trunk/Master/texmf-dist/doc/support/latexmk/CHANGES 2020-04-18 20:56:25 UTC (rev 54786)
@@ -702,3 +702,24 @@
If there were missing subdirectories in output/aux directories, and these
were successfully created, then ignore error from *latex, since rerun
may succeed.
+
+From v. 4.67 to 4.69a
+ Add -E option to default command for xdvipdfmx, to match call made
+ by xetex. This forces xdvipdfmx to always try to embed fonts.
+ Add -MSWinBackSlash -MSWinBackSlash- options (and corresponding
+ configuration variable $MSWin_back_slash) to control whether
+ directory separator '\' is used for filenames on command line for
+ called programs under MSWin. -MSWinBackSlash- needs to be used
+ when TeXLive is used on MSWin and the TeX filename includes a
+ directory component.
+ When command-line-specified tex file not found, test for cusdep to
+ make it, then try kpsewhich, and only if all 3 fail report an
+ error.
+ Remove use of $extension_treatment: Too hard to check. Always use
+ what was called 'unix' method, which all *latex implementations
+ now use.
+ Improve some warning messages.
+ Fix bug when -cd and -outdir are used, and outdir is same as
+ document directory. (Bug is caused by problem in perl module
+ Cwd.)
+ Report rc files read
Modified: trunk/Master/texmf-dist/doc/support/latexmk/INSTALL
===================================================================
--- trunk/Master/texmf-dist/doc/support/latexmk/INSTALL 2020-04-18 20:56:01 UTC (rev 54785)
+++ trunk/Master/texmf-dist/doc/support/latexmk/INSTALL 2020-04-18 20:56:25 UTC (rev 54786)
@@ -1,6 +1,6 @@
INSTALLING latexmk
==================
- (Version 4.67, 26 December 2019)
+ (Version 4.69a, 17 April 2020)
John Collins
Physics Department
Modified: trunk/Master/texmf-dist/doc/support/latexmk/README
===================================================================
--- trunk/Master/texmf-dist/doc/support/latexmk/README 2020-04-18 20:56:01 UTC (rev 54785)
+++ trunk/Master/texmf-dist/doc/support/latexmk/README 2020-04-18 20:56:25 UTC (rev 54786)
@@ -1,5 +1,5 @@
-Latexmk, version 4.67, 26 December 2019
------------------------------------
+Latexmk, version 4.69a, 17 April 2020
+-------------------------------------
Latexmk completely automates the process of generating a LaTeX
document. Essentially, it is a highly specialized cousin of the
@@ -87,8 +87,8 @@
John Collins
---------------------------- "latexmk -h" ----------------------------
-===== Set bibtex_fudge = 0 ===
-Latexmk 4.67: Automatic LaTeX document generation routine
+------ TO STDOUT from JCC's latexmkrc
+Latexmk 4.69a: Automatic LaTeX document generation routine
Usage: latexmk [latexmk_options] [filename ...]
@@ -151,6 +151,10 @@
-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.
+ -MSWinBackSlash under MSWin use backslash (\) for directory separators
+ for filenames given to called programs
+ -MSWinBackSlash- under MSWin use forward slash (/) for directory separators
+ for filenames given to called programs
-new-viewer - in -pvc mode, always start a new viewer
-new-viewer- - in -pvc mode, start a new viewer only if needed
-nobibtex - never use bibtex
Modified: trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/glossary_latexmkrc
===================================================================
--- trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/glossary_latexmkrc 2020-04-18 20:56:01 UTC (rev 54785)
+++ trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/glossary_latexmkrc 2020-04-18 20:56:25 UTC (rev 54786)
@@ -1,11 +1,9 @@
-# This shows how to use
-# the glossaries package (http://www.ctan.org/pkg/glossaries)
-# the glossaries-extra package (http://www.ctan.org/pkg/glossaries-extra)
-# with latexmk.
+# This shows how to use the glossaries package
+# (http://www.ctan.org/pkg/glossaries) and the glossaries-extra package
+# (http://www.ctan.org/pkg/glossaries-extra) with latexmk.
# N.B. There is also the OBSOLETE glossary package
-# (http://www.ctan.org/pkg/glossary), which has some differences. See items
-# 2 and 3
+# (http://www.ctan.org/pkg/glossary), which has some differences. See item 2.
# 1. If you use the glossaries or the glossaries-extra package, then you use:
@@ -21,22 +19,26 @@
}
-# 2. If you use the OBSOLETE glossary package, then you can do
+# 2. If you use the OBSOLETE glossary package, then you can do the following:
+# (Note that the code lines are commented out to avoid trouble when this
+# file is simply copied into a latexmkrc or this file is arranged to be
+# read by latexmk, and one of the modern packages glossaries and
+# glossaries-extra is used.)
- add_cus_dep( 'glo', 'gls', 0, 'makeglo2gls' );
- sub makeglo2gls {
- system("makeindex -s \"$_[0].ist\" -t \"$_[0].glg\" -o \"$_[0].gls\" \"$_[0].glo\"" );
- }
+ ## For the main glossary:
+ #add_cus_dep( 'glo', 'gls', 0, 'makeglo2gls' );
+ #sub makeglo2gls {
+ # system("makeindex -s \"$_[0].ist\" -t \"$_[0].glg\" -o \"$_[0].gls\" \"$_[0].glo\"" );
+ #}
-# 2. If you use the OBSOLETE glossary package, then you can do
-# the following for acronyms:
-
- # ONLY FOR PACKAGE glossary, NOT FOR glossaries and glossaries-extra
- add_cus_dep( 'acr', 'acn', 0, 'makeacr2acn' );
- sub makeacr2acn {
- system( "makeindex -s \"$_[0].ist\" -t \"$_[0].alg\" -o \"$_[0].acn\" \"$_[0].acr\"" );
- }
-
-# ===> WARNING: In the current glossaries and glossaries-extra packages
-# the roles of the .acr and .acn files are exchanged, so the above
-# code will fail with the more modern packages.
+ ## For acronyms:
+ ##
+ ## ===> WARNING: The code below is ONLY FOR PACKAGE glossary, NOT FOR
+ ## glossaries and glossaries-extra. In the current glossaries and
+ ## glossaries-extra packages the roles of the .acr and .acn files are
+ ## exchanged compared with the old glossary package. Hence the the
+ ## code below will fail with the more modern packages.
+ #add_cus_dep( 'acr', 'acn', 0, 'makeacr2acn' );
+ #sub makeacr2acn {
+ # system( "makeindex -s \"$_[0].ist\" -t \"$_[0].alg\" -o \"$_[0].acn\" \"$_[0].acr\"" );
+ #}
Added: trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/knitr-latexmkrc
===================================================================
--- trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/knitr-latexmkrc (rev 0)
+++ trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/knitr-latexmkrc 2020-04-18 20:56:25 UTC (rev 54786)
@@ -0,0 +1,100 @@
+# This code was provided by Michael Stewart, Feb. 2020.
+#
+# Knitr is a successor to Sweave (see sweave_latexmkrc) which allows the embedding
+# of R code (and its output) into LaTeX files. A .Rnw file (including LaTeX code
+# and R code) is "knitted" to produce a LaTeX file, which also includes the output
+# obtained from running the R code. Knitr also works with other plain-text markup
+# languages (e.g. Rmarkdown and brew) but they are not supported here.
+# See https://yihui.org/knitr for more information.
+#
+# This latexmkrc file permits using knitr, allowing SyncTeX to work properly.
+# It also works for a multiple-file project under one caveat: the "native"
+# knitr child document inclusion method which uses chunks like
+#
+# <<child='child.Rnw'>>=
+# @
+#
+# is *not* used. Rather, each .Rnw file is "knitted" in a standalone fashion
+# and the "inputting" is done purely at the LaTeX phase.
+#
+# Thus if we have a main document "main.Rnw" and a child document "child.Rnw"
+# the successful workflow is:
+# 0. put a line
+#
+# \input child.tex
+#
+# at the deisred location in main.Rnw;
+# 1. knit('main.Rnw') # to produce main.tex (which inherits the \input line above);
+# 2. knit('child.Rnw') # to produce child.tex;
+# 3. pdflatex -synctex=1 main.tex;
+# 4. patchSynctex('main.Rnw');
+# 5. patchSynctex('child.Rnw',syncfile='main');
+# All steps except 3. are R commands (note that the add-on R package "patchSynctex"
+# needs to be installed); 3. is an ordinary shell command.
+#
+# The configuration below handles both single-file and multiple-file projects (using
+# the workflow described above).
+
+# In the line below replace 'main.tex' with the name of the main *LaTeX* file.
+# This line is optional for single-file projects; using it means that latexmk
+# may be invoked without a filename, even if the file main.tex doesn't yet exist:
+#
+# $ latexmk
+#
+# If the line is not used, and the target LaTeX file does not yet exist,
+# its name must be supplied, e.g.:
+#
+# $ latexmk main
+#
+# It is compulsory for multiple file projects, so we avoid running pdflatex
+# on child documents.
+ at default_files=('main.tex');
+
+$pdf_mode=1;
+
+# The definition of $pdflatex below runs pdflatex on the main LaTeX file
+# and runs patchSynctex(...,syncfile='main') once for each .Rnw file appearing
+# in the working directory:
+$pdflatex = "pdflatex -interaction=nonstopmode -synctex=1 %O %B ;"
+ . "Rscript -e \"library(patchSynctex); "
+ . "Rnw.files=system(\\\"ls *.Rnw\\\",intern=T); "
+ . "Rnw.stems=unlist(strsplit(Rnw.files,split=\\\".Rnw\\\")); "
+ . "for (i in 1:length(Rnw.stems)) "
+ . "patchSynctex(Rnw.stems[i],syncfile=\\\"%B\\\",verbose=T)\" " ;
+
+
+# The remaining code defines a custom dependency to ensure that each LaTeX file
+# is updated whenever the corresponding .Rnw file is updated. See below for how
+# to adapt this for use with Sweave instead of knitr.
+add_cus_dep( 'Rnw', 'tex', 0 , 'knit' );
+sub knit {
+ system( "Rscript -e \"library(knitr); "
+ . "opts_knit\\\$set(concordance=T); "
+ . "knitr::knit(\\\"$_[0].Rnw\\\",output=\\\"$_[0].tex\\\")\" " );
+}
+
+# For use with Sweave (rather than knitr) make the following adjustments:
+#
+# 1. Ensure that
+#
+# \SweaveOpts{concordance=T}
+#
+# (possibly with other global options e.g. stylepath=T) appears near the top of each
+# .Rnw file *after* \begin{document} (at the time of writing there seems to be a bug
+# in Sweave() so that this is the only reliable way to pass the global
+# concordance=T option; neither Sweave(...,concordance=T) nor # the setting of the
+# SWEAVE_OPTIONS environment variable seems to work).
+#
+# 2. Replace the last 6 lines of code above this comment block with the commented-out
+# code below:
+#
+#add_cus_dep( 'Rnw', 'tex', 0, 'Sweave');
+#sub Sweave {
+# system("Rscript -e \"Sweave(\\\"$_[0].Rnw\\\")\" ");
+#}
+
+# You will need to uncomment the two lines below if you are using this with a version
+# of latexmk older than version 4.68:
+#$force_mode=1;
+#push @file_not_found, '^\\! I can\\\'t find file `([^\\\']*)\\\'\\.';
+
Added: trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/pweave-latexmkrc
===================================================================
--- trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/pweave-latexmkrc (rev 0)
+++ trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/pweave-latexmkrc 2020-04-18 20:56:25 UTC (rev 54786)
@@ -0,0 +1,6 @@
+# How to use latexmk with pweave to generate tex file
+
+add_cus_dep('texw', 'tex', 0, 'pweave2tex');
+sub pweave2tex {
+ system("pweave -f tex \"$_[0].texw\"");
+}
Modified: trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/sweave_latexmkrc
===================================================================
--- trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/sweave_latexmkrc 2020-04-18 20:56:01 UTC (rev 54785)
+++ trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/sweave_latexmkrc 2020-04-18 20:56:25 UTC (rev 54786)
@@ -25,12 +25,15 @@
# N.B. ===> IMPORTANT NOTES <===
#
-# 1. The patchDVI package for R needs to be installed from R-Forge, as
+# 1. See the comments in knitr-latexmkrc for an alternative and probably better
+# way of using Sweave with latexmk
+#
+# 2. The patchDVI package for R needs to be installed from R-Forge, as
# follows:
#
# install.packages("patchDVI", repos="http://R-Forge.R-project.org")
#
-# 2. In all Sweave (.Rnw) documents, the following lines must be included:
+# 3. In all Sweave (.Rnw) documents, the following lines must be included:
#
# \usepackage{Sweave}
# \SweaveOpts{concordance=TRUE}
Modified: trunk/Master/texmf-dist/doc/support/latexmk/latexmk.pdf
===================================================================
(Binary files differ)
Modified: trunk/Master/texmf-dist/doc/support/latexmk/latexmk.txt
===================================================================
--- trunk/Master/texmf-dist/doc/support/latexmk/latexmk.txt 2020-04-18 20:56:01 UTC (rev 54785)
+++ trunk/Master/texmf-dist/doc/support/latexmk/latexmk.txt 2020-04-18 20:56:25 UTC (rev 54786)
@@ -61,7 +61,7 @@
- 26 December 2019 1
+ 17 April 2020 1
@@ -127,7 +127,7 @@
- 26 December 2019 2
+ 17 April 2020 2
@@ -193,7 +193,7 @@
- 26 December 2019 3
+ 17 April 2020 3
@@ -259,7 +259,7 @@
- 26 December 2019 4
+ 17 April 2020 4
@@ -325,7 +325,7 @@
- 26 December 2019 5
+ 17 April 2020 5
@@ -391,7 +391,7 @@
- 26 December 2019 6
+ 17 April 2020 6
@@ -457,7 +457,7 @@
- 26 December 2019 7
+ 17 April 2020 7
@@ -523,7 +523,7 @@
- 26 December 2019 8
+ 17 April 2020 8
@@ -589,7 +589,7 @@
- 26 December 2019 9
+ 17 April 2020 9
@@ -655,7 +655,7 @@
- 26 December 2019 10
+ 17 April 2020 10
@@ -721,7 +721,7 @@
- 26 December 2019 11
+ 17 April 2020 11
@@ -787,7 +787,7 @@
- 26 December 2019 12
+ 17 April 2020 12
@@ -811,6 +811,32 @@
move header files without updating the Makefile to match.
+ -MSWinBackSlash
+ This option only has an effect when latexmk is running under MS-
+ Windows. This is that when latexmk runs a command under MS-Win-
+ dows, the Windows standard directory separator "\" is used to
+ separate directory components in a file name. Internally, la-
+ texmk uses "/" for the directory separator character, which is
+ the character used by Unix-like systems.
+
+ This is the default behavior. However the default may have been
+ overridden by a configuration file (latexmkrc file) which sets
+ $MSWin_back_slash=0.
+
+
+ -MSWinBackSlash-
+ This option only has an effect when latexmk is running under MS-
+ Windows. This is that when latexmk runs a command under MS-Win-
+ dows, the substitution of "\" for the separator character be-
+ tween directory components of a file name is not done. Instead
+ the forward slash "/" is used, the same as on Unix-like systems.
+ This is acceptable in most situations under MS-Windows, provided
+ that filenames are properly quoted, as latexmk does by default.
+
+ See the documentation for the configuration variable
+ $MSWin_back_slash for more details.
+
+
-new-viewer
When in continuous-preview mode, always start a new viewer to
view the generated file. By default, latexmk will, in continu-
@@ -824,6 +850,18 @@
-new-viewer-
The inverse of the -new-viewer option. It puts latexmk in its
+
+
+
+ 17 April 2020 13
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
normal behavior that in preview-continuous mode it checks for an
already-running previewer.
@@ -850,18 +888,6 @@
See also the -auxdir/-aux-directory options, and the $aux_dir,
$out_dir, and $search_path_separator configuration variables of
-
-
-
- 26 December 2019 13
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
latexmk. In particular, see the documentation of $out_dir for
some complications on what directory names are suitable.
@@ -890,6 +916,18 @@
turns them off.
+
+
+
+ 17 April 2020 14
+
+
+
+
+
+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
@@ -916,18 +954,6 @@
multiple runs to generate a fully up-to-date .xdv file does la-
texmk then call xdvipdfmx to generate the final .pdf file.
-
-
-
- 26 December 2019 14
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
(Note: The reason why latexmk arranges for xelatex to make an
.xdv file instead of the xelatex's default of a .pdf file is as
follows: When the document includes large graphics files, espe-
@@ -958,6 +984,16 @@
the -pdflatex="COMMAND" option.
+
+ 17 April 2020 15
+
+
+
+
+
+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-
@@ -982,18 +1018,6 @@
for pdflatex) see the -latex option.
-
-
-
- 26 December 2019 15
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
-pdflualatex="COMMAND"
Equivalent to -lualatex="COMMAND".
@@ -1024,6 +1048,18 @@
If you already have a suitable command configured, you only need
+
+
+
+ 17 April 2020 16
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
latexmk -pretex='\AtBeginDocument{Message\par}' foo.tex
@@ -1048,18 +1084,6 @@
-pF Postscript file filtering. The argument to this option is a
filter which will generate a filtered postscript file with the
-
-
-
- 26 December 2019 16
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
extension ".psF". All extra processing (e.g. preview, printing)
will then be performed on this filtered postscript file.
@@ -1090,6 +1114,18 @@
-pvc Run a file previewer and continually update the .dvi, .ps,
and/or .pdf files whenever changes are made to source files (see
+
+
+
+ 17 April 2020 17
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
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
@@ -1115,17 +1151,6 @@
mode. It is better to use a different viewer: SumatraPDF and
gsview are good possibilities.
-
-
- 26 December 2019 17
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
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.
@@ -1157,6 +1182,16 @@
Set period of inactivity in minutes for pvc timeout.
+
+ 17 April 2020 18
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
-quiet Same as -silent
@@ -1180,18 +1215,6 @@
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
-
-
-
- 26 December 2019 18
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
instances of the -r and -e options can be used, and they are ex-
ecuted in the order they appear on the command line.
@@ -1223,6 +1246,18 @@
-showextraoptions
Show the list of extra latex and pdflatex options that latexmk
+
+
+
+ 17 April 2020 19
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
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
@@ -1246,18 +1281,6 @@
-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.
-
-
-
- 26 December 2019 19
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
These options do have entries in this documentation. These op-
tions are: -jobname=STRING, -aux-directory=dir, -output-direc-
tory=DIR, -quiet, and -recorder.
@@ -1289,6 +1312,18 @@
ones. This is useful to override special configurations.
The result is that $latex = 'latex %O %S', and similarly for
+
+
+
+ 17 April 2020 20
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
$pdflatex, $lualatex, and $xelatex. (The option -no-pdf needed
for $xelatex is provided automatically, given that %O appears in
the definition.)
@@ -1312,18 +1347,6 @@
gram to try to make the missing files.
Note that the filename may be specified without an extension,
-
-
-
- 26 December 2019 20
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
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
@@ -1357,6 +1380,16 @@
latexmk -usepretex='\AtBeginDocument{Message\par}' foo.tex
+
+ 17 April 2020 21
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
-v, -version
Print version number of latexmk.
@@ -1378,18 +1411,6 @@
be opened.
-
-
-
- 26 December 2019 21
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
-Werror
This causes latexmk to return a non-zero status code if any of
the files processed gives a warning about problems with cita-
@@ -1424,6 +1445,17 @@
This sets the string specifying the command to run xelatex. It
sets the variable $xelatex.
+
+
+ 17 April 2020 22
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
Warning: It is important to ensure that the -no-pdf is used when
xelatex is invoked, since latexmk expects xelatex to produce an
.xdv file, not a .pdf file. If you provide %O in the command
@@ -1444,18 +1476,6 @@
Compatibility between options
-
-
-
- 26 December 2019 22
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
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.
@@ -1489,13 +1509,25 @@
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-
- 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 out-
- put.
+ on the screen and in log files. While there is much that is
+
+
+ 17 April 2020 23
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
+ notoriously verbose in the output of latex (and that is added to by la-
+ texmk), the verbosity is there for a reason: to enable the user to di-
+ agnose 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
+ output.
+
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
@@ -1510,18 +1542,6 @@
tions. (But there is a lot of reading!)
The remainder of these notes consists of ideas for dealing with more
-
-
-
- 26 December 2019 23
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
difficult situations.
d. Further tricks can involve replacing the standard commands that la-
@@ -1557,6 +1577,17 @@
i. Ask a question at tex.stackexchange.com.
+
+
+ 17 April 2020 24
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
j. Or ask me (the author of latexmk). My e-mail is at the end of this
documentation.
@@ -1575,22 +1606,10 @@
tion. The difference in output file type can happen for two reasons:
One is that for latex, pdflatex and lualatex the document itself can
override the defaults. The other is that there may be a configuration,
- or misconfiguration, such that the program that latexmk invokes to
-
-
-
- 26 December 2019 24
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
- compile the document is not the expected one, or is given options in-
- compatible with what latexmk initially expects. (E.g., the -output-
- format=... option could be used with lualatex, or xelatex gets invoked
+ or misconfiguration, such that the program that latexmk invokes to com-
+ pile the document is not the expected one, or is given options incom-
+ patible with what latexmk initially expects. (E.g., the -output-for-
+ mat=... option could be used with lualatex, or xelatex gets invoked
without the -no-pdf option.)
Under latex and pdflatex, control of the output format by the document
@@ -1623,6 +1642,18 @@
to a non-zero value as it is by default. If this variable is zero, a
mismatch of filetypes in the compilation results in an erro.
+
+
+
+ 17 April 2020 25
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
The second condition for latexmk to be able to handle a change of out-
put type is that no explicit requests for .dvi or .ps output files are
made. Explicit requests are by the -dvi and -ps, -print=dvi,
@@ -1644,16 +1675,6 @@
-
- 26 December 2019 25
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
CONFIGURATION/INITIALIZATION (RC) FILES
In this section is explained which configuration files are read by la-
texmk. Subsequent sections "How to Set Variables in Initialization
@@ -1687,6 +1708,18 @@
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
+
+
+
+ 17 April 2020 26
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
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
@@ -1708,18 +1741,6 @@
texmk does not look for an RC file under it.
-
-
-
- 26 December 2019 26
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
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.
@@ -1753,6 +1774,18 @@
$bibtex = 'bibtex %O %B';
+
+
+
+ 17 April 2020 27
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
for the setting of a string variable,
$preview_mode = 1;
@@ -1774,18 +1807,6 @@
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
-
-
-
- 26 December 2019 27
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
these complications.)
You can do much more complicated things, but for this you will need to
@@ -1819,6 +1840,18 @@
The available placeholders are:
+
+
+
+ 17 April 2020 28
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
%A basename of the main tex file. Unlike %R, this is unaffected by
the setting of a jobname by the -jobname option or the $jobname
configuration value.
@@ -1840,18 +1873,6 @@
source file is read.
If the variable $pre_tex_code is the empty string, then %P is
-
-
-
- 26 December 2019 28
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
equivalent to %S.
%R root filename. This is the base name for the main tex file.
@@ -1885,6 +1906,18 @@
UNIX and MS-Windows, i.e., ':', '/' and '\'.
If for some reason you need a literal % character in your string not
+
+
+
+ 17 April 2020 29
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
subject to the above rules, use "%%".
Appropriate quoting will be applied to the filename substitutions, so
@@ -1905,54 +1938,52 @@
$bibtex = 'bibtex %O %B';
- Generally, you should use %B rather than %R. Similarly for most
+ 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.
-
-
- 26 December 2019 29
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
- purposes, the name %T of the primary texfile is not a useful place-
- holder.
-
- 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 re-
- turns 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
+ run detached, so that latexmk gets the previewer running and then re-
+ turns 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
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 de-
- tached. 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
+ tached. 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
problem.
+
+
+ 17 April 2020 30
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
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 en-
@@ -1962,37 +1993,26 @@
%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.)
-
-
- 26 December 2019 30
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
- 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:
@@ -1999,9 +2019,9 @@
$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.
@@ -2010,18 +2030,29 @@
$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:
+
+
+ 17 April 2020 31
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
$latex = 'latex --src-specials %O %S';
- Running a subroutine instead of an external command: Use a specifica-
+ Running a subroutine instead of an external command: Use a specifica-
tion starting with "internal", as in
$latex = 'internal mylatex %O %S';
@@ -2031,42 +2062,30 @@
return system 'latex', @args;
}
- For some of the more exotic possibilities that then become available,
- see the section "ADVANCED CONFIGURATION: Some extra resources and ad-
- vanced 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 ad-
+ vanced 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
-
-
-
- 26 December 2019 31
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
- additional processing you need to do in your special situation, you can
+ Advanced tricks: Normally one specifies a single command for the com-
+ mands invoked by latexmk. Naturally, if there is some complicated ad-
+ ditional 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
+ 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 ex-
tra 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 in-
- cludes 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 in-
+ cludes 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
@@ -2074,48 +2093,47 @@
$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.
LIST OF CONFIGURATION VARIABLES USABLE IN INITIALIZATION FILES
- In this section are specified the variables whose values can be ad-
- justed to configure latexmk. (See the earlier section "Configura-
- tion/Initialization (rc) Files" for the files where the configurations
+ In this section are specified the variables whose values can be ad-
+ justed to configure latexmk. (See the earlier section "Configura-
+ tion/Initialization (rc) Files" for the files where the configurations
are done.)
- Default values are indicated in brackets. Note that for variables that
- are boolean in character, concerning whether latexmk does or does not
- behave in a certain way, a non-zero value, normally 1, indicates true,
- i.e., the behavior occurs, while a zero value indicates a false value,
- i.e., the behavior does not occur.
- $allow_switch [1]
+ 17 April 2020 32
- This controls what happens when the output extension of latex,
- pdflatex, lualatex or xelatex differs from what is expected.
- (The possible extensions are .dvi, .pdf, .xdv.) This can happen
- with the use of the \pdfoutput macro in a document compiled un-
- der latex or pdflatex, or with the use of the \outputmode macro
- under lualatex. It can also happen with certain kinds of incor-
- rect configuration.
- In such a case, latexmk can appropriately adjust its network of
- 26 December 2019 32
+LATEXMK(1) General Commands Manual LATEXMK(1)
+ Default values are indicated in brackets. Note that for variables that
+ are boolean in character, concerning whether latexmk does or does not
+ behave in a certain way, a non-zero value, normally 1, indicates true,
+ i.e., the behavior occurs, while a zero value indicates a false value,
+ i.e., the behavior does not occur.
+ $allow_switch [1]
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ This controls what happens when the output extension of latex,
+ pdflatex, lualatex or xelatex differs from what is expected.
+ (The possible extensions are .dvi, .pdf, .xdv.) This can happen
+ with the use of the \pdfoutput macro in a document compiled un-
+ der latex or pdflatex, or with the use of the \outputmode macro
+ under lualatex. It can also happen with certain kinds of incor-
+ rect configuration.
-
+ In such a case, latexmk can appropriately adjust its network of
rules. The adjustment is made if $allow_switch is on, and if no
request for a dvi or ps file has been made.
@@ -2123,11 +2141,11 @@
$always_view_file_via_temporary [0]
- Whether .ps and .pdf files are initially to be made in a tempo-
- rary directory and then moved to the final location. (This ap-
+ Whether .ps and .pdf files are initially to be made in a tempo-
+ rary directory and then moved to the final location. (This ap-
plies to dvips, dvipdf, and ps2pdf operations, and the filtering
operators on .dvi and .ps files. It does not apply to pdflatex,
- unfortunately, since pdflatex provides no way of specifying a
+ 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
@@ -2137,7 +2155,7 @@
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.
@@ -2144,72 +2162,72 @@
$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
+ 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-
+ 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.)
+ usually $analyze_input_log_always is best set to zero. But the
+ test of the log file is needed at least in the following
- 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)
- 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
+ 17 April 2020 33
- 26 December 2019 33
+LATEXMK(1) General Commands Manual LATEXMK(1)
+ 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 depen-
+ dent, e.g., there was a big change between TeXLive 2016 and
+ TeXLive 2017.)
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ To keep backward compatibility with older versions of latexmk,
+ the default is to set $analyze_input_log_always to 1.
- turn this setting off, i.e., it could set $auto_rc_use to zero
+ $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 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
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
+ 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
+ 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
@@ -2218,40 +2236,40 @@
$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
- black, 1 is white. The default is just right if your toner car-
- tridge isn't running too low.
- $banner_message ["DRAFT"]
- The banner message to print across each page when converting the
- 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.
- This is equivalent to the -bs option.
- @BIBINPUTS
- This is an array variable, now mostly obsolete, that specifies
+ 17 April 2020 34
- 26 December 2019 34
+LATEXMK(1) General Commands Manual LATEXMK(1)
+ 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.
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ $banner_message ["DRAFT"]
+ The banner message to print across each page when converting the
+ 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.
+ This is equivalent to the -bs option.
- directories where latexmk should look for .bib files. By de-
- fault 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.
+ @BIBINPUTS
+ This is an array variable, now mostly obsolete, that specifies
+ directories where latexmk should look for .bib files. By de-
+ fault 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.
The format of the directory names depends on your operating sys-
tem, of course. Examples for setting this variable are:
@@ -2261,16 +2279,16 @@
@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
+ 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.
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
+ 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"]
@@ -2277,112 +2295,113 @@
The biber processing program.
$biber_silent_switch ["--onlylog"]
- Switch(es) for the biber processing program when silent mode is
+ Switch(es) for the biber processing program when silent mode is
on.
$bibtex ["bibtex %O %S"]
The BibTeX processing program.
- $bibtex_fudge [1]
- When using bibtex, whether to take special action to allow bib-
- tex to work when $out_dir or $aux_dir is specified. In May
- 2018, there was planned an update to bibtex to correct a bug,
- after that update, the special action will no longer be re-
- quired.
- $bibtex_silent_switch ["-terse"]
- Switch(es) for the BibTeX processing program when silent mode is
- on.
- $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
+ 17 April 2020 35
- 26 December 2019 35
-
LATEXMK(1) General Commands Manual LATEXMK(1)
- 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
+ $bibtex_fudge [1]
+ When using bibtex, whether to take special action to allow bib-
+ tex to work when $out_dir or $aux_dir is specified. In May
+ 2018, there was planned an update to bibtex to correct a bug,
+ after that update, the special action will no longer be re-
+ quired.
+
+ $bibtex_silent_switch ["-terse"]
+ Switch(es) for the BibTeX processing program when silent mode is
+ on.
+
+ $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 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
+ 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
+ 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
+ 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
+ the bbl files, without testing for the existence of the bib
files; always delete .bbl files in a cleanup.
- Note that the value 1.5 does not work properly if the document
+ Note that the value 1.5 does not work properly if the document
uses biber instead of bibtex. (There's a long story why not.)
$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
+ If nonzero, specifies that cleanup also deletes files that are
detected in the fls file (or failing that, in log file) as being
- generated. It will also include files made from these first
+ generated. It will also include files made from these first
generation generated files.
- This operation is somewhat dangerous, and can have unintended
- consequences, since the files to be deleted are determined from
- a file created by (pdf)latex, which can contain erroneous infor-
- mation. Therefore this variable is turned off by default, and
- then files to be deleted are restricted to those explictly spec-
- ified by patterns configured in the variables clean_ext,
- clean_full_ext, and @generated_exts, together with those very
- standard cases that are hardwired into latexmk (e.g., .log
- files).
+ This operation is somewhat dangerous, and can have unintended
+ consequences, since the files to be deleted are determined from
- $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 ex-
- cept for dep and aux files. (There is also extra cleaning as
- specified 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.
+ 17 April 2020 36
- 26 December 2019 36
+LATEXMK(1) General Commands Manual LATEXMK(1)
+ a file created by (pdf)latex, which can contain erroneous infor-
+ mation. Therefore this variable is turned off by default, and
+ then files to be deleted are restricted to those explictly spec-
+ ified by patterns configured in the variables clean_ext,
+ clean_full_ext, and @generated_exts, together with those very
+ standard cases that are hardwired into latexmk (e.g., .log
+ 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 ex-
+ cept for dep and aux files. (There is also extra cleaning as
+ specified 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
+ 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.
@@ -2394,124 +2413,124 @@
files-%R/*";
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, %R-
- figures*.log, and pythontex-files-FOO/*, where FOO stands for
+ tion is specified, not only is the standard set of files
+ deleted, but also files of the form FOO.out, FOO-blx.bib, %R-
+ figures*.log, and pythontex-files-FOO/*, where FOO stands for
the basename of the file being processed (as in FOO.tex).
- The files to be deleted are relative to the directory specified
- by $aux_dir. (Note that if $out_dir but not $aux_dir is set,
- then in its initialization, latexmk sets $aux_dir equal to
- $out_dir. A normal situation is therefore that $aux_dir equals
- $out_dir, which is the only case supported by TeXLive, unlike
+ The files to be deleted are relative to the directory specified
+ by $aux_dir. (Note that if $out_dir but not $aux_dir is set,
+ then in its initialization, latexmk sets $aux_dir equal to
+ $out_dir. A normal situation is therefore that $aux_dir equals
+ $out_dir, which is the only case supported by TeXLive, unlike
MiKTeX.)
- The filenames specfied for a clean-up operation can refer not
- only to regular files but also to directories. Directories are
+ The filenames specfied for a clean-up operation can refer not
+ only to regular files but also to directories. Directories are
only deleted if they are empty. An example of an application is
- to pythontex, which creates files in a particular directory.
- You can arrange to remove both the files and the directory by
+ to pythontex, which creates files in a particular directory.
+ You can arrange to remove both the files and the directory by
setting
$clean_ext = "pythontex-files-%R pythontex-files-%R";
- See also the variable @generated_exts.
- $clean_full_ext [""]
- Extra extensions of files for latexmk to remove when the -C op-
- tion 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.
- The files specified by $clean_full_ext to be deleted are rela-
- tive to the directory specified by $out_dir.
+ 17 April 2020 37
- $compiling_cmd [""], $failure_cmd [""], $warning_cmd [""], $success_cmd
- [""]
- These variables specify commands that are executed at certain
- points of compilations. One motivation for their existance is
- to allow very useful convenient visual indications of
+LATEXMK(1) General Commands Manual LATEXMK(1)
- 26 December 2019 37
+ See also the variable @generated_exts.
+ $clean_full_ext [""]
+ Extra extensions of files for latexmk to remove when the -C op-
+ tion 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.
+ The files specified by $clean_full_ext to be deleted are rela-
+ tive to the directory specified by $out_dir.
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ $compiling_cmd [""], $failure_cmd [""], $warning_cmd [""], $success_cmd
+ [""]
- compilation status even when the window receiving the screen
- output of the compilation is hidden. This is particularly use-
- ful in preview-continuous mode.
+ These variables specify commands that are executed at certain
+ points of compilations. One motivation for their existance is
+ to allow very useful convenient visual indications of compila-
+ tion status even when the window receiving the screen output of
+ the compilation is hidden. This is particularly useful in pre-
+ view-continuous mode.
- The commands are executed at the following points: $compil-
- ing_cmd at the start of compilation, $success_cmd at the end of
- a completely successful compilation, $failure_cmd at the end of
+ The commands are executed at the following points: $compil-
+ ing_cmd at the start of compilation, $success_cmd at the end of
+ a completely successful compilation, $failure_cmd at the end of
an unsuccessful compilation, $warning_cmd at the of an otherwise
successful compilation that gives warnings about undefined cita-
tions or references or about multiply defined references. If any
- of above variables is undefined or blank (the default situa-
+ of above variables is undefined or blank (the default situa-
tion), then the corresponding command is not executed.
- However, when $warning_cmd is not set, then in the case of a
- compilation with warnings about references or citations, but
- with no other error, one or other of $success_cmd or $fail-
- ure_cmd is used (if it is set) according to the setting of
+ However, when $warning_cmd is not set, then in the case of a
+ compilation with warnings about references or citations, but
+ with no other error, one or other of $success_cmd or $fail-
+ ure_cmd is used (if it is set) according to the setting of
$warnings_as_errors.
An example of a simple setting of these variables is as follows
- $compiling_cmd = "xdotool search --name \"%D\" set_window
+ $compiling_cmd = "xdotool search --name \"%D\" set_window
--name \"%D compiling\"";
- $success_cmd = "xdotool search --name \"%D\" set_window
+ $success_cmd = "xdotool search --name \"%D\" set_window
--name \"%D OK\"";
$warning_cmd = "xdotool search --name \"%D\" ".
"set_window --name \"%D CITE/REF ISSUE\"";
- $failure_cmd = "xdotool search --name \"%D\" set_window
+ $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".
+ 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
- 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.
- More complicated situations can best be handled by defining a
- Perl subroutine to invoke the necessary commands, and using the
- "internal" keyword in the definitions to get the subroutine to
- be invoked. (See the section "Format of Command Specifications"
- for how to do this.)
- Naturally, the above settings that invoke the xdotool program
- are only applicable when the X-Window system is used for the
+ 17 April 2020 38
- 26 December 2019 38
+LATEXMK(1) General Commands Manual LATEXMK(1)
+ 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".
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ 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.
+ More complicated situations can best be handled by defining a
+ Perl subroutine to invoke the necessary commands, and using the
+ "internal" keyword in the definitions to get the subroutine to
+ be invoked. (See the section "Format of Command Specifications"
+ for how to do this.)
+ Naturally, the above settings that invoke the xdotool program
+ are only applicable when the X-Window system is used for the
relevant window(s). For other cases, you will have to find what
software solutions are available.
@@ -2520,15 +2539,15 @@
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 de-
- fault list. In that case you can specify the excluded files in
+ fault 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
+ 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
@@ -2538,10 +2557,10 @@
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 @de-
- fault_files and having to update the list every time you change
+ fault_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
+ 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.
@@ -2548,74 +2567,86 @@
@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:
- @default_files = ("paper_current");
+ 17 April 2020 39
- @default_files = ("paper1", "paper2.tex");
- 26 December 2019 39
+LATEXMK(1) General Commands Manual LATEXMK(1)
+ 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:
+ @default_files = ("paper_current");
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ @default_files = ("paper1", "paper2.tex");
-
@default_files = ("*.tex", "*.dtx");
- Note that more than file may be given, and that the default ex-
+ Note that more than file may be given, and that the default ex-
tension 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 up-
+ 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 up-
dating 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 be-
- havior is not to do this, which is the same as the behavior of
- latex and pdflatex programs. This variable is set by the -cd
+ Whether to change working directory to the directory specified
+ for the main source file before processing it. The default be-
+ havior 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.
$dvi_filter [empty]
- The dvi file filter to be run on the newly produced dvi file be-
- fore other processing. Equivalent to specifying the -dF option.
+ The dvi file filter to be run on the newly produced dvi file
+
+
+ 17 April 2020 40
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
+ before other processing. Equivalent to specifying the -dF op-
+ tion.
+
$dvi_mode [See below for default]
If nonzero, generate a dvi version of the document. Equivalent
to the -dvi option.
@@ -2632,18 +2663,6 @@
start program, which will cause to be run whatever command the
system has associated with .dvi files.]
-
-
-
- 26 December 2019 40
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
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-
@@ -2679,6 +2698,18 @@
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
+
+
+
+ 17 April 2020 41
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
dvipdfm and dvipdfmx.
$dvips ["dvips %O -o %D %S"]
@@ -2698,18 +2729,6 @@
$dvips_silent_switch ["-q"]
Switch(es) for dvips program when silent mode is on.
-
-
-
- 26 December 2019 41
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
$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
@@ -2745,6 +2764,18 @@
$failure_cmd [undefined]
See the documentation for $compiling_cmd.
+
+
+
+ 17 April 2020 42
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
$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
@@ -2764,18 +2795,6 @@
stamps of the files it works with. However, there are a couple
of situations when it needs to know whether a certain file was
created in the current run of a program (e.g., (pdf)latex) or is
-
-
-
- 26 December 2019 42
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
a leftover file from a previous run. It does this by comparing
the modification time of the file with the system time just be-
fore the program was started. If the modification time is ear-
@@ -2811,6 +2830,18 @@
it normally indicates that at least one of the systems is mis-
configured. The variable $filetime_offset_report_threshold
specifies the smallest size of the difference (or offset) in
+
+
+
+ 17 April 2020 43
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
seconds between the times of the local and remote system beyond
which the offset is reported. This is reported at the point in
the latexmk's progress that it measures the offset. The report
@@ -2830,18 +2861,6 @@
This list specifies files known to be generated by latex (and
pdflatex, etc). It is used in two ways: (a) The specified files
-
-
-
- 26 December 2019 43
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
are deleted in a cleanup operation (with the -c, -C, -CA, -g and
-gg options), and (b) It affects the determination of whether a
rerun of (pdf)LaTeX is needed after a run that gives an error.
@@ -2877,6 +2896,18 @@
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
+
+
+
+ 17 April 2020 44
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
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
@@ -2896,18 +2927,6 @@
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
-
-
-
- 26 December 2019 44
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
expression specifies that lines beginning with "%%CreationDate:
" are to be ignored in deciding whether a file of the given ex-
tension .eps has changed.
@@ -2942,8 +2961,20 @@
not contain spaces.)
The placeholder '%A' is permitted. This will be substituted by
- the basename of the TeX file. The primary purpose is when a va-
- riety of tex files are to be processed, and you want to use a
+ the basename of the TeX file. The primary purpose is when a
+
+
+
+ 17 April 2020 45
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
+ variety of tex files are to be processed, and you want to use a
different jobname for each but one that is distinct for each.
Thus if you wanted to compare compilations of a set of files on
different operating systems, with distinct filenames for all the
@@ -2962,18 +2993,6 @@
both files will be compiled. The .aux, .log, and .pdf files
will have basenames test1-MSWin32 ante test2-MSWin32 on a MS-
Windows system, test1-darwin and test2-darwin on an OS-X system,
-
-
-
- 26 December 2019 45
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
and a variety of similar cases on linux systems.
@@ -3010,6 +3029,17 @@
visible in latexmk's screen output about invocations of kpse-
which.
+
+
+ 17 April 2020 46
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
$landscape_mode [0]
If nonzero, run in landscape mode, using the landscape mode pre-
viewers and dvi to postscript converters. Equivalent to the -l
@@ -3027,19 +3057,6 @@
tex, and $xelatex, see the section "Advanced Configuration".
-
-
-
-
- 26 December 2019 46
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
%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
@@ -3077,6 +3094,18 @@
Switch(es) for the LaTeX processing program when silent mode is
on.
+
+
+
+ 17 April 2020 47
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
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
@@ -3095,17 +3124,6 @@
$lpr = '"c:/Program Files/Ghostgum/gsview/gsview32.exe" /p';
-
-
- 26 December 2019 47
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
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
@@ -3141,6 +3159,19 @@
tex, and $xelatex, see the section "Advanced Configuration".
+
+
+
+
+ 17 April 2020 48
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
%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
@@ -3161,17 +3192,6 @@
Switch(es) for the lualatex program (specified in the variable
$lualatex) when silent mode is on.
-
-
- 26 December 2019 48
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
See details of the $latex_silent_switch for other information
that equally applies to $lualatex_silent_switch.
@@ -3197,21 +3217,42 @@
$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.
+ running under MS-Windows. With the default value of 1 for this
+ variable, when a command is executed under MS-Windows, latexmk
+ substitutes "\" for the separator character between components
+ of a directory name. Internally, latexmk uses "/" for the di-
+ rectory 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
- 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 en-
- vironment inside MS-Windows.)
+ For almost all programs and for almost all filenames under MS-
+ Windows, both "\" and "/" are acceptable as the directory
+
+
+ 17 April 2020 49
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
+ separator character, provided at least that filenames are prop-
+ erly quoted. But it is possible that programs exist that only
+ accept "\" on the command line, since that is the standard di-
+ rectory separator for MS-Windows. So for safety latexmk makes
+ the substitution from "/" to "\", by default.
+
+ However there are also programs on MS-Windows for which a back
+ slash "\" is interpreted differently than as a directory separa-
+ tor; for these the directory separator should be "/". Programs
+ with this behavior include all the *latex programs in the
+ TeXLive implementation (but not the MiKTeX implementation).
+ Hence if you use TeXLive on MS-Windows, then $MSWin_back_slash
+ should be set to zero.
+
+
$new_viewer_always [0]
This variable applies to latexmk only in continuous-preview
mode. If $new_viewer_always is 0, latexmk will check for a pre-
@@ -3225,24 +3266,12 @@
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
+ The effect of this variable (when non-blank) is achieved by us-
+ ing 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.
-
-
- 26 December 2019 49
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
- 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
the document directory.
@@ -3263,6 +3292,18 @@
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
+
+
+
+ 17 April 2020 50
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
variable openout_any to "a" (as in "all"), to override the de-
fault "paranoid" setting.
@@ -3293,17 +3334,6 @@
$pdflatex = "pdflatex --shell-escape %O %S";
-
-
- 26 December 2019 50
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
(In some earlier versions of latexmk, you needed to use an as-
signment to $pdflatex to allow the use of lualatex or xelatex
instead of pdflatex. There are now separate configuration vari-
@@ -3329,6 +3359,17 @@
See details of the %latex_input_extensions for other information
that equally applies to %pdflatex_input_extensions.
+
+
+ 17 April 2020 51
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
$pdflatex_silent_switch ["-interaction=batchmode"]
Switch(es) for the pdflatex program (specified in the variable
$pdflatex) when silent mode is on.
@@ -3358,18 +3399,6 @@
ample, SumatraPDF or gsview is used to view pdf files.
Important note: Normally you will want to have a previewer run
-
-
-
- 26 December 2019 51
-
-
-
-
-
-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
@@ -3396,6 +3425,17 @@
Note that acroread under MS-Windows (but not UNIX) locks the pdf
file, so the default value is then 3.
+
+
+ 17 April 2020 52
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
Arranging to use a command to get a previewer explicitly updated
requires three variables to be set. For example:
@@ -3424,18 +3464,6 @@
with their default settings of $pscmd.
Setting the variable to -1 is used to indicate that $pscmd is
-
-
-
- 26 December 2019 52
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
not to be used.
$postscript_mode [0]
@@ -3463,6 +3491,17 @@
+
+
+ 17 April 2020 53
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
$preview_continuous_mode [0]
If nonzero, run a previewer to view the document, and continue
running latexmk to keep .dvi up-to-date. Equivalent to the -pvc
@@ -3490,18 +3529,6 @@
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
-
-
-
- 26 December 2019 53
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
the previewer about file changes).
Each line of the output of this command is assumed to correspond
@@ -3529,6 +3556,18 @@
Note that gv could be used with the -watch option updates its
display whenever the postscript file changes, whereas ghostview
+
+
+
+ 17 April 2020 54
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
does not. However, different versions of gv have slightly dif-
ferent ways of writing this option. You can configure this
variable appropriately.
@@ -3557,17 +3596,6 @@
command, this is the command that is run. See the information
for the variable $ps_update_method.
-
-
- 26 December 2019 54
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
$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_up-
@@ -3595,6 +3623,17 @@
The period of inactivity, in minutes, after which pvc mode times
out. This is used if $pvc_timeout is nonzero.
+
+
+ 17 April 2020 55
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
$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).
@@ -3622,18 +3661,6 @@
source files and generated files after a run of latex or pdfla-
tex.
-
-
-
- 26 December 2019 55
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
It is generally recommended to use this option (or to configure
the $recorder variable to be on.) But it only works if (pdf)la-
tex supports the -recorder option, which is true for most cur-
@@ -3661,6 +3688,18 @@
and dvips do, because sometimes graphics files get generated in
the output or aux directories.]
+
+
+
+ 17 April 2020 56
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
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-
@@ -3687,21 +3726,9 @@
also set this variable.
Note that multiple occurrences for the same undefined object on
- the same page and same line will be compressed to a single
+ the same page and same line will be compressed to a single warn-
+ ing.
-
-
- 26 December 2019 56
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
- warning.
-
$silent [0]
Whether to run silently. Setting $silent to 1 has the same ef-
fect as the -quiet of -silent options on the command line.
@@ -3727,6 +3754,18 @@
$success_cmd [undefined]
See the documentation for $compiling_cmd.
+
+
+
+ 17 April 2020 57
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
$tmpdir [See below for default]
Directory to store temporary files that latexmk may generate
while running.
@@ -3753,19 +3792,6 @@
do this. The intent of calling make from latexmk is merely to
detect dependencies.
-
-
-
-
- 26 December 2019 57
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
$view ["default"]
Which kind of file is to be previewed if a previewer is used.
The possible values are "default", "dvi", "ps", "pdf". The
@@ -3794,6 +3820,18 @@
The default behavior is normally satisfactory in the usual edit-
compile-edit cycle. But, for example, latexmk can also be used
+
+
+
+ 17 April 2020 58
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
as part of a build process for some bigger project, e.g., for
creating documentation in the build of a software application.
Then it is often sensible to treat citation and reference warn-
@@ -3815,23 +3853,11 @@
that one or more of the commands isn't set.)
- $xdvipdfmx ["xdvipdfmx -o %D %O %S"]
+ $xdvipdfmx ["xdvipdfmx -E -o %D %O %S"]
The program to make a pdf file from an xdv file (used in con-
junction with xelatex when $pdf_mode=5).
-
-
-
- 26 December 2019 58
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
$xdvipdfmx_silent_switch ["-q"]
Switch(es) for the xdvipdfmx program when silent mode is on.
@@ -3860,6 +3886,18 @@
not been found, and the file is given without an extension.
This typically happens when LaTeX commands of the form \in-
put{file} or \includegraphics{figure}, when the relevant source
+
+
+
+ 17 April 2020 59
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
file does not exist.
In this situation, latexmk searches for custom dependencies to
@@ -3887,17 +3925,6 @@
in the .tex file.
-
-
- 26 December 2019 59
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
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
@@ -3925,6 +3952,18 @@
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
+
+
+
+ 17 April 2020 60
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
we are converting from doesn't exist, then no action is taken.
Generally, the appropriate value of must is zero.
@@ -3952,18 +3991,6 @@
tects that a run of latex/pdflatex needs to read a file, like a graph-
ics file, whose extension is the to-extension of a custom dependency.
Then latexmk examines whether a file exists with the same name, but
-
-
-
- 26 December 2019 60
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
with the corresponding from-extension, as specified in the custom-de-
pendency. If it does, then a corresponding instance of the custom de-
pendency is created, after which the rule is invoked whenever the des-
@@ -3991,6 +4018,18 @@
Note for advanced usage: The operating system's environment variable
TEXINPUTS can be used to specify a search path for finding files by la-
tex etc. Correspondingly, when a missing file is reported, latexmk
+
+
+
+ 17 April 2020 61
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
looks in the directories specified in TEXINPUTS as well as in the cur-
rent directory, to find a source file from which an instance of a cus-
tom dependency can be used to make the missing file.
@@ -4018,18 +4057,6 @@
initialization file), the latexmk will delete this rule before making
the new one.
-
-
-
- 26 December 2019 61
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
Suppose latexmk is using this rule to convert a file "figure.fig" to
"figure.eps". Then it will invoke the fig2eps subroutine defined in
the above code with a single argument "figure", which is the basename
@@ -4056,11 +4083,23 @@
}
Note 1: In the command lines given in the system commands in the above
- examples, double quotes have been inserted around the file names (im-
- plemented by '\"' 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 nor-
- mally safer to keep them in. Even though the rules for quoting vary
+ examples, double quotes have been inserted around the file names
+
+
+
+ 17 April 2020 62
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
+ (implemented by '\"' 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 vary
between operating systems, command shells and individual pieces of
software, the quotes in the above examples do not cause problems in the
cases I have tested.
@@ -4084,18 +4123,6 @@
Removing custom dependencies, and when you might need to do this:
If you have some general custom dependencies defined in the system or
-
-
-
- 26 December 2019 62
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
user initialization file, you may find that for a particular project
they are undesirable. So you might want to delete the unneeded ones.
A situation where this would be desirable is where there are multiple
@@ -4122,13 +4149,25 @@
texmk, and many examples can be found, e.g., on the web.
However in later versions of latexmk the internal structure of the im-
- plementation of its "rules" for the steps of processing, including cus-
- tom 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".
+ plementation of its "rules" for the steps of processing, including
+
+
+ 17 April 2020 63
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
+ 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.
@@ -4150,18 +4189,6 @@
push @generated_exts, 'ndx', 'nnd';
Notice the added line compared with earlier examples. The extra line
-
-
-
- 26 December 2019 63
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
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
@@ -4189,6 +4216,18 @@
This last example uses the command specification in $makeindex, and so
any customization you have made for the standard index also applies to
+
+
+
+ 17 April 2020 64
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
your extra indexes.
Similar techniques can be applied for glossaries.
@@ -4216,18 +4255,6 @@
item, and the name of the subroutine for the custom dependency. These
were all defined above.
-
-
-
- 26 December 2019 64
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
An example of the old method of defining custom dependencies is as fol-
lows. It is the code in an RC file to ensure automatic conversion of
.fig files to .eps files:
@@ -4257,6 +4284,16 @@
ful ideas
+
+ 17 April 2020 65
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
Utility subroutines
ensure_path( var, values ...)
@@ -4283,17 +4320,6 @@
invoked programs.
-
-
- 26 December 2019 65
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
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
@@ -4322,6 +4348,18 @@
This gives the name of the main output file if any. Note the
double dollar signs.
+
+
+
+ 17 April 2020 66
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
rdb_ensure_file( $rule, file )
This a subroutine that ensures that the given file is among the
source files for the specified rule. It is typically used when,
@@ -4348,18 +4386,6 @@
rdb_set_source( $rule, file, ... )
-
-
-
- 26 December 2019 66
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
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
@@ -4388,6 +4414,18 @@
&std_tex_cmds;
+
+
+
+ 17 April 2020 67
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
This results in $latex = 'latex %O %S', and similarly for $pdflatex,
$lualatex, and $xelatex. Note the ampersand in the invocation; this
indicates to Perl that a subroutine is being called.
@@ -4414,18 +4452,6 @@
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
-
-
-
- 26 December 2019 67
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
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-
@@ -4454,6 +4480,18 @@
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.
+
+
+
+ 17 April 2020 68
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
The simplest method is simply to delegate all the relevant tasks to la-
texmk, as is suitable for a straightforward LaTeX document. For this a
suitable Makefile is like
@@ -4479,26 +4517,14 @@
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
+ the effect of causing the rule to be always out-of-date, so that la-
+ texmk is always run. It is latexmk that decides whether any action is
+ needed, e.g., a rerun of pdflatex. Effectively the Makefile delegates
+ 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 by cus-
+ tom dependencies configured in latexmk.
-
-
- 26 December 2019 68
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
- 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
- by custom dependencies configured in latexmk.
-
But something better is needed in more complicated situations, for ex-
ample, 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 follow-
@@ -4520,6 +4546,18 @@
%.pdf : %.fig
fig2dev -Lpdf $< $@
+
+
+
+ 17 April 2020 69
+
+
+
+
+
+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.
@@ -4546,18 +4584,6 @@
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
-
-
-
- 26 December 2019 69
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
"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.pdf", and only then reruns latexmk.
@@ -4587,6 +4613,17 @@
pdf file cannot be updated. (Remedy: configure latexmk to use suma-
trapdf instead.)
+
+
+ 17 April 2020 70
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
THANKS TO
Authors of previous versions. Many users with their feedback, and es-
pecially David Coppit (username david at node coppit.org) who made many
@@ -4596,7 +4633,7 @@
AUTHOR
Current version, by John Collins (username jcc8 at node psu.edu).
- (Version 4.67).
+ (Version 4.69a).
Released version can be obtained from CTAN:
<http://www.ctan.org/pkg/latexmk/>, and from the author's website
@@ -4615,13 +4652,11 @@
- 26 December 2019 70
-LATEXMK(1) General Commands Manual LATEXMK(1)
@@ -4646,41 +4681,6 @@
+ 17 April 2020 71
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 26 December 2019 71
-
-
Modified: trunk/Master/texmf-dist/scripts/latexmk/latexmk.pl
===================================================================
--- trunk/Master/texmf-dist/scripts/latexmk/latexmk.pl 2020-04-18 20:56:01 UTC (rev 54785)
+++ trunk/Master/texmf-dist/scripts/latexmk/latexmk.pl 2020-04-18 20:56:25 UTC (rev 54786)
@@ -124,7 +124,7 @@
# Test for already running previewer gets wrong answer if another
# process has the viewed file in its command line
-## Copyright John Collins 1998-2019
+## Copyright John Collins 1998-2020
## (username jcc8 at node psu.edu)
## (and thanks to David Coppit (username david at node coppit.org)
## for suggestions)
@@ -162,6 +162,32 @@
##
## 12 Jan 2012 STILL NEED TO DOCUMENT some items below
##
+## 16 Apr 2020 John Collins Correct contents of "All targets (...) are up-to-date" message
+## V. 4.69a.
+## 12 Mar 2020 John Collins Version is 4.69
+## 7 Feb 2020 John Collins Report rc files read
+## 6 Feb 2020 John Collins Fix bug when -cd and -outdir are used, and outdir is
+## same as document directory. (Bug is caused by
+## problem in perl module Cwd.)
+## 2,3 Feb 2020 John Collins Correction in find_basename.
+## 31 Jan 2020 John Collins Cleanup sub exit_msg1: incorrect comment etc.
+## Extra @file_not_found entry for message from
+## \input on not-found-file
+## Remove use of $extension_treatment: Too hard to
+## check. Always use what was called 'unix' method.
+## When command-line-specified tex file not found,
+## test for cusdep to make it, then try kpsewhich,
+## and only if all 3 fail report an error.
+## 15 Jan 2020 John Collins Add -MSWinBackSlash -MSWinBackSlash- options to
+## control whether directory separator '\' is
+## used for filenames on command line for
+## called programs under MSWin.
+## 3 Jan 2020 John Collins Add -E option to default command for xdvipdfmx, to
+## match call made by xetex (see XeTeX_ext.c in
+## xetex source). This forces xdvipdfmx to always
+## try to embed fonts, ignoring licensing flags, etc.
+##
+## Current version (4.67, 26 Dec 2019) to CTAN
## 26 Dec 2019 John Collins Change place of setting of $view_file
## Make fully consistent set of options for engines:
## -latex, -latex=...,
@@ -254,8 +280,8 @@
$my_name = 'latexmk';
$My_name = 'Latexmk';
-$version_num = '4.67';
-$version_details = "$My_name, John Collins, 26 Dec. 2019";
+$version_num = '4.69a';
+$version_details = "$My_name, John Collins, 17 Apr. 2020";
use Config;
use File::Basename;
@@ -293,7 +319,7 @@
use File::Find;
use List::Util qw( max );
use Cwd; # To be able to change cwd
-use Cwd "chdir"; # Ensure $ENV{PWD} tracks cwd
+#use Cwd "chdir"; # Ensure $ENV{PWD} tracks cwd. NO NEED, and it messes up -cd -outdir=
use Digest::MD5;
#use strict;
@@ -337,6 +363,7 @@
@file_not_found = (
'^No file\\s*(.*)\\.$',
'^\\! LaTeX Error: File `([^\\\']*)\\\' not found\\.',
+ '^\\! I can\\\'t find file `([^\\\']*)\\\'\\.',
'.*?:\\d*: LaTeX Error: File `([^\\\']*)\\\' not found\\.',
'^LaTeX Warning: File `([^\\\']*)\\\' not found',
'^Package .* [fF]ile `([^\\\']*)\\\' not found',
@@ -653,7 +680,7 @@
$ps2pdf = 'ps2pdf %O %S %D';
## Command to convert xdv file to pdf file
-$xdvipdfmx = 'xdvipdfmx -o %D %O %S';
+$xdvipdfmx = 'xdvipdfmx -E -o %D %O %S';
$xdvipdfmx_silent_switch = '-q';
@@ -669,13 +696,6 @@
# 'auto' ==> set print type according to the printable
# file(s) being made: priority 'ps', 'pdf', 'dvi'
-## Which treatment of default extensions and filenames with
-## multiple extensions is used, for given filename on
-## tex/latex's command line? See sub find_basename for the
-## possibilities.
-## Current tex's treat extensions like UNIX teTeX:
-$extension_treatment = 'unix';
-
# Viewers. These are system dependent, so default to none:
$pdf_previewer = $ps_previewer = $ps_previewer_landscape = $dvi_previewer = $dvi_previewer_landscape = "NONE";
@@ -914,6 +934,8 @@
# NT executables.
$tmpdir = $ENV{TMPDIR} || $ENV{TEMP} || '.';
+ # Which rc files did I read?
+ @rc_files_read = ();
## List of possibilities for the system-wide initialization file.
## The first one found (if any) is used.
## We could stay with MSWin files here, since cygwin perl understands them
@@ -1676,7 +1698,6 @@
" and in that case it should be a regular text file, not a directory.\n";
}
elsif ( -e $rc_file ) {
- #print "===Reading rc file \"$rc_file\" ...\n";
process_rc_file( $rc_file );
return;
}
@@ -1801,6 +1822,8 @@
shift;
}
elsif ( /^-MP$/ ) { $dependents_phony = 1; }
+ elsif ( /-MSWinBackSlash$/ ) { $MSWin_back_slash = 1; }
+ elsif ( /-MSWinBackSlash-$/ ) { $MSWin_back_slash = 0; }
elsif (/^-new-viewer$/) {
$new_viewer_always = 1;
}
@@ -1990,6 +2013,9 @@
}
}
+show_array( "Rc files read:", @rc_files_read )
+ unless ( $silent && ! $diagnostics );
+
if ( $bad_options > 0 ) {
&exit_help( "Bad options specified" );
}
@@ -2413,7 +2439,7 @@
($filename, $path) = fileparse( $filename );
warn "$My_name: Changing directory to '$path'\n"
if !$silent;
- pushd( $path );
+ pushd( dirname_no_tail( $path ) );
}
else {
$path = '';
@@ -2880,6 +2906,8 @@
# Normalize versions terminating in directory/path separator
# and versions referring to current directory
# These actions in a subroutine so they can be used elsewhere.
+ $out_dir = dirname_no_tail( $out_dir );
+ $aux_dir = dirname_no_tail( $aux_dir );
$out_dir1 = $out_dir;
$aux_dir1 = $aux_dir;
foreach ( $aux_dir1, $out_dir1 ) {
@@ -3410,84 +3438,76 @@
# 2 - Where to place base file
# 3 - Where to place tex file
# Returns non-zero if tex file does not exist
- #
- # The rules for determining this depend on the implementation of TeX.
- # The variable $extension_treatment determines which rules are used.
- # !!!!!!!! I still need to implement use of kpsewhich to match behavior
- # of (pdf)latex correctly.
+ my $fail = 0;
+ local ( $given_name, $base_name, $ext, $path, $tex_name, $source_name );
+ $given_name = $_[0];
+ $source_name = '';
+ $tex_name = $given_name; # Default name if I don't find the tex file
+ ($base_name, $path, $ext) = fileparseB( $given_name );
- local($given_name, $base_name, $ext, $path, $tex_name);
- $given_name = $_[0];
- if ( "$extension_treatment" eq "miktex_old" ) {
- # Miktex v. 1.20d:
- # 1. If the filename has an extension, then use it.
- # 2. Else append ".tex".
- # 3. The basename is obtained from the filename by
- # removing the path component, and the extension, if it
- # exists. If a filename has a multiple extension, then
- # all parts of the extension are removed.
- # 4. The names of generated files (log, aux) are obtained by
- # appending .log, .aux, etc to the basename. Note that
- # these are all in the CURRENT directory, and the drive/path
- # part of the originally given filename is ignored.
- #
- # Thus when the given filename is "\tmp\a.b.c", the tex
- # filename is the same, and the basename is "a".
+ # Treatment of extensions (in TeXLive 2019), with omission of path search:
+ # Exists: always means exists as a file, i.e., not as a directory.
+ # A. Finding of tex file:
+ # 1. If extension is .tex and given_name.tex exists, use it.
+ # 2. Else if given_name.tex exists, use it.
+ # 3. Else if givne_name exists, use it.
+ # B. The base filename is obtained by deleting the path
+ # component and the extension.
+ # C. The names of generated files (log, aux) are obtained by appending
+ # .log, .aux, etc to the basename. Note that these are all in the
+ # CURRENT directory (or the output or aux directory, as appropriate).
+ # The drive/path part of the originally given filename is ignored.
- ($base_name, $path, $ext) = fileparse( $given_name, '\..*' );
- if ( "$ext" eq "") { $tex_name = "$given_name.tex"; }
- else { $tex_name = $given_name; }
- $_[1] = $base_name;
- $_[2] = $tex_name;
- }
- elsif ( "$extension_treatment" eq "unix" ) {
- # unix (at least TeXLive 2016) =>
- # A. Finding of tex file:
- # 1. If filename.tex exists, use it,
- # 2. else if kpsewhich finds filename.tex, use it
- # 3. else if filename exists, use it,
- # 4. else if kpsewhich finds filename, use it.
- # (Probably can unify the above by
- # 1'. If kpsewhich finds filename.tex, use result.
- # 2'. else if kpsewhich finds filename, use result.
- # 3'. else report file not found.
- # B. The base filename is obtained by deleting the path
- # component and, if an extension exists, the last
- # component of the extension, even if the extension is
- # null. (A name ending in "." has a null extension.)
- # C. The names of generated files (log, aux) are obtained by
- # appending .log, .aux, etc to the basename. Note that
- # these are all in the CURRENT directory, and the drive/path
- # part of the originally given filename is ignored.
- #
- # Thus when the given filename is "/tmp/a.b.c", there are two
- # cases:
- # a. /tmp/a.b.c.tex exists. Then this is the tex file,
- # and the basename is "a.b.c".
- # b. /tmp/a.b.c.tex does not exist. Then the tex file is
- # "/tmp/a.b.c", and the basename is "a.b".
- # But there are also modifications of this when a file can be
- # found by kpsewhich.
+ # Here we'll do:
+ # 1. Find the tex file by the above method, if possible.
+ # 2. If not, find a custom dependency with a source file that exists to
+ # make the tex file so that after the tex file is made, the above
+ # rules find the tex file.
+ # 3. If that also fails, use kpsewhich on given_name to find the tex
+ # file
+ # 4. If that also fails, report non-existent tex file.
- if ( -f "$given_name.tex" ) {
- $tex_name = "$given_name.tex";
- }
- else {
- $tex_name = "$given_name";
- }
- ($base_name, $path, $ext) = fileparse( $tex_name, '\.[^\.]*' );
- $_[1] = $base_name;
- $_[2] = $tex_name;
- }
- else {
- die "$My_name: Incorrect configuration gives \$extension_treatment=",
- "'$extension_treatment'\n";
- }
- if ($diagnostics) {
- print "Given='$given_name', tex='$tex_name', base='$base_name'\n";
- }
- return ! -e $tex_name;
+
+ if ( ($ext eq '.tex') && (-f $given_name) ) {
+ $tex_name = "$given_name";
+ }
+ elsif ( -f "$given_name.tex" ) {
+ $tex_name = "$given_name.tex";
+ $base_name .= $ext;
+ }
+ elsif ( -f $given_name ) {
+ $tex_name = $given_name;
+ }
+ elsif ( ($ext eq '.tex') && find_cus_dep( $given_name, $source_name ) ) {
+ $tex_name = $given_name;
+ }
+ elsif ( find_cus_dep( "$given_name.tex", \$source_name ) ) {
+ $tex_name = "$given_name.tex";
+ $base_name .= $ext;
+ }
+ elsif ( ($ext =~ /^\..+/) && find_cus_dep( $given_name, $source_name ) ) {
+ $tex_name = $given_name;
+ }
+ else {
+ my @kpse_result = kpsewhich( $given_name );
+ if ($#kpse_result < 0) {
+ $fail = 1;
+ }
+ else {
+ $tex_name = $kpse_result[0];
+ ($base_name) = fileparseB( $tex_name );
+ }
+ }
+
+ $_[1] = $base_name;
+ $_[2] = $tex_name;
+
+ if ($diagnostics) {
+ print "Given='$given_name', tex='$tex_name', base='$base_name', ext= $ext, source='$source_name'\n";
+ }
+ return $fail;
+
} #END find_basename
#************************************************************
@@ -3728,8 +3748,8 @@
# Exit with code 2 if is a syntax error or other problem.
my $rc_file = $_[0];
my $ret_code = 0;
- warn "$My_name: Executing Perl code in file '$rc_file'...\n"
- if $diagnostics;
+ push @rc_files_read, $rc_file;
+
# I could use the do command of perl, but the preceeding -r test
# to get good diagnostics gets the wrong result under cygwin
# (e.g., on /cygdrive/c/latexmk/LatexMk)
@@ -3878,10 +3898,9 @@
sub exit_msg1
{
- # exit_msg1( error_message, retcode [, action])
+ # exit_msg1( error_message, retcode )
# 1. display error message
- # 2. if action set, then restore aux file
- # 3. exit with retcode
+ # 2. exit with retcode
warn "\n------------\n";
warn "$My_name: $_[0].\n";
warn "-- Use the -f option to force complete processing.\n";
@@ -3985,6 +4004,10 @@
" -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",
+ " -MSWinBackSlash under MSWin use backslash (\\) for directory separators\n",
+ " for filenames given to called programs\n",
+ " -MSWinBackSlash- under MSWin use forward slash (/) for directory separators\n",
+ " for filenames given to called programs\n",
" -new-viewer - in -pvc mode, always start a new viewer\n",
" -new-viewer- - in -pvc mode, start a new viewer only if needed\n",
" -nobibtex - never use bibtex\n",
@@ -5396,6 +5419,30 @@
#************************************************************
+sub dirname_no_tail {
+ my $dirname = $_[0];
+# print "DNT1 = '$dirname'\n";
+ foreach ($dirname) {
+ # Normalize name to use / to separate directory components:
+ # (Note both / and \ are allowed under MSWin.)
+ s(\\)(/)g;
+ # Change multiple trailing / to single /
+ # (Note internal // or \\ can have special meaning on MSWin)
+ s(/+$)(/);
+ # Remove trailing /,
+ # BUT **not** if that changes the semantics, i.e., if name is "/" or "C:/".
+ if ( m(/$) ) {
+ if ( ( ! m(^/+$) ) && ( ! m(:/+$) ) ) {
+ s(/$)();
+ }
+ }
+ }
+# print "DNT2 = '$dirname'\n";
+ return $dirname;
+}
+
+#************************************************************
+
sub clean_filename {
# Convert quoted filename as found in log file to filename without quotes
# Allows arbitrarily embedded double-quoted substrings, includes the
@@ -5427,13 +5474,17 @@
# (Note both / and \ are allowed under MSWin.)
foreach ($cwd, $file, @dirs) {
s(\\)(/)g;
+ $_ = dirname_no_tail( $_ );
}
# Remove initial component equal to current working directory.
# Use \Q and \E round directory name in regex to avoid interpretation
# of metacharacters in directory name:
foreach my $dir ( @dirs, '.', $cwd ) {
- if ( $file =~ s(^\Q$dir\E/)() ) {
- last;
+ if ( $dir =~ /^\s*$/ ) {
+ next;
+ }
+ if ( $file =~ s(^\Q$dir\E/)() ) {
+ last;
}
}
return $file;
@@ -6172,6 +6223,7 @@
}
&parse_log;
+
my $missing_dirs = 'none'; # Status of missing directories
if (@missing_subdirs) {
$missing_dirs = 'success';
@@ -6639,7 +6691,7 @@
foreach my $dep (@cus_dep_list){
my ($fromext,$toext) = split('\s+',$dep);
if ( ( "$ext" eq "$toext" )
- && ( -e "$path$base.$fromext" )
+ && ( -f "$path$base.$fromext" )
) {
# Source file for the missing file exists
# So we have a real include file, and it will be made
@@ -6657,7 +6709,7 @@
# and $_ doesn't have an extension
foreach my $dep (@cus_dep_list){
my ($fromext,$toext) = split('\s+',$dep);
- if ( -e "$path$base.$fromext" ) {
+ if ( -f "$path$base.$fromext" ) {
# Source file for the missing file exists
# So we have a real include file, and it will be made
# next time by &rdb__dependents
@@ -6664,7 +6716,7 @@
$new_includes{"$path$base.$toext"} = 1;
# next MISSING_FILE;
}
- if ( -e "$path$base.$toext" ) {
+ if ( -f "$path$base.$toext" ) {
# We've found the extension for the missing file,
# and the file exists
$new_includes{"$path$base.$toext"} = 1;
@@ -7265,8 +7317,10 @@
print "$My_name: Errors, so I did not complete making targets\n";
}
else {
+# local @dests = ( keys %current_primaries, @pre_primary, @post_primary, @unusual_one_time );
+ local @rules = ( keys %current_primaries, @post_primary, @unusual_one_time );
local @dests = ();
- rdb_for_some( [@_], sub{ push @dests, $$Pdest if ($$Pdest); } );
+ rdb_for_some( [@rules], sub{ push @dests, $$Pdest if ($$Pdest); } );
print "$My_name: All targets (@dests) are up-to-date\n";
}
}
@@ -7440,7 +7494,7 @@
$rules_applied{$rule} = 1;
$runs++;
- $pass{$rule}++;
+ $pass{$rule}++;
if ($bibtex_not_run > 0) {
if ($bibtex_not_run == 1 ) {
show_array ("$My_name: I WON'T RUN '$rule' because I don't find the following files:",
@@ -7449,7 +7503,7 @@
elsif ($bibtex_not_run == 2 ) {
warn "$My_name: I AM CONFIGURED/INVOKED NOT TO RUN '$rule'\n";
}
- $return = &rdb_dummy_run1;
+ $return = &rdb_dummy_run0;
}
else {
warn_running( "Run number $pass{$rule} of rule '$rule'" );
@@ -7822,7 +7876,7 @@
#-----------------
-sub rdb_dummy_run1 {
+sub rdb_dummy_run0 {
# Assumes contexts for: rule.
# Update rule state as if the rule ran successfully,
# but don't run the rule.
@@ -7844,7 +7898,7 @@
$$Pout_of_date = $$Pout_of_date_user = 0;
return 0;
-} # END rdb_dummy_run1
+} # END rdb_dummy_run0
#-----------------
@@ -9211,8 +9265,6 @@
#************************************************************
sub find_file1 {
-#?? Need to use kpsewhich, if possible
-
# Usage: find_file1(name, ref_to_array_search_path)
# Modified find_file, which doesn't die.
# Given filename and path, return array of:
@@ -9407,6 +9459,29 @@
####################################################
+sub find_cus_dep {
+ # Usage find_cus_dep( dest, source )
+ # Given dest, if a cus_dep to make it is found, set source.
+ # Return 1 or 0 on success or failure.
+ #
+ my $dest = $_[0];
+ my ($base, $path, $ext) = fileparseB( $dest );
+ $ext =~ s/^\.//;
+ if (! $ext ) { return 0; }
+ foreach my $dep ( @cus_dep_list ) {
+ my ($fromext, $toext) = split( '\s+', $dep );
+ if ( ( "$ext" eq "$toext" ) && ( -f "$path$base.$fromext" ) ) {
+ # We have a way of making $dest
+ $_[1] = "$path$base.$fromext";
+ return 1
+ }
+ }
+ return 0;
+}
+
+####################################################
+####################################################
+
sub add_aux_hook {
# Usage: add_aux_hook( sub_name )
# Add the name subroutine to the array of hooks for
@@ -9975,7 +10050,7 @@
sub pushd {
push @dir_stack, [cwd(), $cache{cwd}];
if ( $#_ > -1) {
- chdir $_[0];
+ chdir dirname_no_tail( $_[0] );
&cache_good_cwd;
}
}
More information about the tex-live-commits
mailing list.