texlive[69221] trunk: latexmk (26dec23)
commits+karl at tug.org
commits+karl at tug.org
Tue Dec 26 22:04:28 CET 2023
Revision: 69221
https://tug.org/svn/texlive?view=revision&revision=69221
Author: karl
Date: 2023-12-26 22:04:28 +0100 (Tue, 26 Dec 2023)
Log Message:
-----------
latexmk (26dec23)
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/glossaries_latexmkrc
trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/glossary_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
Modified: trunk/Build/source/texk/texlive/linked_scripts/latexmk/latexmk.pl
===================================================================
--- trunk/Build/source/texk/texlive/linked_scripts/latexmk/latexmk.pl 2023-12-26 21:02:15 UTC (rev 69220)
+++ trunk/Build/source/texk/texlive/linked_scripts/latexmk/latexmk.pl 2023-12-26 21:04:28 UTC (rev 69221)
@@ -1,6 +1,8 @@
#!/usr/bin/env perl
use warnings;
+
+
## Copyright John Collins 1998-2023
## (username jcc8 at node psu.edu)
## (and thanks to David Coppit (username david at node coppit.org)
@@ -40,10 +42,14 @@
## 20 = probable bug
## or retcode from called program.
-$my_name = 'latexmk';
-$My_name = 'Latexmk';
-$version_num = '4.81';
-$version_details = "$My_name, John Collins, 6 Nov. 2023. Version $version_num";
+BEGIN {
+ # Make sure the following are available when printing diagnostics in BEGIN
+ # blocks.
+ $my_name = 'latexmk';
+ $My_name = 'Latexmk';
+ $version_num = '4.82';
+ $version_details = "$My_name, John Collins, 24 Dec. 2023. Version $version_num";
+}
use Config;
use File::Basename;
@@ -81,9 +87,25 @@
use Cwd "chdir"; # Ensure $ENV{PWD} tracks cwd.
use Digest::MD5;
-# **WARNING**: Don't import time; that overrides core function time(), and messes up
-# somethings
+our %HiRes_non_imports;
use Time::HiRes;
+BEGIN {
+ # Import some HiRes functions to override standard ones.
+ # However, Time::HiRes's documentation says that some of its functions
+ # may be unimplemented on some systems.
+ # So take precautions in case the ones I need aren't implemented.
+ # I must do the import in a BEGIN block, i.e., during compilation
+ # phase, else calls to time() etc get compiled to use std time(), i.e.,
+ # CORE::time(), instead of the HiRes versions.
+ %HiRes_non_imports = ();
+ foreach ( ( qw( time stat sleep ) ) ) {
+ if ( ! eval{ Time::HiRes->import($_); 1; } ) {
+ $HiRes_non_imports{$_} = 1;
+ warn "$My_name: Cannot import Time::HiRes::$_ on this system\n",
+ "$@";
+ }
+ }
+}
#################################################
#
@@ -365,6 +387,14 @@
# Use to limit number of (potentially) wrapped lines to combine into single line.
$max_log_construct = 600;
+# Whether to search for ^^ notation in log file for non-7-bit characters,
+# and convert to bytes. (Note: ^^ notation is produced by hilatex in
+# TeXLive 2023, and by pdflatex in MiKTeX 22.1 if no special option is
+# used (-enable-8bit-chars). (Also pdflatex in TeXLive 2023 (and earlier)
+# gives it if -translate-file=empty is used.)
+# Should also do same with aux files, but I've not done that yet. ????
+# fls file is always UTF-8.
+$conv_hathat = 1;
#########################################################################
## Default parsing and file-handling settings
@@ -483,10 +513,11 @@
$tex_distribution = '';
# List of known *latex rules:
-%possible_primaries = ( 'dvilualatex' => 'primary', 'latex' => 'primary',
+%possible_primaries = ( 'dvilualatex' => 'primary', 'hilatex' => 'primary',
+ 'latex' => 'primary',
'lualatex' => 'primary', 'pdflatex' => 'primary',
'xelatex' => 'primary' );
-&std_tex_cmds;
+std_tex_cmds();
# Possible code to execute by *latex before inputting source file.
# Not used by default.
@@ -493,6 +524,7 @@
$pre_tex_code = '';
## Default switches:
+$hilatex_default_switches = '';
$latex_default_switches = '';
$pdflatex_default_switches = '';
$dvilualatex_default_switches = '';
@@ -502,6 +534,7 @@
$xelatex_default_switches = '-no-pdf';
## Switch(es) to make them silent:
+$hilatex_silent_switch = '-interaction=batchmode';
$latex_silent_switch = '-interaction=batchmode';
$pdflatex_silent_switch = '-interaction=batchmode';
$dvilualatex_silent_switch = '-interaction=batchmode';
@@ -533,6 +566,15 @@
# Possible extensions for main output file of *latex:
%allowed_output_ext = ( ".dvi" => 1, ".xdv" => 1, ".pdf" => 1 );
+# Extensions etc, of special use by latexmk
+$save_error_suffix = '-SAVE-ERROR'; # Suffix to be added to filename, when an
+ # erroneous file is saved insted of being deleted.
+$fdb_ext = 'fdb_latexmk'; # Extension for the file for latexmk's
+ # file-database
+ # Make it long to avoid possible collisions.
+$fdb_ver = 4; # Version number for kind of fdb_file.
+
+
# Variables relevant to specifying cleanup.
# The first set of variables is intended to be user configurable.
#
@@ -564,7 +606,8 @@
# bbl files get special treatment because their deletion is conditional
# and because of the possibility of extra bibtex/biber rules with
# non-standard basename.
- at generated_exts = ( 'aux', 'bcf', 'fls', 'idx', 'ind', 'lof', 'lot',
+ at generated_exts = ( 'aux', 'bcf', 'bcf'.$save_error_suffix, 'fls',
+ 'idx', 'ind', 'lof', 'lot',
'out', 'run.xml', 'toc',
'blg', 'ilg', 'log',
'xdv'
@@ -576,7 +619,7 @@
# Extensions of files to be deleted by -C, but aren't normally included
# in the small clean up by -c. Analogous to @generated_exts and $clean_ext,
# except that pattern rules (with %R) aren't applied.
- at final_output_exts = ( 'dvi', 'dviF', 'ps', 'psF', 'pdf',
+ at final_output_exts = ( 'dvi', 'dviF', 'hnt', 'ps', 'psF', 'pdf',
'synctex', 'synctex.gz' );
$clean_full_ext = "";
@@ -725,6 +768,7 @@
# in case the values of $latex and/or $pdflatex change after an option
# is added.
@extra_dvilualatex_options = ();
+ at extra_hilatex_options = ();
@extra_latex_options = ();
@extra_pdflatex_options = ();
@extra_lualatex_options = ();
@@ -819,7 +863,7 @@
# file(s) being made: priority 'ps', 'pdf', 'dvi'
# Viewers. These are system dependent, so default to none:
-$pdf_previewer = $ps_previewer = $ps_previewer_landscape = $dvi_previewer = $dvi_previewer_landscape = "NONE";
+$pdf_previewer = $ps_previewer = $ps_previewer_landscape = $dvi_previewer = $dvi_previewer_landscape = $hnt_previewer = "NONE";
$dvi_update_signal = undef;
$ps_update_signal = undef;
@@ -918,9 +962,15 @@
# Latexmk does tests on whether a particular generated file, e.g., log or
# fls, has been generated on a current run of a rule, especially *latex, or
-# is leftover from previous runs. This is done by finding whether or not
-# the modification time of the file is at least as recent as the system
-# time at the start of the run. A file with a modification time
+# is leftover from previous runs. An expected file can fail to be
+# generated or generated in other than the expected place because of errors
+# or because of misconfiguration of latexmk. There are also files (notably
+# bcf files) that are generated or not according to the current set of
+# packages, options, etc used by a document.
+#
+# The test for whether a file was generated on the current run of a rule is
+# that the modification time of the file is at least as recent as the
+# system time at the start of the run. A file with a modification time
# significantly less than the time at the start of the run is presumably
# left over from a previous run and not generated in the currrent run. (An
# allowance is made in this comparison for the effects of granularity of
@@ -928,50 +978,63 @@
# earlier than the system time at which the file was last modified.)
#
# But generated files may be on a file system hosted by a server computer
-# that is different than the computer running latexmk. There may there may
-# be an offset between the time on the two computers; this can make it
-# appear that the generated files were made before the run. Most of the
-# time, this problem does not arise, since (a) typical usage of latexmk is
-# with a local file system, and (b) current-day computers and operating
-# systems have their time synchronized accurately with a time server.
+# that is different than the computer running latexmk. There may be an
+# offset between the time on the two computers; this can make it
+# incorrectly appear that the generated files were made before the
+# run. Most of the time, this problem does not arise, since (a) typical
+# usage of latexmk is with a local file system, and (b) current-day
+# computers and operating systems have their time synchronized accurately
+# with a time server. Difficulties are most acute with small documents
+# compiled on a fast computer, e.g., with sub-second compilation times.
#
-# But when latexmk sees symptoms of an excessive offset, it measures the
-# offset between the filesystem time and the system time. This involves
-# writing a temporary file, getting its modification time, and deleting
-# it. The following variables are used for this purpose.
-
+# When latexmk sees symptoms of an excessive offset, it measures the offset
+# between the filesystem time and the system time. This involves writing a
+# temporary file, getting its modification time, and deleting it. Then
+# when testing for whether a file was made on the current run or not, an
+# allowance is then made for the measured time offset between the two
+# computers.
#
-our $filetime_offset_measured = 0; # Measurement not yet done.
-our $filetime_offset = 0; # Filetime relative to system time.
-our $filetime_offset_report_threshold = 10; # Threshold beyond which filetime offsets
- # are reported; large offsets indicate
- # incorrect system time on at least one system.
-# The following variable gives the threshold for detection of left-over
-# file. It allows for (a) different granularity between system time and
-# filesystem time, (b) for some mismatch between file and system time.
-# Note that the making or not making of a file is controlled by the
-# state of the document being compiled and by latexmk's configuration.
-# So a file that is left over from a previous run and not overwritten
-# on the current run will have a file time at least many seconds less
-# than the current time, corresponding to the time scale for a human
-# run-edit-run cycle.
+# Note that typically an invocation of latexmk's processing of a document
+# occurs after some human action, e.g., editting a document or a
+# configuration file. So a file that is left over from a previous run and
+# not overwritten on the current run will have a file time at least many
+# seconds less than the current time, corresponding to the time scale for a
+# human run-edit-run cycle. So one does NOT have to particularly precise
+# about time differences.
#
-# Note that the making or not making of a file is controlled by the
-# state of the document being compiled and by latexmk's configuration.
-# So a file that is left over from a previous run and not overwritten
-# on the current run will have a file time at least many seconds less
-# than the current time, corresponding to the time scale for a human
-# run-edit-run cycle. So one does NOT have to tune this variable
-# precisely.
-#
-# Concerning granularity of file system
-# FAT file system: 2 sec granularity. Others 1 sec or less.
-# Perl CORE's mtime in stat: 1 sec.
-# Perl CORE's time(): 1 sec. Time::HiRes::time(): Much less than 1 sec.
+# Granularity of file system etc:
+# FAT file system: 2 sec granularity. Others 1 sec or often much less.
+#
+# Functions available to latexmk from Perl:
+# mtime from Perl's CORE::stat: 1 sec, but 2 sec on FAT file system;
+# mtime from Time_HiRes::stat: can be much less than 1 sec, if the
+# combination of Perl, the OS and the file system support it.
+# system time from CORE::time(): 1 sec;
+# system time from Time::HiRes::time(): Much less than 1 sec.
+# Variables controlling the assessment of time offset between file system
+# and computer:
+
our $filetime_causality_threshold = 5;
+ # This is the size of time differences below which latexmk doesn't
+ # worry. It allows for (a) different granularity between system time
+ # and filesystem time, (b) for a modest mismatch between file and system
+ # time. This allowance can be generous; it merely needs to be below the
+ # human time-scale for editing documents, reconfiguring (or
+ # misconfiguring) latexmk, etc.
+our $filetime_offset_measured = 0; # Measurement not yet done.
+our $filetime_offset = 0; # Filetime relative to system time.
+ # Assume zero to start (corresponding to
+ # local file system).
+ # Will be updated if necessary.
+our $filetime_offset_report_threshold = 10; # Threshold beyond which filetime offsets
+ # are reported at end of run; large
+ # offsets indicate incorrect system
+ # time on at least one system.
+
+
################################################################
################################################################
@@ -1008,6 +1071,7 @@
$ps_previewer_landscape = $ps_previewer;
$dvi_previewer = 'start %O %S';
$dvi_previewer_landscape = "$dvi_previewer";
+ $hnt_previewer = 'start %O %S';
# Viewer update methods:
# 0 => auto update: viewer watches file (e.g., gv)
# 1 => manual update: user must do something: e.g., click on window.
@@ -1020,6 +1084,7 @@
# specified by the variables $dvi_update_command,
# $ps_update_command, $pdf_update_command
$dvi_update_method = 1;
+ $hnt_update_method = 1;
$ps_update_method = 1;
$pdf_update_method = 3; # acroread locks the pdf file
}
@@ -1110,6 +1175,7 @@
$ps_previewer_landscape = $ps_previewer;
$dvi_previewer = "$start_NT %O %S";
$dvi_previewer_landscape = $dvi_previewer;
+ $hnt_previewer = "$start_NT %O %S";
# Viewer update methods:
# 0 => auto update: viewer watches file (e.g., gv)
# 1 => manual update: user must do something: e.g., click on window.
@@ -1119,6 +1185,7 @@
# 3 => viewer can't update, because it locks the file and the file
# cannot be updated. (acroread under MSWIN)
$dvi_update_method = 1;
+ $hnt_update_method = 1;
$ps_update_method = 1;
$pdf_update_method = 3; # acroread locks the pdf file
}
@@ -1129,6 +1196,7 @@
$pdf_previewer = q[sh -c 'start %S'];
$ps_previewer = q[sh -c 'start %S'];
$dvi_previewer = q[sh -c 'start %S'];
+ $hnt_previewer = q[sh -c 'start %S'];
$ps_previewer_landscape = $ps_previewer;
$dvi_previewer_landscape = "$dvi_previewer";
}
@@ -1253,6 +1321,8 @@
# does not deal with changed dvi files, as far as I can see.
$pdf_previewer = 'open %S';
$pdf_update_method = 1; # manual
+ $hnt_previewer = 'open %S';
+ $hnt_update_method = 1; # manual
$dvi_previewer = $dvi_previewer_landscape = 'NONE';
$ps_previewer = $ps_previewer_landscape = 'NONE';
# Others
@@ -1310,11 +1380,6 @@
# This variable is obsolete, and only in here for
# backward compatibility.
-$fdb_ext = 'fdb_latexmk'; # Extension for the file for latexmk's
- # file-database
- # Make it long to avoid possible collisions.
-$fdb_ver = 4; # Version number for kind of fdb_file.
-
$jobname = ''; # Jobname: as with current tex, etc indicates
# basename of generated files. Defined so
# that --jobname=STRING on latexmk's command
@@ -1347,7 +1412,10 @@
$max_logfile_warnings = 7; # Max. # number of log file warnings to report
$rc_report = 1; # Whether to report on rc files read
$aux_out_dir_report = 0; # Whether to report on aux_dir & out_dir after
- # initialization and normalization
+ # initialization and normalization.
+ # When $aux_out_dir_report is set to 2, latexmk
+ # does no further processing after the report of
+ # the aux and out directories.
$kpsewhich_show = 0; # Show calls to and results from kpsewhich
$landscape_mode = 0; # default to portrait mode
@@ -1380,7 +1448,7 @@
# Which kinds of file do I have requests to make?
-our ($dvi_mode, $pdf_mode, $postscript_mode, $xdv_mode,
+our ($dvi_mode, $hnt_mode, $pdf_mode, $postscript_mode, $xdv_mode,
$cleanup_mode, $force_mode, $go_mode, $landscape_mode, $preview_mode, $preview_continuous_mode, $printout_mode );
# If no requests at all are made, then I will make dvi file
# If particular requests are made then other files may also have to be
@@ -1390,6 +1458,7 @@
# 0: no request for dvi file
# 1: use latex to make dvi file
# 2: use dvilualatex to make dvi file
+$hnt_mode = 0; # No hnt file requested
$postscript_mode = 0; # No postscript file requested
$pdf_mode = 0; # No pdf file requested to be made by pdflatex
# Possible values:
@@ -1402,6 +1471,7 @@
$xdv_mode = 0; # No xdv file requested
$view = 'default'; # Default preview is of highest of dvi, ps, pdf
+$min_sleep_time = 0.01; # Minimum non-zero sleep time
$sleep_time = 2; # time to sleep b/w checks for file changes in -pvc mode
$banner = 0; # Non-zero if we have a banner to insert
$banner_scale = 220; # Original default scale
@@ -1460,8 +1530,8 @@
# Whether times computed are clock times (HiRes) since Epoch, or are
# processing times for this process and child processes, as reported by
# times(). Second is the best, if accurate. But on MSWin32, times()
-# appears not to included subprocess times, so we use clock time instead.
-our $times_are_clock = ($^O eq "MSWin32" );
+# appears not to include subprocess times, so we use clock time instead.
+our $times_are_clock = ($^O eq "MSWin32" ? 1 : 0);
# Data for 1 run and global (ending in '0'):
@@ -1830,6 +1900,8 @@
# of the current rule. That must not trigger
# another run.
# The values for the hash are currently unused, only the keys.
+ # (Some packages that exhibit the
+ # rewrite-before-read behavior: pythontex, showexpl.)
# 4: {Hash source_rule -> last_pass }
# This lists rules that are to be considered source
# rules for the current rule, separately from the
@@ -1861,7 +1933,17 @@
# way is that the source_rule passes files (or
# other information) to the current rule, and that
# the current rule is to be rerun whenever the
- # source_rule has been run.
+ # source_rule has been run.
+ # 5: {Hash keys -> values}
+ # Used for any extra information needed for a specific
+ # rule. The first one I'll set up is for cached
+ # datasource information for the biber rule. The
+ # key is 'bcf_datasources', and the value is a
+ # reference to a hash mapping filename
+ # specifications in the bcf file to actual files
+ # (if found).
+ # The aim of this item is for flexible
+ # rule-dependent add-ons.
%fdb_current = (); # Hash of information for all files used.
# It maps filename to a reference to an array
@@ -2037,9 +2119,11 @@
$dependents_list = 1;
}
elsif (/^-diagnostics/) { $diagnostics = 1; }
+ elsif (/^-dir-report-only$/) { $aux_out_dir_report = 2; }
elsif (/^-dir-report$/) { $aux_out_dir_report = 1; }
elsif (/^-dir-report-$/) { $aux_out_dir_report = 0; }
elsif (/^-dvi$/) { $dvi_mode = 1;
+ $hnt_mode = 0;
if ( ($pdf_mode != 2) && ($pdf_mode != 3) ) {
# if pdf_mode is not via dvi or pdf, turn it off
$pdf_mode = 0;
@@ -2046,6 +2130,7 @@
}
}
elsif (/^-dvilua$/) { $dvi_mode = 2;
+ $hnt_mode = 0;
if ( ($pdf_mode != 2) && ($pdf_mode != 3) ) {
# if pdf_mode is not via dvi or pdf, turn it off
$pdf_mode = 0;
@@ -2068,6 +2153,9 @@
$go_mode = 3;
}
elsif ( /^-h$/ || /^-help$/ ) { &print_help; exit;}
+ elsif (/^-hnt$/) { $hnt_mode = 1;
+ $dvi_mode = $postscript_mode = $pdf_mode = 0;
+ }
elsif (/^-jobname=(.*)$/) {
$jobname = $1;
}
@@ -2077,6 +2165,7 @@
$pdf_mode = 0;
$postscript_mode = 0;
$dvi_mode = 1;
+ $hnt_mode = 0;
}
elsif (/^-latex=(.*)$/) {
$latex = $1;
@@ -2094,7 +2183,7 @@
{ $silence_logfile_warnings = 1; }
elsif ( /^-lualatex$/ || /^-pdflualatex$/ ) {
$pdf_mode = 4;
- $dvi_mode = $postscript_mode = 0;
+ $dvi_mode = $hnt_mode = $postscript_mode = 0;
}
# See below for -lualatex=...
# See above for -M
@@ -2130,6 +2219,7 @@
my $format = $1;
if ($format eq 'dvi' ) {
$dvi_mode = 1;
+ $hnt_mode = 0;
if ( ($pdf_mode != 2) && ($pdf_mode != 3) ) {
# if pdf_mode is not via dvi or pdf, turn it off
$pdf_mode = 0;
@@ -2137,7 +2227,7 @@
}
elsif ($format eq 'pdf' ) {
$pdf_mode = 1;
- $dvi_mode = $postscript_mode = 0;
+ $dvi_mode = $hnt_mode = $postscript_mode = 0;
}
else {
warn "$My_name: unknown format in option '$_'\n";
@@ -2149,16 +2239,16 @@
$preview_mode = 0;
}
elsif (/^-p-$/) { $printout_mode = 0; }
- elsif (/^-pdf$/) { $pdf_mode = 1; $dvi_mode = $postscript_mode = 0; }
+ elsif (/^-pdf$/) { $pdf_mode = 1; $dvi_mode = $hnt_mode = $postscript_mode = 0; }
elsif (/^-pdf-$/) { $pdf_mode = 0; }
- elsif (/^-pdfdvi$/){ $pdf_mode = 3; }
- elsif (/^-pdflua$/){ $pdf_mode = 4; $dvi_mode = $postscript_mode = 0; }
- elsif (/^-pdfps$/) { $pdf_mode = 2; }
- elsif (/^-pdfxe$/) { $pdf_mode = 5; $dvi_mode = $postscript_mode = 0; }
+ elsif (/^-pdfdvi$/){ $pdf_mode = 3; $hnt_mode = 0; }
+ elsif (/^-pdflua$/){ $pdf_mode = 4; $dvi_mode = $hnt_mode = $postscript_mode = 0; }
+ elsif (/^-pdfps$/) { $pdf_mode = 2; $hnt_mode = 0; }
+ elsif (/^-pdfxe$/) { $pdf_mode = 5; $dvi_mode = $hnt_mode = $postscript_mode = 0; }
elsif (/^-pdflatex$/) {
$pdflatex = "pdflatex %O %S";
$pdf_mode = 1;
- $dvi_mode = $postscript_mode = 0;
+ $dvi_mode = $hnt_mode = $postscript_mode = 0;
}
elsif (/^-pdflatex=(.*)$/) {
$pdflatex = $1;
@@ -2246,6 +2336,7 @@
elsif (/^-verbose$/) { $silent = 0; }
elsif (/^-view=default$/) { $view = "default";}
elsif (/^-view=dvi$/) { $view = "dvi";}
+ elsif (/^-view=hnt$/) { $view = "hnt";}
elsif (/^-view=none$/) { $view = "none";}
elsif (/^-view=ps$/) { $view = "ps";}
elsif (/^-view=pdf$/) { $view = "pdf"; }
@@ -2254,7 +2345,7 @@
elsif (/^-xdv-$/) { $xdv_mode = 0; }
elsif ( /^-xelatex$/ || /^-pdfxelatex$/ ) {
$pdf_mode = 5;
- $dvi_mode = $postscript_mode = 0;
+ $dvi_mode = $hnt_mode = $postscript_mode = 0;
}
# See above for -xelatex=...
elsif (/^-e$/) {
@@ -2318,6 +2409,7 @@
)
{
push @extra_dvilualatex_options, $original;
+ push @extra_hilatex_options, $original;
push @extra_latex_options, $original;
push @extra_pdflatex_options, $original;
push @extra_lualatex_options, $original;
@@ -2490,6 +2582,7 @@
# Add common options
add_option( $dvilualatex_default_switches, \$dvilualatex );
+add_option( $hilatex_default_switches, \$hilatex );
add_option( $latex_default_switches, \$latex );
add_option( $pdflatex_default_switches, \$pdflatex );
add_option( $lualatex_default_switches, \$lualatex );
@@ -2496,6 +2589,7 @@
add_option( $xelatex_default_switches, \$xelatex );
foreach (@extra_dvilualatex_options) { add_option( $_, \$dvilualatex ); }
+foreach (@extra_hilatex_options) { add_option( $_, \$hilatex ); }
foreach (@extra_latex_options) { add_option( $_, \$latex ); }
foreach (@extra_pdflatex_options) { add_option( $_, \$pdflatex ); }
foreach (@extra_lualatex_options) { add_option( $_, \$lualatex ); }
@@ -2527,6 +2621,7 @@
if ( $silent ) {
add_option( "$dvilualatex_silent_switch", \$dvilualatex );
+ add_option( "$hilatex_silent_switch", \$hilatex );
add_option( "$latex_silent_switch", \$latex );
add_option( "$pdflatex_silent_switch", \$pdflatex );
add_option( "$lualatex_silent_switch", \$lualatex );
@@ -2540,7 +2635,7 @@
}
if ( $recorder ) {
- add_option( "-recorder", \$dvilualatex, \$latex, \$pdflatex, \$lualatex, \$xelatex );
+ add_option( "-recorder", \$dvilualatex, \$hilatex, \$latex, \$pdflatex, \$lualatex, \$xelatex );
}
# If the output and/or aux directories are specified, fix the *latex
@@ -2552,20 +2647,21 @@
if ( $jobname ne '' ) {
# Since $jobname may include placeholder(s), put %R placeholder
# in option, and let %R be substituted by actual jobname at runtime.
- add_option( "--jobname=%R", \$dvilualatex, \$latex, \$lualatex, \$pdflatex, \$xelatex );
+ add_option( "--jobname=%R", \$dvilualatex, \$hilatex, \$latex, \$lualatex, \$pdflatex, \$xelatex );
}
# Make sure we make the kind of file we want to view:
if ( ($view eq 'dvi') && ($dvi_mode == 0) ) { $dvi_mode = 1; }
-if ($view eq 'ps') { $postscript_mode = 1; }
+if ( ($view eq 'hnt') && ($hnt_mode == 0) ) { $hnt_mode = 1; }
+if ( $view eq 'ps' ) { $postscript_mode = 1; }
if ( ($view eq 'pdf') && ($pdf_mode == 0) ) {
$pdf_mode = 1;
}
# Make sure that we make something if all requests are turned off
-unless ( $dvi_mode || $pdf_mode || $postscript_mode || $printout_mode || $xdv_mode ) {
+unless ( $dvi_mode || $hnt_mode || $pdf_mode || $postscript_mode || $printout_mode || $xdv_mode ) {
print "No specific requests made, so using default for $invoked_name.\n";
- ($dvi_mode, $postscript_mode, $pdf_mode, $xdv_mode )
+ ($dvi_mode, $hnt_mode, $postscript_mode, $pdf_mode, $xdv_mode )
= @{$compilation_defaults{$invoked_name}};
}
@@ -2576,8 +2672,9 @@
# that was requested by user.
# No explicit request means view dvi.
$view = "dvi";
+ if ( $hnt_mode ) { $view = "hnt"; }
+ if ( $pdf_mode ) { $view = "pdf"; }
if ( $postscript_mode ) { $view = "ps"; }
- if ( $pdf_mode ) { $view = "pdf"; }
}
# Determine requests.
@@ -2648,7 +2745,7 @@
if ( $preview_continuous_mode || $preview_mode ) { $one_time{'view'} = 1; }
$can_switch = $allow_switch;
-if ( $dvi_mode || $postscript_mode || $xdv_mode
+if ( $dvi_mode || $hnt_mode || $postscript_mode || $xdv_mode
|| ( $printout_mode && ($print_type eq 'ps') || ($print_type eq 'dvi') )
|| ( ($preview_mode || $preview_continuous_mode) && ( ($view eq 'ps') || ($view eq 'dvi') ) )
) {
@@ -2669,17 +2766,15 @@
add_option( "$dvips_pdf_switch", \$dvips );
}
-# Note sleep has granularity of 1 second.
-# Sleep periods 0 < $sleep_time < 1 give zero delay,
-# which is probably not what the user intended.
-# Sleep periods less than zero give infinite delay
+# Note that 100% CPU usage may not be terribly bad with a multi-core CPU,
+# and an SSD, especially when the OS caches file metadata reliably.
if ( $sleep_time == 0 ) {
warn "$My_name: sleep_time was configured to zero.\n",
" Do you really want to do this? It can give 100% CPU usage.\n";
}
-elsif ( $sleep_time < 1 ) {
- warn "$My_name: Correcting nonzero sleep_time of less than 1 sec to 1 sec.\n";
- $sleep_time = 1;
+elsif ( $sleep_time < $min_sleep_time ) {
+ warn "$My_name: Correcting nonzero sleep_time of less than $min_sleep_time sec to $min_sleep_time sec.\n";
+ $sleep_time = $min_sleep_time;
}
@@ -2779,6 +2874,7 @@
local $out_dir = $out_dir;
local $dvilualatex = $dvilualatex;
+ local $hilatex = $hilatex;
local $latex = $latex;
local $lualatex = $lualatex;
local $pdflatex = $pdflatex;
@@ -2992,8 +3088,12 @@
}
if ( !$force_mode ) {
warn
- "$My_name: If appropriate, the -f option can be used to get latexmk\n",
- " to try to force complete processing.\n";
+ "$My_name: Sometimes, the -f option can be used to get latexmk\n",
+ " to try to force complete processing.\n",
+ " But normally, you will need to correct the file(s) that caused the\n",
+ " error, and then rerun latexmk.\n",
+ " In some cases, it is best to clean out generated files before rerunning\n",
+ " latexmk after you've corrected the files.\n";
}
exit 12;
}
@@ -3028,7 +3128,7 @@
# Initialize timing for one run.
@timings1 = ();
$processing_time1 = processing_time();
- $clock1 = Time::HiRes::time();
+ $clock1 = time();
}
############################
@@ -3055,7 +3155,7 @@
", of which invoked processes = $invoked_time, other = ",
sprintf( '%.2f', $processing_time-$invoked_time ), ".\n";
print "Elapsed clock time = ",
- sprintf( '%.2f', Time::HiRes::time()-$clock1 ), ".\n";
+ sprintf( '%.2f', time()-$clock1 ), ".\n";
print "Number of rules run = ", 1+$#timings1, "\n";
}
@@ -3315,6 +3415,9 @@
print "$My_name: Cwd: '", good_cwd(), "'\n";
print "$My_name: Normalized aux dir and out dir: '$aux_dir', '$out_dir'\n";
print "$My_name: and combining forms: '$aux_dir1', '$out_dir1'\n";
+ if ($aux_out_dir_report == 2) {
+ exit 0;
+ }
}
} #END normalize_aux_out_ETC
@@ -3338,13 +3441,13 @@
# the relevant files (.pdf, .ps, .dvi, .xdv, .fls to the output
# directory after running *latex.
add_option( "-output-directory=%V",
- \$dvilualatex, \$latex, \$pdflatex, \$lualatex, \$xelatex );
+ \$dvilualatex, \$hilatex, \$latex, \$pdflatex, \$lualatex, \$xelatex );
}
}
else {
if ( $out_dir && ($out_dir ne '.') ) {
add_option( "-output-directory=%W",
- \$dvilualatex, \$latex, \$pdflatex, \$lualatex, \$xelatex );
+ \$dvilualatex, \$hilatex, \$latex, \$pdflatex, \$lualatex, \$xelatex );
}
if ( $aux_dir ne $out_dir ) {
# N.B. If $aux_dir and $out_dir are the same, then the
@@ -3351,7 +3454,7 @@
# -output-directory option is sufficient, especially because
# the -aux-directory exists only in MiKTeX, not in TeXLive.
add_option( "-aux-directory=%V",
- \$dvilualatex, \$latex, \$pdflatex, \$lualatex, \$xelatex );
+ \$dvilualatex, \$hilatex, \$latex, \$pdflatex, \$lualatex, \$xelatex );
}
}
} #END set_aux_out_options
@@ -3360,7 +3463,7 @@
sub fix_cmds {
# If commands do not have placeholders for %S etc, put them in
- foreach ($latex, $lualatex, $pdflatex, $xelatex, $lpr, $lpr_dvi, $lpr_pdf,
+ foreach ($hilatex, $latex, $lualatex, $pdflatex, $xelatex, $lpr, $lpr_dvi, $lpr_pdf,
$pdf_previewer, $ps_previewer, $ps_previewer_landscape,
$dvi_previewer, $dvi_previewer_landscape,
$kpsewhich
@@ -3414,10 +3517,13 @@
# (The rule database may get overridden/extended after the fdb_latexmk
# file is read, and after running commands to adjust to dependencies
# determined from document.
+
%rule_db = ();
%target_rules = ();
%target_files = ();
-
+ %actives = ();
+ %from_rules = ();
+
local %rule_list = ();
&rdb_set_rule_templates;
@@ -3474,10 +3580,12 @@
elsif ($pdf_mode == 4) { $current_primary = 'lualatex'; }
elsif ($pdf_mode == 5) { rdb_activate( 'xdvipdfmx' ); $current_primary = 'xelatex'; }
if ($dvi_mode == 2) { $current_primary = 'dvilualatex'; }
+ if ($hnt_mode) { $current_primary = 'hilatex'; }
rdb_activate( $current_primary );
if ($dvi_mode) { $target_files{$dvi_final} = 1; }
+ if ($hnt_mode) { $target_files{$hnt_final} = 1; }
if ($postscript_mode) { $target_files{$ps_final} = 1; }
if ($pdf_mode) { $target_files{$pdf_final} = 1; }
if ($xdv_mode) { $target_files{$xdv_final} = 1; }
@@ -3518,7 +3626,7 @@
my $viewer_update_signal = undef;
my $viewer_update_command = undef;
- if ( ($view eq 'dvi') || ($view eq 'pdf') || ($view eq 'ps') ) {
+ if ( ($view eq 'dvi') || ($view eq 'hnt') || ($view eq 'pdf') || ($view eq 'ps') ) {
$view_file = ${$view.'_final'};
$viewer = ${$view.'_previewer'};
$viewer_update_method = ${$view.'_update_method'};
@@ -3532,6 +3640,7 @@
%rule_list = (
'dvilualatex' => [ 'primary', "$dvilualatex", '', "%T", $dvi_name, "%R", 1, [$aux_main, $log_name], [$aux_main] ],
+ 'hilatex' => [ 'primary', "$hilatex", '', "%T", $hnt_name, "%R", 1, [$aux_main, $log_name], [$aux_main] ],
'latex' => [ 'primary', "$latex", '', "%T", $dvi_name, "%R", 1, [$aux_main, $log_name], [$aux_main] ],
'lualatex' => [ 'primary', "$lualatex", '', "%T", $pdf_name, "%R", 1, [$aux_main, $log_name], [$aux_main] ],
'pdflatex' => [ 'primary', "$pdflatex", '', "%T", $pdf_name, "%R", 1, [$aux_main, $log_name], [$aux_main] ],
@@ -3770,7 +3879,7 @@
my @files_to_delete = ();
@dirs = ($aux_dir1);
if ($out_dir1 ne $aux_dir1) { push @dirs, $out_dir1; }
-
+
push @files_to_delete, &get_small_cleanup;
if ($kind == 1) {
foreach my $dir1 (@dirs) {
@@ -3785,6 +3894,8 @@
# sort deletes contents of directory before attempting to delete the
# directory:
unlink_or_move( reverse sort @files_to_delete );
+
+
# If the fdb file (or log, fls and/or aux files) exist, it/they will have
# been used to make a changed rule database. But a cleanup implies
@@ -4188,7 +4299,7 @@
$quell_uptodate_msgs = 1;
- if ( ($view eq 'dvi') || ($view eq 'pdf') || ($view eq 'ps') ) {
+ if ( ($view eq 'dvi') || ($view eq 'hnt') || ($view eq 'pdf') || ($view eq 'ps') ) {
print "Viewing $view\n";
}
elsif ( $view eq 'none' ) {
@@ -4579,7 +4690,7 @@
sub traceback {
# Call: traceback()
# or traceback( message )
- # NOT &traceback!!!
+ # NOT &traceback, normally!!!
my $msg = shift;
if ($msg) { warn "$msg\n"; }
warn "Traceback:\n";
@@ -4676,7 +4787,10 @@
" and turn on showing of dependency list\n",
" -dF <filter> - Filter to apply to dvi file\n",
" -dir-report - Before processing a tex file, report aux and out dir settings\n",
- " -dir-report- - Before processing a tex file, do not report aux and out dir settings\n",
+ " -dir-report- - Before processing a tex file, do not report aux and out dir\n",
+ " settings\n",
+ " -dir-report-only - Report aux and out dir settings after initialization\n",
+ " and previous option processing, and then stop\n",
" -dvi - generate dvi by latex\n",
" -dvilua - generate dvi by dvilualatex\n",
" -dvi- - turn off required dvi\n",
@@ -4695,6 +4809,7 @@
" -g - process at least one run of all rules\n",
" -g- - Turn off -g and -gg\n",
" -h - print help\n",
+ " -hnt - generate hnt by hilatex\n",
" -help - print help\n",
" -indexfudge or -makeindexfudge - change directory to output directory when running makeindex\n",
" -indexfudge- or -makeindexfudge- - don't change directory when running makeindex\n",
@@ -4795,6 +4910,7 @@
" -version - display program version\n",
" -view=default - viewer is default (dvi, ps, pdf)\n",
" -view=dvi - viewer is for dvi\n",
+ " -view=hnt - viewer is for hnt\n",
" -view=none - no viewer is used\n",
" -view=ps - viewer is for ps\n",
" -view=pdf - viewer is for pdf\n",
@@ -4823,6 +4939,7 @@
sub print_commands {
print "Commands used by $my_name:\n",
+ " To run hilatex, I use \"$hilatex\"\n",
" To run latex, I use \"$latex\"\n",
" To run pdflatex, I use \"$pdflatex\"\n",
" To run dvilualatex, I use \"$dvilualatex\"\n",
@@ -4844,6 +4961,7 @@
" To view a dvi file, I use \"$dvi_previewer\"\n",
" To view a dvi file in landscape format, ",
"I use \"$dvi_previewer_landscape\"\n",
+ " To view an hnt file, I use \"$hnt_previewer\"\n",
" To print a ps file, I use \"$lpr\"\n",
" To print a dvi file, I use \"$lpr_dvi\"\n",
" To print a pdf file, I use \"$lpr_pdf\"\n",
@@ -4865,44 +4983,147 @@
} #END view_file_via_temporary
#************************************************************
-#### Tex-related utilities
+#### Tex-related utilities #######################
+
#**************************************************
+sub after_biber {
+ # Analyze results of biber run, take appropriate actions on dependencies.
+ # Assumes rule context for biber
+ # Call
+ # after_biber( \$return ),
+ # where $return is code returned by running of biber (maybe modified by
+ # caller, which is normally rdb_run1). Can adjust its value to provoke
+ # better diagnosis of results of run to caller.
+ use strict;
+ # Rule variables used:
+ our ( $rule, $Pbase, $Pdest, $PHextra, $Plast_message, $Plast_result,
+ $Pout_of_date, $Psource, $PHsource );
+ # Global variables used
+ our ( %current_primaries, $diagnostics, $My_name, $save_error_suffix,
+ $silent );
+ my $Preturn = $_[0];
+ my @biber_datasource = ( );
+ my @biber_remote = ();
+ my @warnings = ();
+ my $add_bcf_datasources = 0;
+
+ my $retcode = check_biber_log( $$Pbase, \@biber_datasource, \@biber_remote );
+ if ($$Preturn) {
+ print
+ "$My_name: Error return from '$rule'\n",
+ "I will add to its source list, anything cached from analysis of bcf file.\n";
+ $add_bcf_datasources = 1;
+ }
+ if ( ! -e $$Psource ) {
+ $retcode = 10;
+ if (!$silent) {
+ print "Source '$$Psource' for '$rule' doesn't exist,\n",
+ "so I'll force *latex to run to try and make it.\n";
+ }
+ rdb_for_some( [keys %current_primaries], sub{ $$Pout_of_date = 1; } );
+ }
+ rdb_set_source_here( @biber_datasource, $$Psource );
+
+ if ($retcode == 6) {
+ # Missing control file. Need to remake it (if possible)
+ # Don't treat missing bbl file as error.
+ print "$My_name: bibtex control file missing. Since that can\n",
+ " be recreated, I'll try to do so.\n";
+ $$Preturn = -2;
+ rdb_for_some( [keys %current_primaries], sub{ $$Pout_of_date = 1; } );
+ }
+ elsif ($retcode == 4) {
+ $$Plast_result = 2;
+ $$Plast_message = "Could not find all biber source files for '$$Pbase'";
+ push @warnings, "Not all biber source files found for '$$Pbase'";
+ }
+ elsif ($retcode == 3) {
+ $$Plast_result = 2;
+ $$Plast_message = "Could not open biber log file for '$$Pbase'";
+ $add_bcf_datasources = 1;
+ push @warnings, $$Plast_message;
+ }
+ elsif ($retcode == 2) {
+ $$Plast_message = "Biber errors: See file '$$Pbase.blg'";
+ push @warnings, $$Plast_message;
+ }
+ elsif ($retcode == 1) {
+ push @warnings, "Biber warnings for '$$Pbase'";
+ }
+ elsif ($retcode == 11) {
+ $$Plast_message = "Biber: malformed bcf file '$$Psource'";
+ push @warnings, $$Plast_message;
+ my $save_bcf = "$$Psource$save_error_suffix";
+ warn "$My_name: biber found malformed bcf file '$$Psource'.\n",
+ " I'll delete any bbl file '$$Pdest', and\n",
+ " rename the bcf file to '$save_bcf'\n";
+ # Malformed bcf file is a downstream consequence, normally,
+ # of an error in *latex run.
+ # Current version of biber deletes bbl file.
+ # Older versions (pre-2016) made an incorrect bbl file, which
+ # tended to cause latex errors, and give a self-perpetuating error.
+ # Ensure the bbl file doesn't exist.
+ # I could delete the bcf file, since it is not usable. But in
+ # non-trivial cases, the user may want to examine the file, so
+ # I'll rename it instead. (Trivial common case: *latex exited
+ # early because of an error, and the resulting bcf file is
+ # incomplete. I should have deleted the file after the error
+ # run of *latex, since there is then no value in the bcf for
+ # diagnostics.)
+ unlink $$Pdest;
+ rename $$Psource, $save_bcf;
+ }
+ if ($add_bcf_datasources) {
+ my $PA_bcf_datasources = $$PHextra{bcf_datasources};
+ if ( ref($PA_bcf_datasources) eq 'ARRAY' ) {
+ rdb_ensure_files_here( @$PA_bcf_datasources );
+ }
+ }
+} #END after_biber
+
+#**************************************************
+
sub check_biber_log {
# Check for biber warnings, and report source files.
- # Usage: check_biber_log( base_of_biber_run, \@biber_datasource )
+ # Usage: check_biber_log( base_of_biber_run, \@datasource, \@remote )
+ # I use a hash for the collection of significant warnings. It maps
+ # categories of warnings to array references (or c.) to allow
+ # flexibility in what I report.
+ # (Return codes compatible with check_bibtex_log, but only used when applicable.)
# return 0: OK;
# 1: biber warnings;
# 2: biber errors;
# 3: could not open .blg file;
# 4: failed to find one or more source files, except for bibfile;
- # 5: failed to find bib file;
- # 6: missing file, one of which is control file
- # 10: only error is missing \citation commands.
+ # 6: missing file;
# 11: Malformed bcf file (normally due to error in pdflatex run)
- # Side effect: add source files @biber_datasource
- # N.B. @biber_datasource is already initialized by caller.
+ # Side effect: add source files to @datasource
+ # N.B. @datasource is already initialized by caller.
# So do **not** initialize it here.
- my $base = $_[0];
- my $Pbiber_datasource = $_[1];
+ use strict;
+ # Global variables used
+ our ($My_name, $silent);
+
+ my ($base, $PAdatasource, $PAremote ) = @_;
my $blg_name = "$base.blg";
open( my $blg_file, "<", $blg_name )
or return 3;
my $have_warning = 0;
my $have_error = 0;
- my $missing_citations = 0;
my $no_citations = 0;
my $error_count = 0; # From my counting of error messages
my $warning_count = 0; # From my counting of warning messages
# The next two occur only from biber
- my $bibers_error_count = 0; # From biber's counting of errors
- my $bibers_warning_count = 0; # From biber's counting of warnings
+ my $biber_error_count = 0; # From biber's counting of errors
+ my $biber_warning_count = 0; # From biber's counting of warnings
my $not_found_count = 0;
my $control_file_missing = 0;
my $control_file_malformed = 0;
- my %remote = (); # List of extensions of remote files
my @not_found = (); # Files, normally .bib files, not found.
+ my @missing_citations = ();
+
while (<$blg_file>) {
$_ = utf8_to_mine($_);
if (/> WARN /) {
@@ -4910,7 +5131,9 @@
$have_warning = 1;
$warning_count ++;
}
- elsif (/> (FATAL|ERROR) /) {
+ # Note that WARN is not exclusive with some of the following,
+ # so we can't use elsif here
+ if (/> (FATAL|ERROR) /) {
print "Biber error: $_";
if ( /> (FATAL|ERROR) - Cannot find file '([^']+)'/ #'
|| /> (FATAL|ERROR) - Cannot find '([^']+)'/ ) { #'
@@ -4930,16 +5153,11 @@
else {
$have_error = 1;
$error_count ++;
- if ( /> (FATAL|ERROR) - The file '[^']+' does not contain any citations!/ ) { #'
- $no_citations++;
- }
}
}
elsif ( /> INFO - Data source '([^']*)' is a remote BibTeX data source - fetching/
){
- my $spec = $1;
- my ( $base, $path, $ext ) = fileparseA( $spec );
- $remote{$ext} = 1;
+ push @$PAremote, $1;
}
elsif ( /> INFO - Found .* '([^']+)'\s*$/
|| /> INFO - Found '([^']+)'\s*$/
@@ -4946,10 +5164,11 @@
|| /> INFO - Reading '([^']+)'\s*$/
|| /> INFO - Processing .* file '([^']+)'.*$/
|| /> INFO - Config file is '([^']+)'.*$/
+ || /> WARN - Data source .*'([^']+)'.*$/
) {
my $file = $1;
my ( $base, $path, $ext ) = fileparseA( $file );
- if ($remote{$ext} && ( $base =~ /^biber_remote_data_source/ ) && 1) {
+ if ( $base =~ /^biber_remote_data_source/ ) {
# Ignore the file, which appears to be a temporary local copy
# of a remote file. Treating the file as a source file will
# be misleading, since it will normally have been deleted by
@@ -4963,33 +5182,32 @@
# copy of a remote file).
# So I have included a condition above that the file must
# exist to be included in the source-file list.
- push @$Pbiber_datasource, $file;
+ push @$PAdatasource, $file;
}
}
+ elsif ( /> WARN - I didn't find a database entry for '([^']+)'/ ) {
+ push @missing_citations, $1;
+ }
elsif ( /> INFO - WARNINGS: ([\d]+)\s*$/ ) {
- $bibers_warning_count = $1;
+ $biber_warning_count = $1;
}
elsif ( /> INFO - ERRORS: ([\d]+)\s*$/ ) {
- $bibers_error_count = $1;
+ $biber_error_count = $1;
}
}
close $blg_file;
- @$Pbiber_datasource = uniqs( @$Pbiber_datasource );
+ @$PAdatasource = uniqs( @$PAdatasource );
+ @$PAremote = uniqs( @$PAremote );
@not_found = uniqs( @not_found );
- push @$Pbiber_datasource, @not_found;
+ push @$PAdatasource, @not_found;
if ($control_file_malformed){return 11;}
- if ( ($#not_found < 0) && ($#$Pbiber_datasource >= 0) ) {
- print "$My_name: Found biber source file(s) [@$Pbiber_datasource]\n"
+ if ( ($#not_found < 0) && ($#$PAdatasource >= 0) ) {
+ print "$My_name: Found biber source file(s) [",
+ join( ', ', @$PAdatasource), "]\n"
unless $silent;
}
- elsif ( ($#not_found == 0) && ($not_found[0] =~ /\.bib$/) ) {
- # Special treatment if sole missing file is bib file
- # I don't want to treat that as an error
- print "$My_name: Biber did't find bib file [$not_found[0]]\n";
- return 5;
- }
else {
warn "$My_name: Failed to find one or more biber source files:\n";
foreach (@not_found) { warn " '$_'\n"; }
@@ -5002,13 +5220,9 @@
}
return 4;
}
-# print "$My_name: #Biber errors = $error_count, warning messages = $warning_count,\n ",
-# "missing citation messages = $missing_citations, no_citations = $no_citations\n";
- if ( ! $have_error && $no_citations ) {
- # If the only errors are missing citations, or lack of citations, that should
- # count as a warning.
- # HOWEVER: biber doesn't generate a new bbl. So it is an error condition.
- return 10;
+ if ( @missing_citations ) {
+ @missing_citations = uniqs( @missing_citations );
+ show_array( "$My_name: Biber reported missing citations", @missing_citations );
}
if ($have_error) {return 2;}
if ($have_warning) {return 1;}
@@ -5018,6 +5232,12 @@
#**************************************************
sub run_bibtex {
+ use strict;
+ # Rule variables used
+ our ( $rule, $Pdest, $Psource );
+ # Global variables used
+ our ( $bibtex_fudge, $My_name, $silent );
+
my $return = 999;
# Prevent changes we make to environment becoming global:
local %ENV = %ENV;
@@ -5067,44 +5287,77 @@
#**************************************************
-sub run_makeindex {
- my $return = 999;
- my ( $base, $path, $ext ) = fileparseA( $$Psource );
+sub after_bibtex {
+ # Analyze results of bibtex run, take appropriate actions on dependencies.
+ # Assumes rule context for bibtex
+ # Call
+ # after_bibtex( \$return ),
+ # where $return is code returned by running of bibtex (maybe modified by
+ # caller, which is normally rdb_run1). Can adjust its value to provoke
+ # better diagnosis of results of run to caller.
- # Define source and dest base to include extension, no path.
- my $source_base = $base.$ext;
- my $dest_base = basename( $$Pdest );
- if ( $path && $makeindex_fudge ) {
- my $cwd = good_cwd();
- pushd( $path );
+ use strict;
+ # Rule variables used
+ our ( $rule, $Pbase, $Pdest, $Plast_message, $Plast_result,
+ $Pout_of_date, $Psource );
+ # Global variables used
+ our ( %current_primaries, $diagnostics, $failure, $My_name, $silent );
+
+ my $Preturn = $_[0];
+ my $retcode = check_bibtex_log($$Pbase);
+ my @warnings = ();
+
+ if ( ! -e $$Psource ) {
+ $retcode = 10;
if (!$silent) {
- print "$My_name: Change directory to '$path'.\n";
+ print "Source '$$Psource' for '$rule' doesn't exist,\n",
+ "so I'll force *latex to run to try and make it.\n";
}
- # Override standard substitutions for source, dest, and base names in
- # default external command:
- $return = &Run_subst( undef, undef, '', $source_base, $dest_base, $base );
- popd();
- if (!$silent) {
- print "$My_name: Change directory back to '$cwd'\n";
+ rdb_for_some( [keys %current_primaries], sub{ $$Pout_of_date = 1; } );
+ }
+ if ($retcode == 3) {
+ $$Plast_result = 2;
+ $$Plast_message = "Could not open bibtex log file for '$$Pbase'";
+ push @warnings, $$Plast_message;
+ }
+ elsif ($retcode == 2) {
+ $$Plast_message = "Bibtex errors: See file '$$Pbase.blg'";
+ $failure = 1;
+ push @warnings, $$Plast_message;
+ }
+ elsif ($retcode == 1) {
+ push @warnings, "Bibtex warnings for '$$Pbase'";
+ }
+ elsif ($retcode == 10) {
+ push @warnings, "Bibtex found no citations for '$$Pbase',\n",
+ " or had missing aux or bib file(s)\n";
+ if (! -e $$Pdest ) {
+ print "$My_name: Bibtex did not produce '$$Pdest'. But that\n",
+ " was because of missing files, so I will continue.\n";
+ $$Preturn = -2;
}
+ else {
+ $$Preturn = 0;
+ }
}
- else {
- # Use default substitutions etc for rule:
- $return = Run_subst();
- }
- return $return;
-} #END run_makeindex
-
+} #END after_bibtex
+
#**************************************************
sub check_bibtex_log {
- # Check for bibtex warnings:
+ # Check for bibtex warnings and errors:
# Usage: check_bibtex_log( base_of_bibtex_run )
+ # (Return codes compatible with check_biber_log, but only used when applicable.)
# return 0: OK, 1: bibtex warnings, 2: bibtex errors,
# 3: could not open .blg file.
# 10: only error is missing \citation commands or a missing aux file
# (which would normally be corrected after a later run of
# *latex).
+ use strict;
+ # Variable used in context of a rule action
+ our ( $Pout_of_date );
+ # Global variables used
+ our ( %current_primaries, $My_name );
my $base = $_[0];
my $blg_name = "$base.blg";
@@ -5112,8 +5365,9 @@
or return 3;
my $have_warning = 0;
my $have_error = 0;
- my $missing_citations = 0;
+ my $no_citations = 0;
my @missing_aux = ();
+ my @missing_bib = ();
my $error_count = 0;
while (<$blg_file>) {
$_ = utf8_to_mine($_);
@@ -5125,8 +5379,11 @@
push @missing_aux, $1;
}
elsif ( /^I found no \\citation commands---while reading file/ ) {
- $missing_citations++;
+ $no_citations++;
}
+ elsif ( /^I couldn't open database file (.*\.bib)/ ) {
+ push @missing_bib, $1;
+ }
elsif (/There (were|was) (\d+) error message/) {
$error_count = $2;
#print "Bibtex error: count=$error_count $_";
@@ -5134,7 +5391,7 @@
}
}
close $blg_file;
- my $missing = $missing_citations + $#missing_aux + 1;
+ my $weak_errors = $no_citations + $#missing_aux + 1 + $#missing_bib + 1;
if ( $#missing_aux > -1 ) {
# Need to make the missing files.
print "$My_name: One or more aux files is missing for bibtex. I'll try\n",
@@ -5142,17 +5399,21 @@
rdb_for_some( [keys %current_primaries], sub{ $$Pout_of_date = 1; } );
}
#print "Bibtex errors = $error_count, missing aux files and citations = $missing\n";
- if ($have_error && ($error_count <= $missing )
- && ($missing > 0) ) {
- # If the only error is a missing citation line, that should only
- # count as a warning.
- # Also a missing aux file should be innocuous; it will be created on
- # next run of *latex. ?? HAVE I HANDLED THAT CORRECTLY?
+ if ($have_error && ($error_count <= $weak_errors )
+ && ($weak_errors > 0) ) {
+ # If the only error(s), are:
+ # lack of any \citation commands in aux file
+ # missing aux file(s)
+ # missing bib file(s)
+ # that should count as a warning.
+ # Note that a missing aux file is generally innocuous, that's
+ # commonly because the document has an include of a file in a
+ # subdirectory, an aux dir is in use, and the sub directory hasn't
+ # yet been made in the aux dir. That situation should be handled
+ # by latexmk by creating the directory and rerunning *latex.
# But have to deal with the problem that bibtex gives a non-zero
- # exit code. So leave things as they are so that the user gets
- # a better diagnostic ??????????????????????????
-# $have_error = 0;
-# $have_warning = 1;
+ # exit code.
+ # Let caller know:
return 10;
}
if ($have_error) {return 2;}
@@ -5162,6 +5423,36 @@
#**************************************************
+sub run_makeindex {
+ my $return = 999;
+ my ( $base, $path, $ext ) = fileparseA( $$Psource );
+
+ # Define source and dest base to include extension, no path.
+ my $source_base = $base.$ext;
+ my $dest_base = basename( $$Pdest );
+ if ( $path && $makeindex_fudge ) {
+ my $cwd = good_cwd();
+ pushd( $path );
+ if (!$silent) {
+ print "$My_name: Change directory to '$path'.\n";
+ }
+ # Override standard substitutions for source, dest, and base names in
+ # default external command:
+ $return = &Run_subst( undef, undef, '', $source_base, $dest_base, $base );
+ popd();
+ if (!$silent) {
+ print "$My_name: Change directory back to '$cwd'\n";
+ }
+ }
+ else {
+ # Use default substitutions etc for rule:
+ $return = Run_subst();
+ }
+ return $return;
+} #END run_makeindex
+
+#**************************************************
+
sub normalize_force_directory {
# Usage, normalize_force_directory( dir, filename )
# Filename is assumed to be relative to dir (terminated with directory separator).
@@ -5214,6 +5505,7 @@
}
$dvi_name = "%Z%R.dvi";
$dviF_name = "%Z%R.dviF";
+ $hnt_name = "%Z%R.hnt";
$ps_name = "%Z%R.ps";
$psF_name = "%Z%R.psF";
$pdf_name = "%Z%R.pdf";
@@ -5224,7 +5516,7 @@
$xdv_name = "%Y%R.xdv";
foreach ( $aux_main, $log_name, $fdb_name, $fls_name, $fls_name_alt,
- $dvi_name, $ps_name, $pdf_name, $xdv_name, $dviF_name, $psF_name ) {
+ $dvi_name, $hnt_name, $ps_name, $pdf_name, $xdv_name, $dviF_name, $psF_name ) {
s/%R/$root_filename/g;
s/%Y/$aux_dir1/;
s/%Z/$out_dir1/;
@@ -5231,6 +5523,7 @@
}
$dvi_final = $dvi_name;
+ $hnt_final = $hnt_name;
$ps_final = $ps_name;
$pdf_final = $pdf_name;
$xdv_final = $xdv_name;
@@ -5257,12 +5550,11 @@
# *latex always produces a log file unless there is a bad error, so
# this gives the best chance of diagnosing errors.
my $where_log = &find_set_log;
-
if ( $emulate_aux && ($aux_dir ne $out_dir) ) {
# Move output files from aux_dir to out_dir
# Move fls file also, if the configuration is for fls in out_dir.
# Omit 'xdv', that goes to aux_dir (as with MiKTeX). It's not final output.
- foreach my $ext ( 'fls', 'dvi', 'pdf', 'ps', 'synctex', 'synctex.gz' ) {
+ foreach my $ext ( 'fls', 'dvi', 'hnt', 'pdf', 'ps', 'synctex', 'synctex.gz' ) {
if ( ($ext eq 'fls') && ! $fls_uses_out_dir ) {next;}
my $from = "$aux_dir1$root_filename.$ext";
my $to = "$out_dir1$root_filename.$ext" ;
@@ -5621,7 +5913,7 @@
# data structure until block is ended.)
my %new_conversions = ();
my $log_silent = ($silent || $silence_logfile_warnings);
- @warning_list = ();
+ @warning_list = (); # Warnings about undefined citations and the like
LINE:
for (@$PAlines) {
@@ -5712,7 +6004,7 @@
push @multiply_defined_references, $2;
$mult_defined++;
}
- elsif (/^LaTeX Warning: (Citation `([^']+)' on page .* undefined on input line .*)\./) {
+ elsif (/^LaTeX Warning: (Citation [`|']([^']+)' on page .* undefined on input line .*)\./) {
push @warning_list, $1;
push @undefined_citations, $2;
$bad_citation++;
@@ -6062,22 +6354,40 @@
# Quote inside filename. Probably misparse.
next INCLUDE_NAME;
}
+ # Most (but not all) implementations of TeX, put a non-empty path
+ # in name of file read in .log file. Flag the situation of no path
+ # separator in the file name: There's a high potential for misparse.
+ # Do this before normalizing filename, and analyzing its components.
+ my $no_path = ( $include_name !~ m'[/|\\]' );
$include_name = normalize_filename( $include_name, @pwd_log );
if ( ! defined $include_name ) { next INCLUDE_NAME; }
+ if ( ! -e $include_name ) { next INCLUDE_NAME; }
my ($base, $path, $ext) = fileparseB( $include_name );
if ( ($path eq './') || ($path eq '.\\') ) {
$include_name = $base.$ext;
}
- if ( $include_name !~ m'[/|\\]' ) {
- # Filename does not include a path character
- # High potential for misparsed line
+ if ( $no_path ) {
$dependents{$include_name} = 2;
} else {
$dependents{$include_name} = 3;
}
if ( $ext eq '.bbl' ) {
- print "$My_name: Found input bbl file '$include_name'\n"
- unless $silent;
+ if ( -e $include_name ) {
+ print "$My_name: Found input bbl file '$include_name'\n"
+ unless $silent;
+ }
+ else {
+ warn "$My_name: Bbl file '$include_name' is listed in .log file\n",
+ " as having been read, but it doesn't exist\n";
+ if ( ($path eq '') && ($aux_dir ne '' ) && ( -e "%aux_dir1$include_name" ) ) {
+ warn " But it's in '$aux_dir'\n",
+ " There's probably a bug in .log file writing\n";
+ $include_name = "%aux_dir1$include_name";
+ }
+ else {
+ next;
+ }
+ }
push @bbl_files, $include_name;
}
} # INCLUDE_NAME
@@ -6154,9 +6464,6 @@
# exists, then the missing file does not correspond
# to the missing file, unless the .tex file was
# created during the run.
- # OLD $dependents{"$path$base.tex"} = 4;
- # OLD delete $dependents{$candidate};
- # NEW:
$dependents{"$path$base.tex"} = 4;
}
push @missing, $candidate;
@@ -6279,6 +6586,11 @@
my ($file, $PAlines, $PHinfo) = @_;
# Where lines are wrapped at. We'll sometimes override.
+ # Note that TeXLive's hilatex, at least in TL 2023, with HINT 2.0,
+ # doesn't obey max_print_line environment or the corresponding
+ # -cnf-line option. They work for pdflatex.
+ # Similarly for MiKTeX 23.10.12's hilatex, which reports the same version of
+ # HINT.
local $log_wrap = $log_wrap;
# Lines held for wrapping:
@@ -6315,6 +6627,8 @@
# luatex: UTF-8 but with wrapping at APPROXIMATELY
# $log_wrap bytes. Rest as pdftex
# xetex: UTF-8 with wrapping at $log_wrap codepoints.
+ # hilatex: (TL 2023, HINT 2.0) Pure 7-bit ASCII with ^^
+ # encoding of non-ASCII. Wrapping at 79 bytes.
# So we read file as bytes. Then
# first line gives which program was used and hence whether to wrap
# according to byte or codepoint count.
@@ -6341,7 +6655,9 @@
}
$lua_mode = ( $engine =~ /lua.*tex/i );
# TeXLive's *tex take log wrap value from environment variable max_print_line, if it exists:
- if ( ($tex_distribution =~ /TeX\s*Live/) && $ENV{max_print_line} ) {
+ if ( ($tex_distribution =~ /TeX\s*Live/) &&
+ $ENV{max_print_line} ) {
+ # See comment earlier about hilatex.
$log_wrap = $ENV{max_print_line};
print "$My_name: changed column for log file wrapping from standard to $log_wrap\n".
" from env. var. max_print_line, which is obeyed by your TeXLive programs\n"
@@ -6401,7 +6717,10 @@
&$Pwrap_sub();
}
close($fh);
- foreach (@$PAlines) { $_ = utf8_to_mine($_); }
+ foreach (@$PAlines) {
+ hathat_to_binary( $_ ) if ( $conv_hathat && /\^\^/ );
+ $_ = utf8_to_mine($_);
+ }
push @$PAlines, ""; # Blank line to terminate. So multiline blocks
# are always terminated by non-block line, rather than eof.
$$PHinfo{max_len} = $max_len;
@@ -6586,6 +6905,28 @@
#************************************************************
+sub hathat_to_binary {
+ # Convert ^^ notation to bytes (log files from non-8bit configured latex).
+ # In-line conversion.
+ # Usage, e.g., hathat_to_binary( $line ) or hathat_to_binary( @array ).
+ #
+ foreach (@_){
+ next unless /\^\^/;
+ while ( /(\^\^([[:xdigit:]]{2}))/g ) {
+ my $match = $1;
+ my $hex = $2;
+ my $pos = pos($_); # Regex analyzer positioned after match
+ my $before = $pos - length($match);
+ pos($_) = $before;
+ my $subst = chr hex $hex;
+ s/\G\Q$match/$subst/;
+ pos($_) = $before + length($subst);
+ }
+ }
+}
+
+#==============================================
+
sub dirname_no_tail {
my $dirname = $_[0];
foreach ($dirname) {
@@ -6818,6 +7159,12 @@
push @$Paux_files, $aux_file;
AUX_LINE:
while (<$aux_fh>) {
+ if ( /\^\^/ ) {
+ warn "$My_name: Line in '$aux_file' uses ^^ notation, which may\n".
+ " cause trouble to bibtex:\n $_";
+ # At least I need to be able to handle the line:
+ hathat_to_binary( $_ ) if $conv_hathat;
+ }
$_ = utf8_to_mine($_);
s/\s$//;
if ( /^\\bibdata\{(.*)\}/ ) {
@@ -6863,69 +7210,145 @@
#************************************************************
sub parse_bcf {
- # Parse bcf file for bib and other source files.
- # Usage: parse_bcf( $bcf_file, \@new_bib_files )
+ # Parse bcf file for bib and other source files, and
+ # do an elementary test for completeness.
+ # Usage: parse_bcf( $bcf_file, \$status, \%bib_files, \@found,
+ # \@not_found, \@remote )
# If can't open bcf file, then
- # Return 0 and leave @new_bib_files empty
- # Else set @new_bib_files from information in the
- # bcf files
- # And:
- # Return 1 if no problems
- # Return 2 with @new_bib_files empty if there are no relevant source
- # file lines.
- # Return 3 if I couldn't locate all the bib_files
+ # Return with $status = 0 and the hash and arrays empy.
+ #
+ # Else set the hash and the arrays from information in the bcf_file,
+ # set $status to
+ # 1 if no problems
+ # 2 if there were no relevant datasource lines
+ # Note this is not an error! *latex & biber will not report an
+ # error, and will simply result in an empty b
+ # 3 if I couldn't locate all the bib_files
+ # 100 plus one of the codes 1..3 if the bcf file appears
+ # incomplete.
+ #
# A full parse of .bcf file as XML would need an XML parsing module, which
# is not in a default installation of Perl, notably in TeXLive's perl for
# Win32 platform. To avoid requiring the installation, just search the
# .bcf file for the relevant lines.
+ #
+ # !!!!!!!!!!!!!!!!!??????????? Allow for remote bib files.
- my $bcf_file = $_[0];
- my $Pbib_files = $_[1];
- # Default return value
- @$Pbib_files = ();
- # Map file specs (from datasource lines) to actual filenames:
- local %bib_files = ();
- my @not_found_bib = ();
+ use strict;
+ # Global variables used
+ our ( $My_name, $silent );
+
+ my ($bcf_file, $Pstatus, $PHbib_files, $PAfound, $PAnot_found, $PAremote ) = @_;
+ $$Pstatus = 0;
+ my %glob_names = ();
+ my @found = ();
+ my @not_found = ();
+ my %remote = ();
+
+ my $incomplete = 0; # Values 0 or 1
+
open(my $bcf_fh, $bcf_file)
|| do {
- warn "$My_name: Couldn't find bcf file '$bcf_file'\n";
- return 0;
+ warn "$My_name: Couldn't find bcf file '$bcf_file'\n";
};
+ $$Pstatus = 1;
while ( <$bcf_fh> ) {
$_ = utf8_to_mine($_);
- if ( /^\s*<bcf:datasource type=\"file\"\s+datatype=\"bibtex\"\s+glob=\"false\">(.+)<\/bcf:datasource>/ ) {
- $bib_files{$1} = '';
+ if (eof($bcf_fh)) {
+ if ( ! /^\s*<\/bcf:controlfile>/ ) {
+ warn "$My_name: Incomplete (and hence corrupt) bcf file '$bcf_file'\n";
+ $incomplete = 1;
+ }
}
+ if ( /^\s*<bcf:datasource type=\"file\"\s+datatype=\"bibtex\"\s*(.*)>(.+)<\/bcf:datasource>/ ) {
+ my $tail = $1; # Can contain a glob item, which will affect meaning of filename.
+ my $file = $2;
+ if ($file =~ /^http:|^https:|^ftp:|^ftps:/ ) { $remote{$file} = ''; }
+ elsif ($tail =~ /glob=\"true\"/ ) { $glob_names{$file} = ''; }
+ else { $$PHbib_files{$file} = ''; }
+ }
}
close $bcf_fh;
- find_files( \%bib_files, 'bib', 'bib', $Pbib_files, \@not_found_bib );
- if ( $#{$Pbib_files} == -1 ) {
- #
- print "$My_name: No .bib files listed in .bcf file '$bcf_file'\n";
- return 2;
+ foreach my $spec ( keys %glob_names ) {
+ my @result = glob $spec;
+ if ( ($#result == 0) && ($spec eq $result[0]) ) {
+ # There was no wild card, and glob just returned the given
+ # name, which applies whether or not the file exists.
+ # We'll treat is the same as a non-globbed name.
+ $$PHbib_files{$spec} = '';
+ delete $glob_names{$spec};
+ }
+ else {
+ foreach (@result) { $$PHbib_files{$_} = $_; }
+ }
}
+ foreach (keys %$PHbib_files) { if (-e) { $$PHbib_files{$_} = $_; } }
+ foreach my $spec (keys %$PHbib_files ) {
+ next if $$PHbib_files{$spec};
+ my @lines = kpsewhich( $spec );
+ if (@lines) { $$PHbib_files{$spec} = $lines[0]; }
+ }
+ while (my ($spec, $file) = each %$PHbib_files ) {
+ if ($file) { push @found, $file; }
+ else { push @not_found, $spec; }
+ }
- show_array( "$My_name: Bibliography file(s) from .bcf file:", @$Pbib_files )
+ @found = uniqs(@found);
+ @not_found = uniqs(@not_found);
+ push @$PAfound, @found;
+ push @$PAnot_found, @not_found;
+ push @$PAremote, sort keys %remote;
+
+ show_array( "$My_name: Bibliography file(s) from .bcf file:", sort( @found, @not_found ) )
unless $silent;
- if (@not_found_bib) {
- show_array(
- "Bib file(s) not found in search path:",
- @not_found_bib );
- }
- if (@not_found_bib) {
- if ($force_mode) {
+ if (@not_found) {
+ show_array( "Bib file(s) not found in search path:", @not_found );
+ if ($force_mode && ! $incomplete) {
warn "$My_name: Failed to find one or more bibliography files in search path.\n";
warn "====BUT force_mode is on, so I will continue. There may be problems ===\n";
}
- return 3;
+ $$Pstatus = 3;
}
- return 1;
+ $$Pstatus += 100 * $incomplete;
} #END parse_bcf
+#************************************************************
+sub incomplete_bcf {
+ # Do simple check of bcf file for completeness.
+ # Usage: incomplete_bcf( $bcf_file )
+ # Reason for this subroutine: If a run of *latex exits prematurely
+ # because of an error, any bcf file generated would normally be
+ # incomplete. It is useful to test for this before running biber,
+ # especially as part of the end-of-run analysis for *latex, to do
+ # appropriate clean up in an error situation.
+ # Perhaps it would be ideal to check for other kinds of malformed bcf
+ # file, but the incomplete run from error termination of *latex is
+ # likely to be the most common case.
+ # Return 1 if bcf file exists but does NOT have the expected final line.
+ # Otherwise return 0.
+
+ my $bcf_file = $_[0];
+ my $last_line = '';
+
+ open(my $bcf_fh, $bcf_file)
+ || do {
+ warn "$My_name: Couldn't find bcf file '$bcf_file'\n";
+ return 0;
+ };
+ while ( <$bcf_fh> ) {
+ if (eof($bcf_fh)) { $last_line = $_; }
+ }
+ close $bcf_fh;
+ if ( $last_line =~ /^\s*<\/bcf:controlfile>/ ) { return 0; }
+ warn "$My_name: Incomplete (and hence corrupt) bcf file '$bcf_file'\n";
+ return 1;
+} #END incomplete_bcf
+
+
#************************************************************
#************************************************************
#************************************************************
@@ -7416,7 +7839,11 @@
# Set its dependents etc, using information from log, aux, and fls files.
# Use fls file only if $recorder is set, and the fls file was generated
# on this run.
- # Return:
+ # Return: An array: ( Whether there are missing directories,
+ # reference to array of missing directories,
+ # whether there are bad warnings
+ # )
+ # (Missing directories are those for aux files in aux_dir.)
# N.B. A complication which we try and handle in determining
# dependent files is that there may be aliasing of file names,
@@ -7756,7 +8183,7 @@
$failure = 0;
}
$created_rules{$ind_file} = $from_rule;
- }
+ } # end IDX_FILE
local %processed_aux_files = ();
BBL_FILE:
@@ -7763,9 +8190,6 @@
foreach my $bbl_file ( uniqs( @bbl_files ) ) {
my ($bbl_base, $bbl_path, $bbl_ext) = fileparseA( $bbl_file );
$bbl_base = $bbl_path.$bbl_base;
- my @new_bib_files = ();
- my @new_aux_files = ();
- my @new_bst_files = ();
my $bcf_file = "$bbl_base.bcf";
my $bib_program = 'bibtex';
if ( test_gen_file( $bcf_file ) ) {
@@ -7772,66 +8196,104 @@
$bib_program = 'biber';
}
my $from_rule = "$bib_program $bbl_base";
- print "======= Dealing with '$from_rule'\n" if ($diagnostics);
+ $created_rules{$bbl_file} = $from_rule;
+ print " ===Source file '$bbl_file' for '$rule'\n"
+ if ($diagnostics);
+ rdb_ensure_file( $rule, $bbl_file, $from_rule );
+ if ( ! -e $bbl_file ) {
+ # Failure was non-existence of makable file
+ # Leave failure issue to other rules.
+ $failure = 0;
+ }
+
# Don't change to use activation and deactivation here, rather than
# creation and removal of rules. This is because rules are to be
# created on the fly here with details corresponding to current state
# of .tex source file(s). So activating a previously inactive rule,
- # which is out-of-date, may cause trouble.
+ # which is out-of-date, may cause trouble. ????????????? I just use previous rule, if it exists???
if ($bib_program eq 'biber') {
# Remove OPPOSITE kind of bbl generation:
rdb_remove_rule( "bibtex $bbl_base" );
-
- parse_bcf( $bcf_file, \@new_bib_files );
- }
+ # Get information from .bcf file:
+ my $bcf_status = 0;
+ my %bib_files = ();
+ my @found = ();
+ my @not_found = ();
+ my @remote = ();
+ parse_bcf( $bcf_file, \$bcf_status, \%bib_files,
+ \@found, \@not_found, \@remote );
+ my @new_sources = (@found, @not_found);
+ push @new_sources, $bcf_file;
+ if ( ! rdb_rule_exists( $from_rule ) ){
+ print " ===Creating rule '$from_rule'\n" if ($diagnostics);
+ rdb_create_rule( $from_rule, 'external', $biber, '', 1,
+ $bcf_file, $bbl_file, $bbl_base,
+ 1, 0, 0, 1, [ "$bbl_base.blg" ] );
+ # Since the rule is new, populate it with the best information
+ # that we have;
+ rdb_ensure_file_multi( $from_rule, @new_sources );
+ }
+ # Cache the information about source files from .bcf file, for use
+ # when biber terminates earlier:
+ rdb_set_extra( $from_rule, 'bcf_datasources', [@new_sources] );
+ if ($bcf_status >= 100 ) {
+ my $save_bcf = "$bcf_file$save_error_suffix";
+ my $save_bbl = "$bbl_file$save_error_suffix";
+ warn "$My_name: ========== Incomplete bcf_file '$bcf_file'.\n",
+ " I'll rename the file to '$save_bcf'.\n";
+ rename $bcf_file, $save_bcf;
+ if ($bibtex_use) {
+ warn " I'll rename the bbl file to '$save_bbl',\n",
+ " in case the incomplete bcf file was a result of error in\n",
+ " '$rule' caused by an error in the bbl file.\n";
+ rename $bbl_file, $save_bbl;
+ }
+ }
+ if ( ($bibtex_use == 1) || ($bibtex_use == 1.5) ) {
+ # Conditional use of biber => we'll make decisions on
+ # whether to run biber according to whether all bib files
+ # exist. That's on the basis of the source list of the
+ # biber rule. So if the latest information from .bcf file
+ # is that a previously listed but non-existent bib file is
+ # not in the list from the .bcf file, then we remove it
+ # from the source list of biber.
+ # AND I must add any files listed in .bcf that are
+ # non-existent.
+ my @bib_to_remove = ();
+ foreach (rdb_get_source( $from_rule ) ) {
+ if ( ( /\.bib$/ ) && ( ! -e $_ ) && ( ! exists $bib_files{$_} ) ) {
+ push @bib_to_remove, $_;
+ }
+ }
+ show_array( "Bib files to remove from source list of '$from_rule'",
+ @bib_to_remove
+ ) if $diagnostics;
+ rdb_remove_files( $from_rule, @bib_to_remove );
+ show_array( "Bib files to add to source list of '$from_rule'",
+ @not_found
+ ) if $diagnostics;
+ rdb_ensure_file_multi( $from_rule, @not_found );
+ }
+ } # end biber setup
else {
+ # Using bibtex
# Remove OPPOSITE kind of bbl generation:
rdb_remove_rule( "biber $bbl_base" );
-
- parse_aux( "$bbl_base.aux", \@new_bib_files, \@new_aux_files, \@new_bst_files );
- }
- if ( ! rdb_rule_exists( $from_rule ) ){
- print " ===Creating rule '$from_rule'\n" if ($diagnostics);
- if ( $bib_program eq 'biber' ) {
- rdb_create_rule( $from_rule, 'external', $biber, '', 1,
- $bcf_file, $bbl_file, $bbl_base, 1, 0, 0, 1, [ "$bbl_base.blg" ] );
- }
- else {
+ if ( ! rdb_rule_exists( $from_rule ) ){
rdb_create_rule( $from_rule, 'external', $bibtex, 'run_bibtex', 1,
- "$bbl_base.aux", $bbl_file, $bbl_base, 1, 0, 0, 1, [ "$bbl_base.blg" ] );
+ "$bbl_base.aux", $bbl_file, $bbl_base,
+ 1, 0, 0, 1, [ "$bbl_base.blg" ] );
}
- }
- $created_rules{$bbl_file} = $from_rule;
- local %old_sources = ();
- rdb_one_rule( $from_rule, sub { %old_sources = %$PHsource; } );
- my @new_sources = ( @new_bib_files, @new_aux_files, @new_bst_files );
- if ( $bib_program eq 'biber' ) {
- push @new_sources, $bcf_file;
- }
- foreach my $source ( @new_sources ) {
- print " ===Source file '$source' for '$from_rule'\n"
- if ($diagnostics);
- rdb_ensure_file( $from_rule, $source );
- delete $old_sources{$source};
- }
- foreach my $source ( @new_aux_files ) {
- $processed_aux_files{$source} = 1;
- }
- if ($diagnostics) {
- foreach ( keys %old_sources ) {
- print "Removing no-longer-needed dependent '$_' from rule '$from_rule'\n";
- }
- }
- rdb_remove_files( $from_rule, keys %old_sources );
- print " ===Source file '$bbl_file' for '$rule'\n"
- if ($diagnostics);
- rdb_ensure_file( $rule, $bbl_file, $from_rule );
- if ( ! -e $bbl_file ) {
- # Failure was non-existence of makable file
- # Leave failure issue to other rules.
- $failure = 0;
- }
- }
+ my @new_bib_files = ();
+ my @new_aux_files = ();
+ my @new_bst_files = ();
+ parse_aux( "$bbl_base.aux",
+ \@new_bib_files, \@new_aux_files, \@new_bst_files );
+ foreach ( @new_aux_files ) { $processed_aux_files{$_} = 1; }
+ rdb_set_source( $from_rule,
+ @new_bib_files, @new_aux_files, @new_bst_files );
+ } # end bibtex set upt
+ } # end BBL_FILE
if ( ($#aux_hooks > -1) && ! exists $processed_aux_files{$aux_main} ) {
my @new_bib_files = ();
@@ -7951,7 +8413,8 @@
rdb_remove_files( $rule, @files_not_needed );
return ($missing_dirs, [@missing_subdirs],
- ( $log_info{bad_warning} ? 1 : 0 ) );
+ ( $log_info{bad_warning} ? 1 : 0 ),
+ );
} # END rdb_set_latex_deps
@@ -8372,6 +8835,7 @@
my @dest_exts = ();
if ($pdf_mode) {push @dest_exts, '.pdf';}
if ($dvi_mode) {push @dest_exts, '.dvi';}
+ if ($hnt_mode) {push @dest_exts, '.hnt';}
if ($postscript_mode) {push @dest_exts, '.ps';}
my $deps_space = ' ';
@@ -8760,6 +9224,7 @@
print "=========SWITCH OF OUTPUT WAS DONE.\n";
next PASS;
}
+
if ( ($runs > 0) && ! $too_many_passes ) {
$retry_msg = 0;
if ( $force_mode || (! $failure) ) {
@@ -8894,6 +9359,33 @@
else { print "$My_name: Nothing to do for '$texfile_name'.\n"; }
# Diagnostics
+ my @missing_bib = ();
+ my @bibx_vetoed = ();
+ rdb_for_some( [rdb_accessible()],
+ sub{ if ( $rule =~ /^(biber|bibtex)/ ) {
+ my $veto = $$PHextra{bibx_vetoed};
+ if ( $veto ) {
+ push @bibx_vetoed, $rule;
+ if ( (ref($veto) eq 'ARRAY') && (@$veto) ) { push @missing_bib, @$veto; }
+ }
+ }
+ }
+ );
+ if (@bibx_vetoed && ! $silent) {
+ show_array(
+ "\n$My_name: The following rules were vetoed from being run, because of the\n".
+ "setting for the non-use/condititional use of bibtex/biber:",
+ sort( @bibx_vetoed )
+ );
+ if ($bibtex_use == 0) { print "Reason: I am configured not to use bibtex/biber\n"; }
+ elsif (@missing_bib) {
+ show_array(
+ "Reason: I am configured only to use bibtex/biber if all .bib files exist,\n".
+ "but the following didn't:",
+ uniqs( @missing_bib )
+ );
+ }
+ }
if ($#primary_warning_summary > -1) {
# N.B. $mult_defined, $bad_reference, $bad_character, $bad_citation also available here.
show_array( "$My_name: Summary of warnings from last run of *latex:",
@@ -8900,10 +9392,10 @@
@primary_warning_summary );
}
if ( ($#warning_list >= 0) && !$silence_logfile_warnings ) {
- warn "$My_name: ====List of undefined refs and citations:\n";
+ warn "$My_name: ====Undefined refs and citations with line #s in .tex file:\n";
for (my $i = 0; $i <= $#warning_list; $i++) {
if ($i >= $max_logfile_warnings ) {
- warn " And ", $#warning_list + 1 - $i, " more --- see log file.\n";
+ warn " And ", $#warning_list + 1 - $i, " more --- see log file '$log_name'\n";
last;
}
warn " $warning_list[$i]\n";
@@ -9006,33 +9498,19 @@
# define $pass{$rule} elsewhere, do it here:
if ( ! defined $pass{$rule} ) {$pass{$rule} = 0; }
- # Special fix up for bibtex:
- my $bibtex_not_run = -1; # Flags status as to whether this is a
- # bibtex rule and if it is, whether out-of-date condition is to
- # be ignored.
- # -1 => not a bibtex rule
- # 0 => no special treatment
- # 1 => don't run bibtex because of non-existent bibfiles
- # (and setting to do this test)
- # 2 => don't run bibtex because of setting
- my @missing_bib_files = ();
- if ( $rule =~ /^(bibtex|biber)/ ) {
- $bibtex_not_run = 0;
- if ($bibtex_use == 0) {
- $bibtex_not_run = 2;
+ my %changes = ();
+ if ( ! rdb_rerun_needed(\%changes, 0) ) {
+ my $veto = $$PHextra{bibx_vetoed};
+ if ($veto && ! $silent ) {
+ warn "$My_name: Veto of running of '$rule' (\$bibtex_use=$bibtex_use)\n";
}
- elsif ( ($bibtex_use == 1) || ($bibtex_use == 1.5) ) {
- # Conditional run of bibtex (or biber) depending on existence of .bib file.
- foreach ( keys %$PHsource ) {
- if ( ( /\.bib$/ ) && (! -e $_) ) {
- push @missing_bib_files, $_;
- $bibtex_not_run = 1;
- }
- }
- }
+ return;
}
- if ( ! rdb_rerun_needed(\%changes, 0) ) { return; }
+ if (!$silent) {
+ print "$My_name: applying rule '$rule'...\n";
+ &rdb_diagnose_changes2( \%changes, "Rule '$rule': ", 0 );
+ }
# Set this in case of early exit:
# ???!!! Check I am setting $missing_dvi_pdf correctly.
@@ -9039,15 +9517,10 @@
if ( $$Pdest && (! -e $$Pdest) && ( $$Pcmd_type eq 'primary' ) ) {
$missing_dvi_pdf = $$Pdest;
}
-
- if (!$silent) {
- print "$My_name: applying rule '$rule'...\n";
- &rdb_diagnose_changes2( \%changes, "Rule '$rule': ", 0 );
- }
-
# We are applying the rule, so its source file state for when it was
- # last made is as of now. This is do in the subroutines that do the
- # actual run, to allow for possible calls to them from other places.
+ # last made should be as of now. This is done in the subroutines that
+ # do the actual run, to allow for possible calls to them from other
+ # places. (Actually only rdb_run1, now.)
# The actual run
my $return = 0; # Return code from called routine
@@ -9069,21 +9542,10 @@
$runs_total++;
$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:",
- @missing_bib_files);
- }
- elsif ($bibtex_not_run == 2 ) {
- warn "$My_name: I AM CONFIGURED/INVOKED NOT TO RUN '$rule'\n";
- }
- $return = &rdb_dummy_run0;
- }
- else {
- warn_running( "Run number $pass{$rule} of rule '$rule'" );
- $return = &rdb_run1;
- }
+ warn_running( "Run number $pass{$rule} of rule '$rule'" );
+ $return = &rdb_run1;
+
if ($$Pchanged) {
$newrule_nofile = 1;
$return = 0;
@@ -9090,10 +9552,10 @@
}
elsif ( $$Pdest && ( !-e $$Pdest ) && (! $failure) ){
# If there is a destination to make, but for some reason
- # it did not get made, and no other error was reported,
- # then a priori there appears to be an error condition:
- # the run failed. But there are some important cases in
- # which this is a wrong diagnosis.
+ # it did not get made, and an error condition wasn't set already
+ # in $failure, then a priori there appears to be an error
+ # condition, i.e., the run failed. But there are some important
+ # cases in which this is a wrong diagnosis.
if ( ( $$Pcmd_type eq 'cusdep') && $$Psource && (! -e $$Psource) ) {
# However, if the rule is a custom dependency, this is not by
# itself an error, if also the source file does not exist. In
@@ -9117,19 +9579,12 @@
# Missing output file was reported to be NOT an error
$$Pout_of_date = 0;
}
- elsif ( ($bibtex_use <= 1.5) && ($bibtex_not_run > 0) ) {
- # Lack of destination file is not to be treated as an error
- # for a bibtex rule when latexmk is configured not to treat
- # this as an error, and the lack of a destination file is the
- # only error.
- $$Pout_of_date = 0;
- }
else {
$failure = 1;
}
}
if ( ($return != 0) && ($return != -2) ) {
- $failure = 1;
+ $failure = 1;
$$Plast_result = 2;
if ( !$$Plast_message ) {
$$Plast_message = "Run of rule '$rule' gave a non-zero error code";
@@ -9149,6 +9604,11 @@
# Otherwise: 0 on other kind of success,
# -1 on error,
# -2 when missing dest_file is to be ignored
+ # -3 for situation like biber with malformed bcf file:
+ # missing dest_file that can't be made without
+ # change of source file
+ # error is to be reported
+ # corrupt source file has been deleted/renamed.
# Defaults for summary of results of run.
$$Prun_time = time();
@@ -9233,105 +9693,10 @@
run_hooks( 'after_xlatex_analysis' );
}
elsif ( $rule =~ /^biber/ ) {
- my @biber_datasource = ( );
- my $retcode = check_biber_log( $$Pbase, \@biber_datasource );
- foreach my $source ( @biber_datasource ) {
-# if ( $source =~ /\"/ ) {next; }
- print " ===Source file '$source' for '$rule'\n"
- if ($diagnostics);
- rdb_ensure_file( $rule, $source );
- }
- if ($retcode == 5) {
- # Special treatment if sole missing file is bib file
- # I don't want to treat that as an error
- $return = 0;
- $$Plast_result = 200;
- $$Plast_message = "Could not find bib file for '$$Pbase'";
- push @warnings, "Bib file not found for '$$Pbase'";
- }
- elsif ($retcode == 6) {
- # Missing control file. Need to remake it (if possible)
- # Don't treat missing bbl file as error.
- print "$My_name: bibtex control file missing. Since that can\n",
- " be recreated, I'll try to do so.\n";
- $return = -2;
- rdb_for_some( [keys %current_primaries], sub{ $$Pout_of_date = 1; } );
- }
- elsif ($retcode == 4) {
- $$Plast_result = 2;
- $$Plast_message = "Could not find all biber source files for '$$Pbase'";
- push @warnings, "Not all biber source files found for '$$Pbase'";
- }
- elsif ($retcode == 3) {
- $$Plast_result = 2;
- $$Plast_message = "Could not open biber log file for '$$Pbase'";
- push @warnings, $$Plast_message;
- }
- elsif ($retcode == 2) {
- $$Plast_message = "Biber errors: See file '$$Pbase.blg'";
- push @warnings, $$Plast_message;
- }
- elsif ($retcode == 1) {
- push @warnings, "Biber warnings for '$$Pbase'";
- }
- elsif ($retcode == 10) {
- push @warnings, "Biber found no citations for '$$Pbase'";
- # Biber doesn't generate a bbl file in this situation.
- $return = -2;
- }
- elsif ($retcode == 11) {
- push @warnings, "Biber: malformed bcf file for '$$Pbase'. IGNORE";
- if (!$silent) {
- print "$My_name: biber found malformed bcf file for '$$Pbase'.\n",
- " I'll ignore error, and delete any bbl file.\n";
- }
- # Malformed bcf file is a downstream consequence, normally,
- # of an error in *latex run. So this is not an error
- # condition in biber itself.
- # Current version of biber deletes bbl file.
- # Older versions (pre-2016) made an incorrect bbl file, which
- # tended to cause latex errors, and give a self-perpetuating error.
- # To be safe, ensure the bbl file doesn't exist.
- unlink $$Pdest;
- # The missing bbl file is now not an error:
- $return = -2;
- }
+ after_biber( \$return );
}
elsif ( $rule =~ /^bibtex/ ) {
- my $retcode = check_bibtex_log($$Pbase);
- if ( ! -e $$Psource ) {
- $retcode = 10;
- if (!$silent) {
- print "Source '$$Psource' for '$rule' doesn't exist,\n",
- "so I'll force *latex to run to try and make it.\n";
- }
- rdb_for_some( [keys %current_primaries], sub{ $$Pout_of_date = 1; } );
- }
- if ($retcode == 3) {
- $$Plast_result = 2;
- $$Plast_message = "Could not open bibtex log file for '$$Pbase'";
- push @warnings, $$Plast_message;
- }
- elsif ($retcode == 2) {
- $$Plast_message = "Bibtex errors: See file '$$Pbase.blg'";
- $failure = 1;
- push @warnings, $$Plast_message;
- }
- elsif ($retcode == 1) {
- push @warnings, "Bibtex warnings for '$$Pbase'";
- }
- elsif ($retcode == 10) {
- push @warnings, "Bibtex found no citations for '$$Pbase',\n",
- " or bibtex found a missing aux file\n";
- if (! -e $$Pdest ) {
- print "$My_name: Bibtex did not produce '$$Pdest'. But that\n",
- " was because of missing files, so I will continue.\n";
- $return = -2;
- }
- else {
- $return = 0;
- }
- }
+ after_bibtex( \$return );
}
else {
# No special analysis for other rules
@@ -9366,28 +9731,6 @@
#-----------------
-sub rdb_dummy_run0 {
- # Assumes contexts for: rule.
- # Update rule state as if the rule ran successfully,
- # but don't run the rule.
- # Returns 0 (success code)
-
- # Source file data, by definition, correspond to the file state just before
- # the latest run, and the run_time to the time just before the run:
- &rdb_update_files;
- $$Prun_time = time();
- $$Pchanged = 0; # No special changes in files
- $$Plast_result = 0;
- $$Plast_result_info = 'CURR';
- $$Plast_message = '';
-
- $$Pout_of_date = $$Pout_of_date_user = 0;
-
- return 0;
-} # END rdb_dummy_run0
-
-#-----------------
-
sub Run_subst {
# Call: Run_subst( cmd, msg, options, source, dest, base )
# Runs command with substitutions.
@@ -9465,6 +9808,9 @@
return $return;
} #END Run_subst
+
+#************************************************************
+
sub analyze_latex_run {
# Call: analyze_latex_run(old_ret_code)
# Analyze results of run of *latex (or whatever was run instead) from
@@ -9493,7 +9839,7 @@
my ($missing_dirs, $PA_missing_subdirs, $bad_warnings) = &rdb_set_latex_deps;
if ($bad_warning_is_error && $bad_warnings) {
warn "$My_name: Serious warnings in .log configured to be errors\n";
- $return ||= $bad_warnings;1
+ $return ||= $bad_warnings;
}
# For each file of the kind made by epstopdf.sty during a run,
@@ -9623,7 +9969,7 @@
);
return $user_changes;
-}
+} #END rdb_user_changes
#************************************************************
@@ -9648,6 +9994,9 @@
local our $PHchanges = shift;
local our $outside_make_loop = shift;
+ my $bibx_rule = ( $rule =~ /^(biber|bibtex)/ );
+
+
# File level routine reports its results in %$PHchanges: maps kind of
# change to ref to array of files with that kind of change.
%$PHchanges = ();
@@ -9766,6 +10115,11 @@
elsif ( $$Pcmd_type eq 'delegated' ) {
# Delegate to destination rule
}
+ elsif ( $$PHextra{bibx_vetoed} ) {
+ # Previous attempt at a run of biber/bibtex was vetoed
+ # So it's pointless to rerun it unless there was some
+ # other change, which will have been detected.
+ }
else {
$rerun_needed = 1;
push @{$$PHchanges{no_dest}}, $rule;
@@ -9779,6 +10133,43 @@
}
}
$$Pno_history = 0; # See comments in definition of %rule_db.
+ if ( $$Psource && (! -e $$Psource) ) {
+# print "================In '$rule', no source '$$Psource'\n";
+ }
+
+ if ( $bibx_rule ) {
+ # Check whether run of biber/bibtex rule is to be vetoed.
+ # Default to no veto:
+ $$PHextra{bibx_vetoed} = 0;
+ if ($rerun_needed) {
+ if ($bibtex_use == 0) {
+ # Do not use biber/bibtex at all
+ $rerun_needed = 0;
+ $$PHextra{bibx_vetoed} = 1;
+ }
+ elsif ($bibtex_use < 1.9) {
+ # Conditional bibtex/biber use, if all .bib files exist
+ my @missing_bib_files = ();
+ foreach ( keys %$PHsource ) {
+ if ( ( /\.bib$/ ) && (! -e $_) ) {
+ push @missing_bib_files, $_;
+ }
+ }
+ if ( @missing_bib_files ) {
+ $rerun_needed = 0;
+ $$PHextra{bibx_vetoed} = [ sort @missing_bib_files ];
+ }
+ }
+ if ($$PHextra{bibx_vetoed}) {
+ # Avoid propagating error state from previous invocations,
+ # since things might have changed if I did a run instead of
+ # vetoing it. A saved non-zero error state tends to stop
+ # certain things from being run.
+ $$Plast_result = 0;
+ }
+
+ }
+ }
if ($rerun_needed) {
push @{$$PHchanges{rules_to_apply}}, $rule;
}
@@ -10122,9 +10513,13 @@
#===== Accesses rule part of database structure =======
local ( $rule, $rule_act1, $file_act, $rule_act2 ) = @_;
- if ( (! $rule) || ! rdb_rule_exists($rule) ) { return; }
+ if ( (! $rule) || ! rdb_rule_exists($rule) ) {
+ die_trace( "$My_name: BUG in call to rdb_one_rule: non-existent rule '$rule'" );
+ }
- local ( $PArule_data, $PHsource, $PHdest, $PHrewritten_before_read, $PHsource_rules ) = @{$rule_db{$rule}};
+ local ( $PArule_data, $PHsource, $PHdest, $PHrewritten_before_read,
+ $PHsource_rules, $PHextra )
+ = @{$rule_db{$rule}};
local ($Pcmd_type, $Pext_cmd, $PAint_cmd, $Pno_history,
$Psource, $Pdest, $Pbase,
$Pout_of_date, $Pout_of_date_user, $Prun_time, $Pcheck_time,
@@ -10286,6 +10681,7 @@
{},
{},
{},
+ {},
{}
];
foreach my $file ($source, @$PAextra_source ) {
@@ -10368,36 +10764,80 @@
if ( ! defined $new_file ) {
die_trace( "$My_name: BUG in call to rdb_ensure_file: undefined file for '$rule'" );
}
- if ( $new_file =~ /\"/ ) {
- warn "$My_name: in rdb_ensure_file for rule '$rule', there is a double quote in\n",
- " the filename: '$new_file'.\n",
- " I cannot handle this, will ignore this file.\n";
- return;
- }
if ( ! defined $set_not_exists ) { $set_not_exists = 0; }
- rdb_one_rule( $rule,
- sub{
- if (! exists ${$PHsource}{$new_file} ) {
- if ( $set_not_exists ) {
- ${$PHsource}{$new_file} = [@nofile, '', 0];
- }
- else {
- ${$PHsource}{$new_file}
- = [fdb_get($new_file, $$Prun_time), '', 0];
- }
- }
+ rdb_one_rule(
+ $rule, sub{ if ($set_not_exists) { rdb_ensure_new_files_here($new_file); }
+ else { rdb_ensure_files_here($new_file); }
}
);
- if (defined $new_from_rule ) {
- $from_rules{$new_file} = $new_from_rule;
- }
+ if (defined $new_from_rule ) { $from_rules{$new_file} = $new_from_rule; }
} #END rdb_ensure_file
#************************************************************
+sub rdb_ensure_file_multi {
+ # rdb_ensure_file( rule, file ... )
+ # Ensures the source files exist in the given rule.
+ # Like rdb_ensure_file, but without the possible setting of a from rule
+ # or of the initialization to non-existent file
+ #============ NOTE: rule and file data set here ===============================
+ use strict;
+ my $rule = shift;
+ my @files = @_;
+ rdb_one_rule( $rule, sub { rdb_ensure_files_here( @files ); } );
+} #END rdb_ensure_file_multi
+
+#************************************************************
+
+sub rdb_ensure_files_here {
+ # rdb_ensure_files_here( file, ...)
+ # Assumes rule context
+ # Ensures the given files are in the source file list.
+ # For added files, initialize state to current of file,
+ # as is appropriate if the file was read in latest run of rule
+ use strict;
+ our ($rule, $My_name, $PHsource, $Prun_time);
+ foreach (@_) {
+ if ( /\"/ ) {
+ warn "$My_name: in rdb_ensure_files_here for rule '$rule', there\n",
+ " is a double quote in the filename: '$_'.\n",
+ " I cannot handle this, will ignore this file.\n";
+ next;
+ }
+ if (! exists ${$PHsource}{$_} ) {
+ ${$PHsource}{$_} = [fdb_get($_, $$Prun_time), '', 0];
+ }
+ }
+} #DN rdb_ensure_files_here
+
+#************************************************************
+
+sub rdb_ensure_new_files_here {
+ # rdb_ensure_new_files_here( file, ...)
+ # Assumes rule context
+ # Ensures the given files are in the source file list.
+ # For added files, initialize state to non-existent,
+ # as is appropriate if the file is new to the rule
+ use strict;
+ our ($rule, $My_name, $PHsource, @nofile);
+ foreach (@_) {
+ if ( /\"/ ) {
+ warn "$My_name: in rdb_ensure_new_files_here for rule '$rule', there\n",
+ " is a double quote in the filename: '$_'.\n",
+ " I cannot handle this, will ignore this file.\n";
+ next;
+ }
+ if (! exists ${$PHsource}{$_} ) {
+ ${$PHsource}{$_} = [@nofile, '', 0];
+ }
+ }
+}
+
+#************************************************************
+
sub rdb_remove_files {
# rdb_remove_file( rule, file, ... )
- # Removes file(s) for the rule.
+ # Removes file(s) for the rule.
my $rule = shift;
if (!$rule) { return; }
local @files = @_;
@@ -10408,37 +10848,86 @@
#************************************************************
-sub rdb_list_source {
- # rdb_list_source( rule )
+sub rdb_get_extra {
+ # rdb_get_extra( rule, key )
+ # Returns value pointed to by key in the rule's extra hash.
+ # Mostly for use when not in context of the given rule
+ # or from user code.
+ use strict;
+ our $PHextra;
+ my ($rule, $key) = @_;
+ my $info = undef;
+ rdb_one_rule( $rule, sub{ $info = $$PHextra{$key}; } );
+ return $info;
+} #END rdb_get_extra
+
+#************************************************************
+
+sub rdb_set_extra {
+ # rdb_set_extra( rule, key, value )
+ # Set value pointed to by key in the rule's extra hash.
+ # Mostly for use when not in context of the given rule,
+ # or from user code.
+ use strict;
+ our $PHextra;
+ my ($rule, $key, $value) = @_;
+ rdb_one_rule( $rule, sub{ $$PHextra{$key} = $value; } );
+} #END rdb_set_extra
+
+#************************************************************
+
+sub rdb_get_source {
+ # rdb_get_source( rule )
# Return array of source files for rule.
- my $rule = shift;
+ use strict;
+ our $PHsource;
+ my $rule = $_[0];
my @files = ();
- rdb_one_rule( $rule,
- sub{ @files = keys %$PHsource; }
- );
+ rdb_one_rule( $rule, sub{ @files = keys %$PHsource; } );
return @files;
-} #END rdb_list_source
+} #END rdb_get_source
#************************************************************
+sub rdb_show_source {
+ # rdb_show_source( rule[, msg] )
+ # Display sorted source files for rule, preceeded by optional message
+ use strict;
+ my ($rule, $msg) = @_;
+ print( $msg ) if $msg;
+ show_array( "Source files for '$rule'", sort( rdb_get_source($rule) ));
+} #END rdb_show_source
+
+#************************************************************
+
sub rdb_set_source {
# rdb_set_source( rule, file, ... )
+ # Set the source file list for rule to given files
+ use strict;
my $rule = shift;
- if (!$rule) { return; }
- my %files = ();
- foreach (@_) {
-# if ( /\"/ ) {next; }
- rdb_ensure_file( $rule, $_ );
- $files{$_} = 1;
- }
- foreach ( rdb_list_source($rule) ) {
- if ( ! exists $files{$_} ) { rdb_remove_files( $rule, $_ ); }
- }
- return;
-} #END rdb_list_source
+ my @files = @_;
+ rdb_one_rule( $rule, sub { rdb_set_source_here( @files ); } );
+} #END rdb_set_source
#************************************************************
+sub rdb_set_source_here {
+ # rdb_set_source_here( file, ... )
+ # Set the source file list for current rule to given files
+ # Rule context assumed.
+ use strict;
+ our ( $rule, $PHsource, $Psource );
+ my @files = @_;
+ push( @files, $$Psource)
+ if ($$Psource);
+ my %deletions = %$PHsource;
+ foreach (@files) { delete $deletions{$_}; }
+ rdb_remove_files( $rule, keys %deletions );
+ rdb_ensure_files_here( @files );
+} #END rdb_set_source
+
+#************************************************************
+
sub rdb_rule_exists {
# Call rdb_rule_exists($rule): Returns whether rule exists.
my $rule = shift;
@@ -10464,7 +10953,12 @@
sub rdb_update_gen_files {
# Assumes rule context. Update source files of rule to current state,
# but only for source files that are generated by this or another rule.
- rdb_do_files(
+ if ($$PHextra{bibx_vetoed} ) {
+ # I will NOT update generated source files for vetoed rule, so that
+ # source file state for the rule corresponds to last actual run of rule
+ return;
+ }
+ rdb_do_files(
sub{ if ( exists $from_rules{$file} ) { &rdb_update1; } }
);
} #END rdb_update_gen_files
@@ -10749,7 +11243,7 @@
my $return_mtime = 0;
foreach my $include (@_)
{
- my $include_mtime = &get_mtime($include);
+ my $include_mtime = get_mtime($include);
# The file $include may not exist. If so ignore it, otherwise
# we'll get an undefined variable warning.
if ( ($include_mtime) && ($include_mtime > $return_mtime) )
@@ -10787,12 +11281,12 @@
sub processing_time {
# Return time used.
# Either total processing time of process and child processes as reported
- # in pieces by times(), or HiRes time since Epoch depending on setting of
+ # in pieces by times(), or time since Epoch depending on setting of
# $times_are_clock.
# That variable is to be set on OSs (MSWin32) where times() does not
# include time for subprocesses.
if ($times_are_clock) {
- return Time::HiRes::time();
+ return time();
}
my ($user, $system, $cuser, $csystem) = times();
return $user + $system + $cuser + $csystem;
@@ -10880,7 +11374,7 @@
# files), which are few in number. Only likely conceivable case for
# having many files is with a big document, for which *latex running
# time is large, so almost certainly that dwarfs run time for several
- # runs of kpsewhich.
+ # runs of kpsewhich.
my ($PHfiles, $format, $ext, $PAfiles, $PAnot_found) = @_;
@$PAfiles = @$PAnot_found = ();
@@ -10900,7 +11394,7 @@
if ( ! /\..*$/ ) { $_ .= ".$ext"; }
push @$PAfiles, $_;
}
-
+
return 1 + $#{$PAnot_found};
} #END find_files
@@ -11001,7 +11495,7 @@
}
}
$cmd =~ s/%[RBTDO]//g;
- $cmd =~ s/%S/@_/g;
+ $cmd =~ s/%S/@args/g;
my @found = ();
local $fh;
if ( $kpsewhich_show || $diagnostics ) {
Modified: trunk/Master/texmf-dist/doc/man/man1/latexmk.1
===================================================================
--- trunk/Master/texmf-dist/doc/man/man1/latexmk.1 2023-12-26 21:02:15 UTC (rev 69220)
+++ trunk/Master/texmf-dist/doc/man/man1/latexmk.1 2023-12-26 21:04:28 UTC (rev 69221)
@@ -1,4 +1,4 @@
-.TH LATEXMK 1 "6 November 2023" ""
+.TH LATEXMK 1 "24 December 2023" ""
.SH NAME
latexmk \- generate LaTeX document
.SH SYNOPSIS
@@ -234,9 +234,11 @@
variable to 1 in a configuration file.
\fBNote\fR that when \fBbiber\fR is used, and a bib file doesn't exist, this
-option does not currently prevent \fIbiber\fR from being run. See the
+option does not prevent \fIbiber\fR from being run, with the bbl file then
+being incorrect.
+See the
documentation on \fI$bibtex_use\fR for more details. However, a bbl file
-is treated as precious.
+is treated as precious in a clean up operation.
.TP
.B -bibtex-cond1
@@ -251,8 +253,11 @@
variable to 1.5 in a configuration file.
\fBNote\fR that when \fBbiber\fR is used, and a bib file doesn't exist, this
-option does not currently prevent \fIbiber\fR from being run. See the
-documentation on \fI$bibtex_use\fR for more details.
+option does not prevent \fIbiber\fR from being run, with the bbl file then
+being incorrect.
+See the
+documentation on \fI$bibtex_use\fR for more details. However, a bbl file
+is treated as precious in a clean up operation.
.TP
.B -bibtexfudge\fR or\fB -bibfudge
@@ -475,6 +480,12 @@
Do not report the settings for aux and out directories. (Default)
.TP
+.B -dir-report-only
+After all initialization is complete, give the settings for the aux and out
+directories, and then halt. This option is primarily used for debugging
+configuration issues.
+
+.TP
.B -dvi
Generate dvi version of document using latex.
@@ -607,6 +618,11 @@
Print help information.
.TP
+.B -hnt
+Generate hnt (HINT) version of document using hilatex. (And turn off dvi,
+postscript, and pdf modes.)
+
+.TP
.B -jobname=STRING
Set the basename of output files(s) to STRING, instead of the default,
which is the basename of the specified TeX file. (At present, STRING
@@ -748,6 +764,10 @@
\fI$makeindex_fudge\fR for details.
.TP
+.B $min_sleep_time [0.01]
+This is the minimum nonzero value allowed for \fI$sleep_time\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
@@ -2177,18 +2197,23 @@
.TP
.B $aux_out_dir_report [0]
-For each primary .tex file processed, list the settings for aux and output
-directories, after they have been normalized from the settings specified
-during initialization.
+If this variable is set to 1, then prior to the processing of each
+primary .tex file, list the settings for aux and output directories, after
+they have been normalized from the settings specified during
+initialization.
This report gives a reminder of where to look for generated files.
-The report has to be done per primary .tex file, because of possible
-directory changes for each file (when the \fB-cd\fR option is used). In
-the simplest cases, the directory names are the same as originally
-specified. But in general some clean up/normalization is performed; this
-helps performance and cleans up output to the screen.
+The report is done per primary .tex file, because of possible directory
+changes for each file (when the \fB-cd\fR option is used). In the simplest
+cases, the directory names are the same as originally specified. But in
+general some clean up/normalization is performed; this helps performance
+and cleans up output to the screen.
+If this variable is set to 2, then halt after reporting the settings for
+the aux and out directories, rather than continuing with processing of tex
+files. This setting is primarily used for debugging configuration issues.
+See the \fB-dir-report-only\fR option.
.TP
.B $bad_warning_is_error [0]
@@ -2313,15 +2338,25 @@
The possible values of \fI$bibtex_use\fR are:
0: never use \fIbibtex\fR or \fIbiber\fR; never delete .bbl files in a cleanup.
- 1: only use \fIbibtex\fR if the bib file(s) exist; never delete .bbl
-files in a cleanup.
- 1.5: only use \fIbibtex\fR if the bib files exist; conditionally
-delete .bbl files in a cleanup (i.e., delete them only when the bib files
-all exist).
+ 1: only use \fIbibtex\fR or \fIbiber\fR if the bib file(s) exist; never
+ delete .bbl files in a cleanup.
+ 1.5: only use \fIbibtex\fR or \fIbiber\fR if the bib files exist;
+ conditionally delete .bbl files in a cleanup (i.e., delete them only when
+ the bib files all exist).
2: run \fIbibtex\fR or \fIbiber\fR whenever it appears necessary to
update the bbl file(s), without testing for the existence of the bib
files; always delete .bbl files in a cleanup.
+\fINote\fR: When \fIbiber\fR is being used, conditional use of \fIbiber\fR
+can be problematic. From \fIlatexmk\fR's point of view the problem is that
+because of how \fIbiber\fR works, a full knowledge of its source files can
+only be obtained after running \fIbiber\fR. In contrast, for \fIbibtex\fR,
+full information on which bib files are used is obtained from the .aux
+file(s) after a run of *latex. But for \fIbiber\fR, the corresponding
+information is somewhat incomplete; this the information obtained in
+the .bcf file that is generated by the biblatex package during a run of
+*latex.
+
.TP
.B $cleanup_includes_cusdep_generated [0]
If nonzero, specifies that cleanup also deletes files that are
@@ -2586,9 +2621,9 @@
$dvilualatex = "dvilualatex --src-specials %O %S";
-To do a coordinated setting of all of \fI$dvilualatex\fR, \fI$latex\fR,
-\fI$pdflatex\fR, \fI$lualatex\fR, and \fI$xelatex\fR, see the section
-"Advanced Configuration".
+To do a coordinated setting of all of \fI$dvilualatex\fR, \fI$hilatex\fR,
+\fI$latex\fR, \fI$pdflatex\fR, \fI$lualatex\fR, and \fI$xelatex\fR, see the
+section "Advanced Configuration".
.TP
.B $dvi_mode [See below for default]
@@ -2763,6 +2798,32 @@
(See documentation on Perl regular expressions for details.)
.TP
+.B $filetime_causality_threshold [5]
+The use of this variable is as follows: At a number of places, latexmk
+needs to determine whether a particular file has been produced during a
+just-concluded run of some rule/program or is leftover from a previous
+run. (An example is the production of a .bcf file by the biblatex package
+during a run of *latex to provide bibliographic information to the biber
+program. If a .bcf file is not produced during a current run of *latex,
+but is leftover from a previous run, then latexmk has to conclude that
+the .tex document has changed so that biber is no longer to be used.)
+
+Latexmk's criterion that a file has been produced during a run is that the
+modification time of the file is more recent than the system time at the
+beginning of the run. Bascially, if the modification time is earlier than
+this, then it is a leftover from a previous run. However, a naive use of
+the criterion can, among other things, run afoul of the granularity of how
+file times are stored in some file systems, which means it is possible that
+the filesystem's reported time for a file might be a second or more earlier
+than the actual modification time, the exact difference being quite random.
+
+The variable \fI$filetime_causality_threshold\fR allows an appopriate
+sloppiness in latexmk's use of file modification time. It can be quite
+generous; it should merely be less than the time scale on which a human
+user makes changes to source files for a document (or to configuration
+files, etc).
+
+.TP
.B $fls_uses_out_dir [0]
This variable determines whether or not the .fls file should be in the
output directory instead of the natural directory, which is the aux
@@ -2831,6 +2892,7 @@
.B $go_mode [0]
If nonzero, process files regardless of timestamps, and is then
equivalent to the \fB-g\fR option.
+
.TP
.B %hash_calc_ignore_pattern
\fB!!!This variable is for experts only!!!\fR
@@ -2881,6 +2943,15 @@
delete $hash_calc_ignore_pattern{'eps'};
.TP
+.B $hilatex ["hilatex %O %S"]
+specifies the command line for the hilatex program.
+
+.TP
+.B $hnt_mode [0]
+Whether to generate a hnt version of the document by use of hilatex. Can
+be turned on by the use of the \fB-hnt\fR option.
+
+.TP
.B $jobname [""]
This specifies the jobname, i.e., the basename that is used for
@@ -2933,6 +3004,7 @@
See also the \fI at BIBINPUTS\fR variable for another way that \fIlatexmk\fR
also uses to try to locate files; it applies only in the case of .bib
files.
+
.TP
.B $kpsewhich_show [0]
Whether to show diagnostics about invocations of \fIkpsewhich\fR: the
@@ -2941,11 +3013,13 @@
on. (But in the second case, lots of other diagnostics are also
shown.) Without these diagnostics there is nothing visible in
\fIlatexmk\fR's screen output about invocations of \fIkpsewhich\fR.
+
.TP
.B $landscape_mode [0]
If nonzero, run in landscape mode, using the landscape mode previewers and
dvi to postscript converters. Equivalent to the \fB-l\fR option.
Normally not needed with current previewers.
+
.TP
.B $latex ["latex %O %S"]
Specifies the command line for
@@ -2955,9 +3029,9 @@
$latex = "latex --src-specials %O %S";
-To do a coordinated setting of all of \fI$dvilualatex\fR, \fI$latex\fR,
-\fI$pdflatex\fR, \fI$lualatex\fR, and \fI$xelatex\fR, see the section
-"Advanced Configuration".
+To do a coordinated setting of all of \fI$dvilualatex\fR, \fI$hilatex\fR,
+\fI$latex\fR, \fI$pdflatex\fR, \fI$lualatex\fR, and \fI$xelatex\fR, see the
+section "Advanced Configuration".
.TP
.B %latex_input_extensions
@@ -3041,9 +3115,9 @@
the LaTeX processing program that is to be used when the \fIlualatex\fR
program is called for (e.g., by the option \fB-lualatex\fR.
-To do a coordinated setting of all of \fI$dvilualatex\fR, \fI$latex\fR,
-\fI$pdflatex\fR, \fI$lualatex\fR, and \fI$xelatex\fR, see the section
-"Advanced Configuration".
+To do a coordinated setting of all of \fI$dvilualatex\fR, \fI$hilatex\fR,
+\fI$latex\fR, \fI$pdflatex\fR, \fI$lualatex\fR, and \fI$xelatex\fR, see the
+section "Advanced Configuration".
.TP
.B %lualatex_input_extensions
@@ -3173,9 +3247,9 @@
variables for the use of \fIlualatex\fR or \fIxelatex\fR. See
\fI$lualatex\fR and \fI$xelatex\fR.)
-To do a coordinated setting of all of \fI$dvilualatex\fR, \fI$latex\fR,
-\fI$pdflatex\fR, \fI$lualatex\fR, and \fI$xelatex\fR, see the section
-"Advanced Configuration".
+To do a coordinated setting of all of \fI$dvilualatex\fR, \fI$hilatex\fR,
+\fI$latex\fR, \fI$pdflatex\fR, \fI$lualatex\fR, and \fI$xelatex\fR, see the
+section "Advanced Configuration".
.TP
.B %pdflatex_input_extensions
@@ -3502,18 +3576,29 @@
Note that multiple occurrences for the same undefined object on the
same page and same line will be compressed to a single warning.
+
.TP
.B $silent [0]
Whether to run silently. Setting $silent to 1 has the same effect as
the \fB-quiet\fR of \fB-silent\fR options on the command line.
+
.TP
.B $sleep_time [2]
-The time to sleep (in seconds) between checking for source file
-changes when running with the \fB-pvc\fR option. This is subject to a
-minimum of one second delay, except that zero delay is also allowed.
+The time to sleep (in seconds) between checking for source-file
+changes when running with the \fB-pvc\fR option. If non-zero, it is subject to a
+minimum value give by the \fI$min_sleep_time\fR variable. But a zero value
+is also allowed.
-A value of exactly 0 gives no delay, and typically results in 100% CPU
-usage, which may not be desirable.
+A value of exactly 0 gives no delay between checks for source-file changes;
+it typically results in 100% CPU usage, which may not be desirable.
+
+In old versions of latexmk, the default value of \fI$sleep_time\fR of 2 was
+set to give a reasonable compromise between responsiveness in \rB-pvc\fR
+mode and the amount of CPU usage. On modern computers with fast multi-core
+CPUs, a smaller value, e.g., 0.1 can give good results, especially when
+working with small documents whose compilation may take well under a
+second.
+
.TP
.B $texfile_search [""]
This is an obsolete variable, replaced by the \fI at default_files\fR
@@ -3629,9 +3714,9 @@
\fIlatexmk\fR makes a .xdv file rather than a .pdf file when \fIxelatex\fR
is used.
-To do a coordinated setting of all of \fI$dvilualatex\fR, \fI$latex\fR,
-\fI$pdflatex\fR, \fI$lualatex\fR, and \fI$xelatex\fR, see the section
-"Advanced Configuration".
+To do a coordinated setting of all of \fI$dvilualatex\fR, \fI$hilatex\fR,
+\fI$latex\fR, \fI$pdflatex\fR, \fI$lualatex\fR, and \fI$xelatex\fR, see the
+section "Advanced Configuration".
.TP
.B %xelatex_input_extensions
@@ -4131,10 +4216,10 @@
.SS Coordinated Setting of Commands for *latex
-To set all of \fI$dvilualatex\fR, \fI$latex\fR, \fI$pdflatex\fR,
-\fI$lualatex\fR, and
-\fI$xelatex\fR to a common pattern, you can use one of the following
-subroutines, std_tex_cmds, alt_tex_cmds, and set_tex_cmds.
+To set all of \fI$dvilualatex\fR, \fI$hilatex\fR, \fI$latex\fR,
+\fI$pdflatex\fR, \fI$lualatex\fR, and \fI$xelatex\fR to a common pattern,
+you can use one of the following subroutines, std_tex_cmds, alt_tex_cmds,
+and set_tex_cmds.
To get the standard commands, use
@@ -4141,11 +4226,11 @@
&std_tex_cmds;
This results in \fI$latex = 'latex %O %S'\fR, and similarly for
-\fI$dvilualatex\fR, \fI$pdflatex\fR, \fI$lualatex\fR, and \fI$xelatex\fR.
-Note the ampersand in the invocation; this indicates to Perl that a
-subroutine is being called. (The use of this subroutine enables you to
-override previous redefinitions of the \fI$latex\fR, etc variables, which
-might have occurred in an earlier-read rc file.)
+\fI$dvilualatex\fR, \fI$hilatex\fR, \fI$pdflatex\fR, \fI$lualatex\fR, and
+\fI$xelatex\fR. Note the ampersand in the invocation; this indicates to
+Perl that a subroutine is being called. (The use of this subroutine
+enables you to override previous redefinitions of the \fI$latex\fR, etc
+variables, which might have occurred in an earlier-read rc file.)
To be able to use the string provided by the -pretex option (if any), you
can use
@@ -4384,7 +4469,7 @@
harvested too easily.)
.SH AUTHOR
Current version, by John Collins
-(Version 4.81).
+(Version 4.82).
Report bugs etc to his e-mail (jcc8 at psu.edu).
Released version can be obtained from CTAN:
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 2023-12-26 21:02:15 UTC (rev 69220)
+++ trunk/Master/texmf-dist/doc/support/latexmk/CHANGES 2023-12-26 21:04:28 UTC (rev 69221)
@@ -873,3 +873,21 @@
preview_continuous_mode, incorrect extra runs were sometimes made.
Other bug fixes.
+From v. 4.81 to 4.82
+ Fixed various anomalies in working with biber, especially under error conditions.
+ Fixed various anomalies with use of -bibtex- and -bibtex-cond options.
+ Fixed problem that -Werror worked only with bibtex and not biber. (This
+ is the option that causes latexmk to return a non-zero exit code to
+ flag an error when there are missing-citation messages in the .log
+ file.)
+ Added -dir-report-only option.
+ Fixed lack of quoting on command line to kpsewhich.
+ Implemented support for hilatex (-hnt option, $hnt_mode configuration
+ variable).
+ Allow sleep times of under a second. (That gives very responsive
+ performance on fast computers.)
+ Support ^^ format in .log file for non-ASCII bytes/characters.
+ Document $filetime_causality_threshold configuration variable.
+ Other documentation improvements.
+
+
Modified: trunk/Master/texmf-dist/doc/support/latexmk/INSTALL
===================================================================
--- trunk/Master/texmf-dist/doc/support/latexmk/INSTALL 2023-12-26 21:02:15 UTC (rev 69220)
+++ trunk/Master/texmf-dist/doc/support/latexmk/INSTALL 2023-12-26 21:04:28 UTC (rev 69221)
@@ -1,6 +1,6 @@
INSTALLING latexmk
==================
- (Version 4.81, 6 Nov. 2023)
+ (Version 4.82, 24 Dec. 2023)
John Collins
Physics Department
@@ -9,8 +9,8 @@
University Park PA 16802
U.S.A.
- http://www.personal.psu.edu/jcc8/
- http://www.personal.psu.edu/jcc8/latexmk/
+ https://www.cantab.net/users/johncollins/
+ https://www.cantab.net/users/johncollins/latexmk/
username jcc8 at node psu.edu
Latexmk is a "make" tool for building latex documents. It runs latex
Modified: trunk/Master/texmf-dist/doc/support/latexmk/README
===================================================================
--- trunk/Master/texmf-dist/doc/support/latexmk/README 2023-12-26 21:02:15 UTC (rev 69220)
+++ trunk/Master/texmf-dist/doc/support/latexmk/README 2023-12-26 21:04:28 UTC (rev 69221)
@@ -1,5 +1,5 @@
-Latexmk, version 4.81, 6 Nov 2023
----------------------------------
+Latexmk, version 4.82, 24 Dec 2023
+----------------------------------
Latexmk completely automates the process of generating a LaTeX
document. Essentially, it is a highly specialized cousin of the
@@ -36,7 +36,7 @@
University Park PA 16802
U.S.A.
- http://www.personal.psu.edu/jcc8/
+ https://www.cantab.net/users/johncollins/
username jcc8 at node psu.edu
The start of the script file has copyright notices and disclaimers.
@@ -56,7 +56,7 @@
b. On the CTAN tex archive --- see http://www.ctan.org/pkg/latexmk
- c. From the author's site at http://www.personal.psu.edu/jcc8/latexmk/
+ c. From the author's site at https://www.cantab.net/users/johncollins/latexmk/
This site also includes previous versions, and sometimes newer versions
under development.
Modified: trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/glossaries_latexmkrc
===================================================================
--- trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/glossaries_latexmkrc 2023-12-26 21:02:15 UTC (rev 69220)
+++ trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/glossaries_latexmkrc 2023-12-26 21:04:28 UTC (rev 69221)
@@ -3,7 +3,7 @@
# (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 item 2.
+# (http://www.ctan.org/pkg/glossary), which has some differences. See item 3.
# 1. If you use the glossaries or the glossaries-extra package, then you can use:
@@ -37,3 +37,26 @@
# return system "makeindex", @args;
# }
+# 3. 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.)
+
+ ## 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\"" );
+ #}
+
+ ## 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\"" );
+ #}
Modified: trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/glossary_latexmkrc
===================================================================
--- trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/glossary_latexmkrc 2023-12-26 21:02:15 UTC (rev 69220)
+++ trunk/Master/texmf-dist/doc/support/latexmk/example_rcfiles/glossary_latexmkrc 2023-12-26 21:04:28 UTC (rev 69221)
@@ -1,39 +1,10 @@
-# 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.
+# In many earlier versions of latexmk, there was a file glossary_latexmrc that
+# originally showed how to use the glossary package with latexmk. That
+# package is now OBSOLETE, and one should use the glossaries package or the
+# glossaries-extra package.
-# N.B. There is also the OBSOLETE glossary package
-# (http://www.ctan.org/pkg/glossary), which has some differences. See item 2.
+# The code for using the glossaries package with latexmk is in the file
+# glossaries_latexmkrc. It also contains (commented out) code for the use
+# of the glossary package, and has some comments on the issues involved.
-# 1. If you use the glossaries or the glossaries-extra package, then you can use:
- add_cus_dep( 'acn', 'acr', 0, 'makeglossaries' );
- add_cus_dep( 'glo', 'gls', 0, 'makeglossaries' );
- $clean_ext .= " acr acn alg glo gls glg";
-
- sub makeglossaries {
- my ($base_name, $path) = fileparse( $_[0] );
- my @args = ( "-q", "-d", $path, $base_name );
- if ($silent) { unshift @args, "-q"; }
- return system "makeglossaries", "-d", $path, $base_name;
- }
-
-# 2. The above will tend to run makeglossaries more often than needed, since
-# each out of date file will trigger the use of makeglossaries, even
-# though makeglossaries makes all the glossaries. The following solution
-# solves this, but at the expense of not having the convenience that
-# makeglossaries can change how it makes the glossaries depending on the
-# settings of the glossaries package.
-# A better solution will need more advanced work.
-#
-# add_cus_dep( 'acn', 'acr', 0, 'makeglossaries' );
-# add_cus_dep( 'glo', 'gls', 0, 'makeglossaries' );
-# $clean_ext .= " acr acn alg glo gls glg";
-#
-# sub makeglossaries {
-# my @args = ( "-s", "$_[0].ist", "-t", "$$Psource.ilg",
-# "-o", $$Pdest, $$Psource );
-# if ($silent) { unshift @args, "-q"; }
-# return system "makeindex", @args;
-# }
-
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 2023-12-26 21:02:15 UTC (rev 69220)
+++ trunk/Master/texmf-dist/doc/support/latexmk/latexmk.txt 2023-12-26 21:04:28 UTC (rev 69221)
@@ -61,7 +61,7 @@
- 6 November 2023 1
+ 24 December 2023 1
@@ -127,7 +127,7 @@
- 6 November 2023 2
+ 24 December 2023 2
@@ -193,7 +193,7 @@
- 6 November 2023 3
+ 24 December 2023 3
@@ -259,7 +259,7 @@
- 6 November 2023 4
+ 24 December 2023 4
@@ -280,9 +280,10 @@
variable to 1 in a configuration file.
Note that when biber is used, and a bib file doesn't exist, this
- option does not currently prevent biber from being run. See the
- documentation on $bibtex_use for more details. However, a bbl
- file is treated as precious.
+ option does not prevent biber from being run, with the bbl file
+ then being incorrect. See the documentation on $bibtex_use for
+ more details. However, a bbl file is treated as precious in a
+ clean up operation.
-bibtex-cond1
@@ -289,62 +290,61 @@
The same as -bibtex-cond except that .bbl files are only treated
as precious if one or more bibfiles fails to exist.
- Thus if all the bib files exist, bibtex is run to generate .bbl
- files as needed, and then it is appropriate to delete the bbl
+ Thus if all the bib files exist, bibtex is run to generate .bbl
+ files as needed, and then it is appropriate to delete the bbl
files in a cleanup operation since they can be re-generated.
- This property can also be configured by setting the $bibtex_use
+ This property can also be configured by setting the $bibtex_use
variable to 1.5 in a configuration file.
Note that when biber is used, and a bib file doesn't exist, this
- option does not currently prevent biber from being run. See the
- documentation on $bibtex_use for more details.
+ option does not prevent biber from being run, with the bbl file
+ then being incorrect. See the documentation on $bibtex_use for
+ more details. However, a bbl file is treated as precious in a
+ clean up operation.
-bibtexfudge or -bibfudge
- Turn on the change-directory fudge for bibtex. See documenta-
+ Turn on the change-directory fudge for bibtex. See documenta-
tion of $bibtex_fudge for details.
-bibtexfudge- or -bibfudge-
- Turn off the change-directory fudge for bibtex. See documenta-
+ Turn off the change-directory fudge for bibtex. See documenta-
tion of $bibtex_fudge for details.
-bm <message>
- A banner message to print diagonally across each page when con-
- verting the dvi file to postscript. The message must be a sin-
+ A banner message to print diagonally across each page when con-
+ verting the dvi file to postscript. The message must be a sin-
gle argument on the command line so be careful with quoting spa-
ces and such.
- Note that if the -bm option is specified, the -ps option is as-
+ Note that if the -bm option is specified, the -ps option is as-
sumed.
+ 24 December 2023 5
- 6 November 2023 5
-
-
-
LATEXMK(1) General Commands Manual LATEXMK(1)
-bi <intensity>
- How dark to print the banner message. A decimal number between
+ How dark to print the banner message. A decimal number between
0 and 1. 0 is black and 1 is white. The default is 0.95, which
is OK unless your toner cartridge is getting low.
-bs <scale>
- 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
+ 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 220.0 which is just right for 5 charac-
ter messages.
@@ -356,42 +356,42 @@
-c Clean up (remove) all regeneratable files generated by latex and
bibtex or biber except dvi, postscript and pdf. These files are
- a combination of log files, aux files, latexmk's database file
- of source file information, and those with extensions specified
- in the @generated_exts configuration variable. In addition,
+ a combination of log files, aux files, latexmk's database file
+ of source file information, and those with extensions specified
+ in the @generated_exts configuration variable. In addition,
files specified by the $clean_ext and @generated_exts configura-
tion variables are removed.
- This cleanup is instead of a regular make. See the -gg option
+ This cleanup is instead of a regular make. See the -gg option
if you want to do a cleanup followed by a make.
- Treatment of .bbl files: If $bibtex_use is set to 0 or 1, bbl
- files are always treated as non-regeneratable. If $bibtex_use
+ Treatment of .bbl files: If $bibtex_use is set to 0 or 1, bbl
+ files are always treated as non-regeneratable. If $bibtex_use
is set to 1.5, bbl files are counted as non-regeneratable condi-
- tionally: If the bib file exists, then bbl files are regenerat-
- able, and are deleted in a clean up. But if $bibtex_use is 1.5
- and a bib file doesn't exist, then the bbl files are treated as
+ tionally: If the bib file exists, then bbl files are regenerat-
+ able, and are deleted in a clean up. But if $bibtex_use is 1.5
+ and a bib file doesn't exist, then the bbl files are treated as
non-regeneratable and hence are not deleted.
- In contrast, if $bibtex_use is set to 2, bbl files are always
+ In contrast, if $bibtex_use is set to 2, bbl files are always
treated as regeneratable, and are deleted in a cleanup.
- Treatment of files generated by custom dependencies: If
- $cleanup_includes_cusdep_generated is nonzero, regeneratable
- files are considered as including those generated by custom de-
- pendencies and are also deleted. Otherwise these files are not
+ Treatment of files generated by custom dependencies: If
+ $cleanup_includes_cusdep_generated is nonzero, regeneratable
+ files are considered as including those generated by custom de-
+ pendencies and are also deleted. Otherwise these files are not
deleted.
-C Clean up (remove) all regeneratable files generated by latex and
bibtex or biber. This is the same as the -c option with the ad-
- dition of dvi, postscript and pdf files, and those specified in
+ dition of dvi, postscript and pdf files, and those specified in
the $clean_full_ext configuration variable.
- 6 November 2023 6
+ 24 December 2023 6
@@ -400,64 +400,64 @@
LATEXMK(1) General Commands Manual LATEXMK(1)
- This cleanup is instead of a regular make. See the -gg option
+ This cleanup is instead of a regular make. See the -gg option
if you want to do a cleanup followed by a make.
- See the -c option for the specification of whether or not .bbl
+ See the -c option for the specification of whether or not .bbl
files are treated as non-regeneratable or regeneratable.
- If $cleanup_includes_cusdep_generated is nonzero, regeneratable
- files are considered as including those generated by custom de-
- pendencies and are also deleted. Otherwise these files are not
+ If $cleanup_includes_cusdep_generated is nonzero, regeneratable
+ files are considered as including those generated by custom de-
+ pendencies and are also deleted. Otherwise these files are not
deleted.
- -CA (Obsolete). Now equivalent to the -C option. See that option
+ -CA (Obsolete). Now equivalent to the -C option. See that option
for details.
- -cd Change to the directory containing the main source file before
- processing it. Then all the generated files (.aux, .log, .dvi,
+ -cd Change to the directory containing the main source file before
+ processing it. Then all the generated files (.aux, .log, .dvi,
.pdf, etc) will be relative to the source file.
- This option is particularly useful when latexmk is invoked from
- a GUI configured to invoke latexmk with a full pathname for the
+ This option is particularly useful when latexmk is invoked from
+ a GUI configured to invoke latexmk with a full pathname for the
source file.
- This option works by setting the $do_cd configuration variable
- to one; you can set that variable if you want to configure la-
+ This option works by setting the $do_cd configuration variable
+ to one; you can set that variable if you want to configure la-
texmk to have the effect of the -cd option without specifying it
on the command line. See the documentation for that variable.
- -cd- Do NOT change to the directory containing the main source file
+ -cd- Do NOT change to the directory containing the main source file
before processing it. Then all the generated files (.aux, .log,
- .dvi, .pdf, etc) will be relative to the current directory
+ .dvi, .pdf, etc) will be relative to the current directory
rather than the source file.
- This is the default behavior and corresponds to the behavior of
+ This is the default behavior and corresponds to the behavior of
the *latex programs. However, it is not desirable behavior when
- latexmk is invoked by a GUI configured to invoke latexmk with a
+ latexmk is invoked by a GUI configured to invoke latexmk with a
full pathname for the source file. See the -cd option.
- This option works by setting the $do_cd configuration variable
- to zero. See the documentation for that variable for more in-
+ This option works by setting the $do_cd configuration variable
+ to zero. See the documentation for that variable for more in-
formation.
- -CF Remove the file containing the database of source file informa-
+ -CF Remove the file containing the database of source file informa-
tion, before doing the other actions requested.
- -d Set draft mode. This prints the banner message "DRAFT" across
- your page when converting the dvi file to postscript. Size and
+ -d Set draft mode. This prints the banner message "DRAFT" across
+ your page when converting the dvi file to postscript. Size and
intensity can be modified with the -bs and -bi options. The -bm
- option will override this option as this is really just a short
+ option will override this option as this is really just a short
way of specifying:
- 6 November 2023 7
+ 24 December 2023 7
@@ -468,27 +468,27 @@
latexmk -bm DRAFT
- Note that if the -d option is specified, the -ps option is as-
+ Note that if the -d option is specified, the -ps option is as-
sumed.
-deps Show a list of dependent files after processing. This is in the
- form of a dependency list of the form used by the make program,
+ form of a dependency list of the form used by the make program,
and it is therefore suitable for use in a Makefile. It gives an
overall view of the files without listing intermediate files, as
well as latexmk can determine them.
- By default the list of dependent files is sent to stdout (i.e.,
- normally to the screen unless you've redirected latexmk's out-
+ By default the list of dependent files is sent to stdout (i.e.,
+ normally to the screen unless you've redirected latexmk's out-
put). But you can set the filename where the list is sent by the
-deps-out= option.
- See the section "USING latexmk WITH make" for an example of how
+ See the section "USING latexmk WITH make" for an example of how
to use a dependency list with make.
- Users familiar with GNU automake and gcc will find that the
- -deps option is very similar in its purpose and results to the
- -M option to gcc. (In fact, latexmk also has options -M, -MF,
+ Users familiar with GNU automake and gcc will find that the
+ -deps option is very similar in its purpose and results to the
+ -M option to gcc. (In fact, latexmk also has options -M, -MF,
and -MP options that behave like those of gcc.)
@@ -496,7 +496,7 @@
Equivalent to -deps.
- -deps- Do not show a list of dependent files after processing. (This
+ -deps- Do not show a list of dependent files after processing. (This
is the default.)
@@ -506,24 +506,24 @@
-deps-escape=<string>
Set the kind of escaping used for spaces in the dependency list.
- The possible values are "none", "unix", "nmake", corresponding
- respectively to no escaping, escaping with a "\" suitable for
- standard Unix make, and escaping with "^", suitable for Micro-
+ The possible values are "none", "unix", "nmake", corresponding
+ respectively to no escaping, escaping with a "\" suitable for
+ standard Unix make, and escaping with "^", suitable for Micro-
soft's nmake.
-deps-out=FILENAME
- Set the filename to which the list of dependent files is writ-
- ten. If the FILENAME argument is omitted or set to "-", then
+ Set the filename to which the list of dependent files is writ-
+ ten. If the FILENAME argument is omitted or set to "-", then
the output is sent to stdout.
- Use of this option also turns on the output of the list of de-
+ Use of this option also turns on the output of the list of de-
pendent files after processing.
- 6 November 2023 8
+ 24 December 2023 8
@@ -532,10 +532,10 @@
LATEXMK(1) General Commands Manual LATEXMK(1)
- -dF Dvi file filtering. The argument to this option is a filter
- which will generate a filtered dvi file with the extension
- ".dviF". All extra processing (e.g. conversion to postscript,
- preview, printing) will then be performed on this filtered dvi
+ -dF Dvi file filtering. The argument to this option is a filter
+ which will generate a filtered dvi file with the extension
+ ".dviF". All extra processing (e.g. conversion to postscript,
+ preview, printing) will then be performed on this filtered dvi
file.
Example usage: To use dviselect to select only the even pages of
@@ -545,91 +545,97 @@
-diagnostics
- Print detailed diagnostics during a run. This may help for de-
- bugging problems or to understand latexmk's behavior in diffi-
+ Print detailed diagnostics during a run. This may help for de-
+ bugging problems or to understand latexmk's behavior in diffi-
cult situations.
-dir-report
- For each .tex file processed, list the settings for aux and out
- directories, after they have been normalized from the settings
- specified during initialization. See the description of the
+ For each .tex file processed, list the settings for aux and out
+ directories, after they have been normalized from the settings
+ specified during initialization. See the description of the
variable $aux_out_dir_report for more details.
-dir-report-
- Do not report the settings for aux and out directories. (De-
+ Do not report the settings for aux and out directories. (De-
fault)
+ -dir-report-only
+ After all initialization is complete, give the settings for the
+ aux and out directories, and then halt. This option is primar-
+ ily used for debugging configuration issues.
+
+
-dvi Generate dvi version of document using latex.
-dvilua
- Generate dvi version of document using lualatex instead of la-
+ Generate dvi version of document using lualatex instead of la-
tex.
- -dvi- Turn off generation of dvi version of document. (This may get
- overridden, if some other file is made (e.g., a .ps file) that
- is generated from the dvi file, or if no generated file at all
+ -dvi- Turn off generation of dvi version of document. (This may get
+ overridden, if some other file is made (e.g., a .ps file) that
+ is generated from the dvi file, or if no generated file at all
is requested.)
-dvilualatex="COMMAND"
This sets the string specifying the command to run dvi lualatex.
- It behaves like the -pdflatex option, but sets the variable
+ It behaves like the -pdflatex option, but sets the variable
$dvilualatex.
- Note: This option when provided with the COMMAND argument only
- sets the command for invoking dvilualatex; it does not turn on
- the use of dvilualatex. That is done by other options or in an
- initialization file.
+ 24 December 2023 9
- 6 November 2023 9
+LATEXMK(1) General Commands Manual LATEXMK(1)
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ Note: This option when provided with the COMMAND argument only
+ sets the command for invoking dvilualatex; it does not turn on
+ the use of dvilualatex. That is done by other options or in an
+ initialization file.
-e <code>
- Execute the specified initialization code before processing.
- The code is Perl code of the same form as is used in latexmk's
- initialization files. For more details, see the information on
- the -r option, and the section about "Configuration/initializa-
- tion (RC) files". The code is typically a sequence of assign-
+ Execute the specified initialization code before processing.
+ The code is Perl code of the same form as is used in latexmk's
+ initialization files. For more details, see the information on
+ the -r option, and the section about "Configuration/initializa-
+ tion (RC) files". The code is typically a sequence of assign-
ment statements separated by semicolons.
- The code is executed when the -e option is encountered during
- latexmk's parsing of its command line. See the -r option for a
- way of executing initialization code from a file. An error re-
- sults in latexmk stopping. Multiple instances of the -r and -e
+ The code is executed when the -e option is encountered during
+ latexmk's parsing of its command line. See the -r option for a
+ way of executing initialization code from a file. An error re-
+ sults in latexmk stopping. Multiple instances of the -r and -e
options can be used, and they are executed in the order they ap-
pear on the command line.
Some care is needed to deal with proper quoting of special char-
- acters in the code on the command line. For example, suppose
- you want to set the latex command to use its -shell-escape op-
+ acters in the code on the command line. For example, suppose
+ you want to set the latex command to use its -shell-escape op-
tion, then under UNIX/Linux you could use the line
latexmk -e '$latex=q/latex %O -shell-escape %S/' file.tex
- Note that the single quotes block normal UNIX/Linux command
- shells from treating the characters inside the quotes as spe-
- cial. (In this example, the q/.../ construct is a Perl idiom
- equivalent to using single quotes. This avoids the complica-
- tions of getting a quote character inside an already quoted
- string in a way that is independent of both the shell and the
+ Note that the single quotes block normal UNIX/Linux command
+ shells from treating the characters inside the quotes as spe-
+ cial. (In this example, the q/.../ construct is a Perl idiom
+ equivalent to using single quotes. This avoids the complica-
+ tions of getting a quote character inside an already quoted
+ string in a way that is independent of both the shell and the
operating-system.)
- The above command line will NOT work under MS-Windows with
- cmd.exe or command.com or 4nt.exe. For MS-Windows with these
+ The above command line will NOT work under MS-Windows with
+ cmd.exe or command.com or 4nt.exe. For MS-Windows with these
command shells you could use
latexmk -e "$latex=q/latex %O -shell-escape %S/" file.tex
@@ -638,68 +644,67 @@
latexmk -e "$latex='latex %O -shell-escape %S'" file.tex
- The last two examples will NOT work with UNIX/Linux command
+ The last two examples will NOT work with UNIX/Linux command
shells.
- (Note: the above examples show are to show how to use the -e to
- specify initialization code to be executed. But the particular
+ (Note: the above examples show are to show how to use the -e to
+ specify initialization code to be executed. But the particular
effect can be achieved also by the use of the -latex option with
less problems in dealing with quoting.)
- -emulate-aux-dir
- Emulate the use of an aux directory instead of leaving it to the
- *latex programs to do it. (MiKTeX supports -aux-directory, but
- TeXLive doesn't.)
+ 24 December 2023 10
- 6 November 2023 10
+LATEXMK(1) General Commands Manual LATEXMK(1)
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ -emulate-aux-dir
+ Emulate the use of an aux directory instead of leaving it to the
+ *latex programs to do it. (MiKTeX supports -aux-directory, but
+ TeXLive doesn't.)
-
- See the section AUXILIARY AND OUTPUT DIRECTORIES for more de-
+ See the section AUXILIARY AND OUTPUT DIRECTORIES for more de-
tails.
-emulate-aux-dir-
Turn off emulation to implement an aux directory and leave it to
- the *latex program to handle the case that the aux directory is
- different from the output directory. Note that if you use
- TeXLive, which doesn't support -aux-directory, latexmk will au-
- tomatically switch aux_dir emulation on after the first run of
+ the *latex program to handle the case that the aux directory is
+ different from the output directory. Note that if you use
+ TeXLive, which doesn't support -aux-directory, latexmk will au-
+ tomatically switch aux_dir emulation on after the first run of
*latex, because it will find the .log file in the wrong place.
- -f Force latexmk to continue document processing despite errors.
+ -f Force latexmk to continue document processing despite errors.
Normally, when latexmk detects that LaTeX or another program has
found an error which will not be resolved by further processing,
no further processing is carried out.
- Note: "Further processing" means the running of other programs
- or the rerunning of latex (etc) that would be done if no errors
- had occurred. If instead, or additionally, you want the latex
- (etc) program not to pause for user input after an error, you
- should arrange this by an option that is passed to the program,
- e.g., by latexmk's option -interaction=nonstopmode (which la-
+ Note: "Further processing" means the running of other programs
+ or the rerunning of latex (etc) that would be done if no errors
+ had occurred. If instead, or additionally, you want the latex
+ (etc) program not to pause for user input after an error, you
+ should arrange this by an option that is passed to the program,
+ e.g., by latexmk's option -interaction=nonstopmode (which la-
texmk passes to *latex).
-f- Turn off the forced processing-past-errors such as is set by the
- -f option. This could be used to override a setting in a con-
+ -f option. This could be used to override a setting in a con-
figuration file.
- -g Force latexmk to process document fully, even under situations
- where latexmk would normally decide that no changes in the
- source files have occurred since the previous run. This option
- is useful, for example, if you change some options and wish to
+ -g Force latexmk to process document fully, even under situations
+ where latexmk would normally decide that no changes in the
+ source files have occurred since the previous run. This option
+ is useful, for example, if you change some options and wish to
reprocess the files.
@@ -714,22 +719,26 @@
Print help information.
- -jobname=STRING
- Set the basename of output files(s) to STRING, instead of the
- default, which is the basename of the specified TeX file. (At
- present, STRING should not contain spaces.)
+ 24 December 2023 11
- 6 November 2023 11
-
LATEXMK(1) General Commands Manual LATEXMK(1)
+ -hnt Generate hnt (HINT) version of document using hilatex. (And
+ turn off dvi, postscript, and pdf modes.)
+
+
+ -jobname=STRING
+ Set the basename of output files(s) to STRING, instead of the
+ default, which is the basename of the specified TeX file. (At
+ present, STRING should not contain spaces.)
+
This is like the same option for current implementations of the
*latex, and the passing of this option to these programs is part
of latexmk's implementation of -jobname.
@@ -776,26 +785,25 @@
-latex="COMMAND" option.
- -latex="COMMAND"
- This sets the string specifying the command to run latex, and is
- typically used to add desired options. Since the string nor-
- mally contains spaces, it should be quoted, e.g.,
- latexmk -latex="latex --shell-escape %O %S" foo.tex
- The specification of the contents of the string are the same as
+ 24 December 2023 12
- 6 November 2023 12
+LATEXMK(1) General Commands Manual LATEXMK(1)
+ -latex="COMMAND"
+ This sets the string specifying the command to run latex, and is
+ typically used to add desired options. Since the string nor-
+ mally contains spaces, it should be quoted, e.g.,
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ latexmk -latex="latex --shell-escape %O %S" foo.tex
-
+ The specification of the contents of the string are the same as
for the $latex configuration variable. Depending on your oper-
ating system and the command-line shell you are using, you may
need to change the single quotes to double quotes (or something
@@ -841,25 +849,25 @@
-lualatex="COMMAND"
This sets the string specifying the command to run lualatex. It
- behaves like the -pdflatex option, but sets the variable $luala-
- tex.
+ behaves like the -pdflatex option, but sets the variable
- Note: This option when provided with the COMMAND argument only
- sets the command for invoking lualatex; it does not turn on the
- use of lualatex. That is done by other options or in an initial-
- ization file.
+ 24 December 2023 13
- 6 November 2023 13
+LATEXMK(1) General Commands Manual LATEXMK(1)
+ $lualatex.
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ Note: This option when provided with the COMMAND argument only
+ sets the command for invoking lualatex; it does not turn on the
+ use of lualatex. That is done by other options or in an initial-
+ ization file.
-M Show list of dependent files after processing. This is equiva-
@@ -887,6 +895,10 @@
tation of $makeindex_fudge for details.
+ $min_sleep_time [0.01]
+ This is the minimum nonzero value allowed for $sleep_time.
+
+
-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-
@@ -903,37 +915,37 @@
-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.
+ dows, the substitution of "\" for the separator character
- 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
+ 24 December 2023 14
- 6 November 2023 14
+LATEXMK(1) General Commands Manual LATEXMK(1)
+ between 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.
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ See the documentation for the configuration variable
+ $MSWin_back_slash for more details.
- continuous-preview mode, test for a previously running previewer
- for the same file and not start a new one if a previous pre-
- viewer is running. However, its test sometimes fails (notably
- if there is an already-running previewer that is viewing a file
- of the same name as the current file, but in a different direc-
- tory). This option turns off the default behavior.
+ -new-viewer
+ When in continuous-preview mode, always start a new viewer to
+ view the generated file. By default, latexmk will, in continu-
+ ous-preview mode, test for a previously running previewer for
+ the same file and not start a new one if a previous previewer is
+ running. However, its test sometimes fails (notably if there is
+ an already-running previewer that is viewing a file of the same
+ name as the current file, but in a different directory). This
+ option turns off the default behavior.
-new-viewer-
@@ -970,31 +982,31 @@
-outdir=FOO or -output-directory=FOO
- Sets the directory for the output files of *latex.
- If the aux directory is not set or is the same as the output di-
- rectory, then all output files of *latex are sent to the output
- directory.
- If the aux directory is set, e.g., by the option -auxdir, and is
- not equal to the output directory, then only final output files
- (.dvi, .ps, .pdf, .synctex, .synctex.gz) are sent to the output
- directory. Other generated files are sent to the aux directory.
- See the section AUXILIARY AND OUTPUT DIRECTORIES for more
+ 24 December 2023 15
- 6 November 2023 15
+LATEXMK(1) General Commands Manual LATEXMK(1)
+ Sets the directory for the output files of *latex.
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ If the aux directory is not set or is the same as the output di-
+ rectory, then all output files of *latex are sent to the output
+ directory.
+ If the aux directory is set, e.g., by the option -auxdir, and is
+ not equal to the output directory, then only final output files
+ (.dvi, .ps, .pdf, .synctex, .synctex.gz) are sent to the output
+ directory. Other generated files are sent to the aux directory.
- details.
+ See the section AUXILIARY AND OUTPUT DIRECTORIES for more de-
+ tails.
-output-format=FORMAT
@@ -1036,6 +1048,18 @@
-pdf Generate pdf version of document using pdflatex. (If you wish
to use lualatex or xelatex, you can use whichever of the options
+
+
+
+ 24 December 2023 16
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
-pdflua, -pdfxe, -lualatex or -xelatex applies.) To configure
latexmk to have such behavior by default, see the section on
"Configuration/initialization (rc) files".
@@ -1050,16 +1074,6 @@
-dvilua option or by setting $dvi_mode to 2.
-
- 6 November 2023 16
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
-pdflua
Generate pdf version of document using lualatex.
@@ -1100,6 +1114,18 @@
used in the $latex configuration variable).
+
+
+
+ 24 December 2023 17
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
-pdflatex
This sets the generation of pdf files by pdflatex, and turns off
the generation of dvi and ps files.
@@ -1114,18 +1140,6 @@
mally contains spaces, it should be quoted, e.g.,
latexmk -pdf -pdflatex="pdflatex --shell-escape %O %S"
-
-
-
- 6 November 2023 17
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
foo.tex
The specification of the contents of the string are the same as
@@ -1166,32 +1180,33 @@
An example:
latexmk -pretex='\AtBeginDocument{Message\par}' -usepretex
- foo.tex
- But this is better written
- latexmk -usepretex='\AtBeginDocument{Message\par}' foo.tex
- If you already have a suitable command configured, you only need
+ 24 December 2023 18
- latexmk -pretex='\AtBeginDocument{Message\par}' foo.tex
- -print=dvi, -print=ps, -print=pdf, -print=auto,
- Define which kind of file is printed. This option also ensures
- that the requisite file is made, and turns on printing.
+LATEXMK(1) General Commands Manual LATEXMK(1)
- 6 November 2023 18
+ foo.tex
+ But this is better written
+ latexmk -usepretex='\AtBeginDocument{Message\par}' foo.tex
+ If you already have a suitable command configured, you only need
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ latexmk -pretex='\AtBeginDocument{Message\par}' foo.tex
+ -print=dvi, -print=ps, -print=pdf, -print=auto,
+ Define which kind of file is printed. This option also ensures
+ that the requisite file is made, and turns on printing.
+
The (default) case -print=auto determines the kind of print file
automatically from the set of files that is being made. The
first in the list postscript, pdf, dvi that is among the files
@@ -1233,6 +1248,16 @@
turns them off.
+
+ 24 December 2023 19
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
-pv- Turn off -pv.
@@ -1246,18 +1271,6 @@
compatible with the -p and -pv options, so it turns these op-
tions off.
-
-
-
- 6 November 2023 19
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
The -pvc option also turns off force mode (-f), as is normally
best for continuous preview mode. If you really want force
mode, use the options in the order -pvc -f.
@@ -1298,32 +1311,34 @@
compiling the document.
- -pvctimeout-
- Don't do timeout in pvc mode after inactivity.
- -pvctimeoutmins=<time>
- Set period of inactivity in minutes for pvc timeout.
- -quiet Same as -silent
+ 24 December 2023 20
- -r <rcfile>
- Read the specified initialization file ("RC file") before pro-
- cessing.
- 6 November 2023 20
+LATEXMK(1) General Commands Manual LATEXMK(1)
+ -pvctimeout-
+ Don't do timeout in pvc mode after inactivity.
+ -pvctimeoutmins=<time>
+ Set period of inactivity in minutes for pvc timeout.
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ -quiet Same as -silent
+
+ -r <rcfile>
+ Read the specified initialization file ("RC file") before pro-
+ cessing.
+
Be careful about the ordering: (1) Standard initialization files
-- see the section below on "Configuration/initialization (RC)
files" -- are read first. (2) Then the options on the command
@@ -1363,31 +1378,31 @@
den in an initialization file.
For further information, see the documentation for the $recorder
- configuration variable.
- -recorder-
- Do not supply the -recorder option with *latex.
+ 24 December 2023 21
- -rules Show a list of latemk's rules and dependencies after processing.
- -rules-
- Do not show a list of latexmk's rules and dependencies after
- processing. (This is the default.)
+LATEXMK(1) General Commands Manual LATEXMK(1)
+ configuration variable.
- 6 November 2023 21
+ -recorder-
+ Do not supply the -recorder option with *latex.
+ -rules Show a list of latemk's rules and dependencies after processing.
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ -rules-
+ Do not show a list of latexmk's rules and dependencies after
+ processing. (This is the default.)
-showextraoptions
@@ -1429,6 +1444,18 @@
tions.
Also reduce the number of informational messages that latexmk
+
+
+
+ 24 December 2023 22
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
itself generates.
To change the options used to make the commands run silently,
@@ -1445,17 +1472,6 @@
Sets the commands for latex, etc, so that they are the standard
ones. This is useful to override special configurations.
-
-
- 6 November 2023 22
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
The result is that $latex = 'latex %O %S', and similarly for
$pdflatex, $lualatex, and $xelatex. (The option -no-pdf needed
for $xelatex is provided automatically, given that %O appears in
@@ -1495,6 +1511,17 @@
fault.)
+
+
+ 24 December 2023 23
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
-usepretex
Sets the command lines for latex, etc, so that they use the code
that is defined by the variable $pre_tex_code or that is set by
@@ -1511,17 +1538,6 @@
-usepretex=CODE
Equivalent to -pretex=CODE -usepretex. Example
-
-
- 6 November 2023 23
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
latexmk -usepretex='\AtBeginDocument{Message\par}' foo.tex
@@ -1561,6 +1577,17 @@
-xdv Generate xdv version of document using xelatex.
+
+
+ 24 December 2023 24
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
-xelatex
Use xelatex. That is, use xelatex to process the source file(s)
to pdf. The generation of dvi and postscript files is turned
@@ -1576,18 +1603,6 @@
file, and does all the extra runs needed (including those of
bibtex, etc). Only after that does it make the pdf file from
the .xdv file, using xdvipdfmx. See the documentation for the
-
-
-
- 6 November 2023 24
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
-pdfxe for why this is done.]
@@ -1627,6 +1642,18 @@
% latexmk thesis # run latex enough times to resolve
cross-references
+
+
+
+ 24 December 2023 25
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
% latexmk -pvc -ps thesis# run latex enough times to resolve
cross-references, make a postscript
file, start a previewer. Then
@@ -1644,16 +1671,6 @@
-
- 6 November 2023 25
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
DEALING WITH ERRORS, PROBLEMS, ETC
Some possibilities:
@@ -1691,6 +1708,18 @@
f. There's a useful trick that can be used when you use lualatex in-
stead of pdflatex (and in some related situations). The problem is
+
+
+
+ 24 December 2023 26
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
that latexmk won't notice a dependency on a file, bar.baz say, that is
input by the lua code in your document instead of by the LaTeX part.
(Thus if you change bar.baz and rerun latexmk, then latexmk will think
@@ -1708,18 +1737,6 @@
g. See also the section "Advanced Configuration: Some extra resources".
-
-
-
- 6 November 2023 26
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
h. Look on tex.stackexchange, i.e., at http://tex.stackex-
change.com/questions/tagged/latexmk Someone may have already solved
your problem.
@@ -1757,6 +1774,18 @@
tex programs, these directories default to the current directory, and
then the generated files aren't segregated. If the two directories are
the same, as is the simplest situation, then all generated files are
+
+
+
+ 24 December 2023 27
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
written to the same directory, and one often simply refers to the out-
put directory, without mentioning a separate aux directory.
@@ -1774,18 +1803,6 @@
separate aux and output directories. Latexmk deals with this by being
able to emulating a separate aux directory: In this method it invokes
*latex with just an -output-directory option, with the directory set
-
-
-
- 6 November 2023 27
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
not to the desired output directory, but to the aux directory. After
running *latex, it moves the relevant final output file(s) to the in-
tended output directory. Emulation can be turned on by setting the
@@ -1822,8 +1839,20 @@
cause of compatibility issues, is of .fls files: See below.
Note that xelatex when invoked with its -no-pdf option, as latexmk
- does, generates an .xdv file, which would appear to have the same sta-
- tus as a .dvi file generated by latex. Nevertheless, latexmk treats
+ does, generates an .xdv file, which would appear to have the same
+
+
+
+ 24 December 2023 28
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
+ status as a .dvi file generated by latex. Nevertheless, latexmk treats
.xdv as an intermediate file that is found in the aux directory. This
is to match MiKTeX's treatment of the -aux-directory option. As fur-
ther justification, one can say that under modern conditions an .xdv
@@ -1840,18 +1869,6 @@
the default is to set it equal to the output directory. For the output
directory, the default is to be the current directory.
-
-
-
- 6 November 2023 28
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
For the turning on and off of the emulation mode, there is the configu-
ration variable $emulate_aux and the options -emulate-aux-dir, -emu-
late-aux-dir-, -noemulate-aux-dir.
@@ -1889,6 +1906,18 @@
programs, by default, will refuse to work when they find that they are
asked to write to a file in a directory that appears not to be the cur-
rent working directory or one of its subdirectories. This is part of
+
+
+
+ 24 December 2023 29
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
security measures by the whole TeX system that try to prevent malicious
or errant TeX documents from incorrectly messing with a user's files.
@@ -1907,17 +1936,6 @@
variable openout_any to "a" (as in "all"), to override the default
"paranoid" setting.
-
-
- 6 November 2023 29
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
Certain names of aux and output directories not allowed on Microsoft
Windows: It is natural to want to use the name "aux" for the aux direc-
tory, e.g., by using the option -auxdir=aux. But on Microsoft operat-
@@ -1954,6 +1972,18 @@
and then latexmk can adjust its processing to accommodate this situa-
tion. The difference in output file type can happen for two reasons:
One is that for latex, pdflatex and lualatex the document itself can
+
+
+
+ 24 December 2023 30
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
override the defaults. The other is that there may be a configuration,
or misconfiguration, such that the program that latexmk invokes to com-
pile the document is not the expected one, or is given options incom-
@@ -1973,17 +2003,6 @@
useful to force output to be of the .dvi format by inserting \pdfout-
put=0 in the preamble of the document.
-
-
- 6 November 2023 30
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
Another example is where the document uses graphics file of the .pdf,
.jpg, and png types. With the default setting for the graphicx pack-
age, these can be processed in compilation to .pdf but not with compi-
@@ -2021,6 +2040,16 @@
+
+ 24 December 2023 31
+
+
+
+
+
+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
@@ -2038,18 +2067,6 @@
The
directories are searched in the following order, and latexmk uses
the first such file it finds (if any):
-
-
-
- 6 November 2023 31
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
"/etc",
"/opt/local/share/latexmk",
"/usr/local/share/latexmk",
@@ -2089,6 +2106,16 @@
texmk does not look for an RC file under it.
+
+ 24 December 2023 32
+
+
+
+
+
+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.
@@ -2104,18 +2131,6 @@
Note that command line options are obeyed in the order in which they
are written; thus any RC file specified on the command line with the -r
-
-
-
- 6 November 2023 32
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
option can override previous options but can be itself overridden by
later options on the command line. There is also the -e option, which
allows initialization code to be specified in latexmk's command line.
@@ -2155,6 +2170,18 @@
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
+
+
+
+ 24 December 2023 33
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
these complications.)
You can do much more complicated things, but for this you will need to
@@ -2171,17 +2198,6 @@
bilities listed here do not apply to the $kpsewhich variable; see its
documentation.)
-
-
- 6 November 2023 33
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
Placeholders: Supposed you wanted latexmk to use the command elatex in
place of the regular latex command, and suppose moreover that you
wanted to give it the option "--shell-escape". You could do this by
@@ -2220,6 +2236,18 @@
source file is read.
If the variable $pre_tex_code is the empty string, then %P is
+
+
+
+ 24 December 2023 34
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
equivalent to %S.
%R root filename. This is the base name for the main tex file.
@@ -2237,17 +2265,6 @@
substituted for %U (appropriately quoted). Otherwise it is re-
placed by a null string.
-
-
- 6 November 2023 34
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
%Y Name of directory for auxiliary output files (see the configura-
tion variable $aux_dir). A directory separation character ('/')
is appended if $aux_dir is non-empty and does not end in a suit-
@@ -2285,6 +2302,18 @@
"Detaching" a command: Normally when latexmk runs a command, it waits
for the command to run to completion. This is appropriate for commands
+
+
+
+ 24 December 2023 35
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
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
@@ -2302,18 +2331,6 @@
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
-
-
-
- 6 November 2023 35
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
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.
@@ -2352,6 +2369,17 @@
$dvi_previewer = 'start %S';
+
+
+ 24 December 2023 36
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
Under MS-Windows, this will cause to be run whatever program the system
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-
@@ -2368,18 +2396,6 @@
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
-
-
-
- 6 November 2023 36
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
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
@@ -2419,6 +2435,17 @@
$pdflatex = 'pdflatex --shell-escape %O %S; pst2pdf_for_latexmk
%B';
+
+
+ 24 December 2023 37
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
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.
@@ -2434,18 +2461,6 @@
the MS-Windows command-line processor cmd.exe.
-
-
-
- 6 November 2023 37
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
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-
@@ -2485,6 +2500,18 @@
chosen name for the output file.)
This use of a temporary file solves a problem that the making of
+
+
+
+ 24 December 2023 38
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
these files can occupy a substantial time. If a viewer (notably
gv) sees that the file has changed, it may read the new file be-
fore the program writing the file has not yet finished its work,
@@ -2500,18 +2527,6 @@
After a run of latex (etc), always analyze .log for input files
in the <...> and (...) constructions. Otherwise, only do the
-
-
-
- 6 November 2023 38
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
analysis when fls file doesn't exist or is out of date.
Under normal circumstances, the data in the fls file is reli-
@@ -2550,46 +2565,53 @@
takes the aux directory to equal the output directory which is
the directory to which final output files are to be written.
- If neither variable is set, then the current directory when *la-
- tex is invoked is used both for the aux and output directories.
+ If neither variable is set, then the current directory when
- If the aux and output directories are distinct, then the aux di-
- rectory contains all generated files with the exception of "fi-
- nal output files", which are defined to be .dvi, .ps, .pdf,
- .synctex, and .synctex.gz files.
- See the section AUXILIARY AND OUTPUT DIRECTORIES for more de-
- tails.
+ 24 December 2023 39
- $aux_out_dir_report [0]
- For each primary .tex file processed, list the settings for aux
- and output directories, after they have been normalized from the
- 6 November 2023 39
+LATEXMK(1) General Commands Manual LATEXMK(1)
+ *latex is invoked is used both for the aux and output directo-
+ ries.
+ If the aux and output directories are distinct, then the aux di-
+ rectory contains all generated files with the exception of "fi-
+ nal output files", which are defined to be .dvi, .ps, .pdf,
+ .synctex, and .synctex.gz files.
+ See the section AUXILIARY AND OUTPUT DIRECTORIES for more de-
+ tails.
-LATEXMK(1) General Commands Manual LATEXMK(1)
- settings specified during initialization.
+ $aux_out_dir_report [0]
+ If this variable is set to 1, then prior to the processing of
+ each primary .tex file, list the settings for aux and output di-
+ rectories, after they have been normalized from the settings
+ specified during initialization.
This report gives a reminder of where to look for generated
files.
- The report has to be done per primary .tex file, because of pos-
- sible directory changes for each file (when the -cd option is
- used). In the simplest cases, the directory names are the same
- as originally specified. But in general some clean up/normal-
- ization is performed; this helps performance and cleans up out-
- put to the screen.
+ The report is done per primary .tex file, because of possible
+ directory changes for each file (when the -cd option is used).
+ In the simplest cases, the directory names are the same as orig-
+ inally specified. But in general some clean up/normalization is
+ performed; this helps performance and cleans up output to the
+ screen.
+ If this variable is set to 2, then halt after reporting the set-
+ tings for the aux and out directories, rather than continuing
+ with processing of tex files. This setting is primarily used
+ for debugging configuration issues. See the -dir-report-only
+ option.
$bad_warning_is_error [0]
@@ -2610,6 +2632,18 @@
$banner [0]
If nonzero, the banner message is printed across each page when
+
+
+
+ 24 December 2023 40
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
converting the dvi file to postscript. Without modifying the
variable $banner_message, this is equivalent to specifying the
-d option.
@@ -2632,18 +2666,6 @@
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
-
-
-
- 6 November 2023 40
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
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.
@@ -2677,6 +2699,17 @@
may need to set the variable @BIBINPUTS.
+
+
+ 24 December 2023 41
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
$biber ["biber %O %S"]
The biber processing program.
@@ -2699,17 +2732,6 @@
find extra aux files, as produced by the \include command in
TeX.
-
-
- 6 November 2023 41
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
b. With all moderately recent versions of bibtex, bibtex may
refuse to write its bbl and blg files, for security reasons, for
certain cases of the path component of the filename given to it.
@@ -2740,16 +2762,39 @@
The possible values of $bibtex_use are:
0: never use bibtex or biber; never delete .bbl files in a
cleanup.
- 1: only use bibtex if the bib file(s) exist; never delete .bbl
- files in a cleanup.
- 1.5: only use bibtex if the bib files exist; conditionally
- delete .bbl files in a cleanup (i.e., delete them only when the
- bib files all exist).
+ 1: only use bibtex or biber if the bib file(s) exist; never
+ delete .bbl files in a cleanup.
+
+
+
+ 24 December 2023 42
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
+ 1.5: only use bibtex or biber if the bib files exist;
+ conditionally delete .bbl files in a cleanup (i.e., delete
+ them only when
+ the bib files all exist).
2: run bibtex or biber whenever it appears necessary to update
the bbl file(s), without testing for the existence of the bib
files; always delete .bbl files in a cleanup.
+ Note: When biber is being used, conditional use of biber can be
+ problematic. From latexmk's point of view the problem is that
+ because of how biber works, a full knowledge of its source files
+ can only be obtained after running biber. In contrast, for bib-
+ tex, full information on which bib files are used is obtained
+ from the .aux file(s) after a run of *latex. But for biber, the
+ corresponding information is somewhat incomplete; this the in-
+ formation obtained in the .bcf file that is generated by the
+ biblatex package during a run of *latex.
+
$cleanup_includes_cusdep_generated [0]
If nonzero, specifies that cleanup also deletes files that are
generated by custom dependencies. (When doing a clean up, e.g.,
@@ -2764,18 +2809,6 @@
generation generated files.
This operation is somewhat dangerous, and can have unintended
-
-
-
- 6 November 2023 42
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
consequences, since the files to be deleted are determined from
a file created by *latex, which can contain erroneous informa-
tion. Therefore this variable is turned off by default, and then
@@ -2796,6 +2829,19 @@
options. But there should be no need to set this variable from
an RC file.
+
+
+
+
+ 24 December 2023 43
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
$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
@@ -2830,18 +2876,6 @@
in $out_dir instead of $aux_dir. This also handles the case of
deleting any fls file, since that file is in $out_dir.
-
-
-
- 6 November 2023 43
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
The filenames specified 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
@@ -2863,6 +2897,17 @@
tion is selected, i.e., extensions of files to remove when the
.dvi, etc files are to be cleaned-up.
+
+
+ 24 December 2023 44
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
More general patterns are allowed, as for $clean_ext.
The files specified by $clean_full_ext to be deleted are rela-
@@ -2896,18 +2941,6 @@
An example of a simple setting of these variables is as follows
-
-
-
- 6 November 2023 44
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
$compiling_cmd = "xdotool search --name \"%D\" set_window
--name \"%D compiling\"";
$success_cmd = "xdotool search --name \"%D\" set_window
@@ -2928,11 +2961,23 @@
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.
+ mand changing the title of the edit window. The visual
+
+
+ 24 December 2023 45
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
+ indication in a window title can useful, since the user does not
+ have to keep shifting attention to the (possibly hidden) compi-
+ lation 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
@@ -2963,17 +3008,6 @@
@default_files = ("*.tex");
-
-
- 6 November 2023 45
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
@default_excluded_files = ("common.tex");
If you have a variable or large number of files to be processed,
@@ -2994,6 +3028,18 @@
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
+
+
+
+ 24 December 2023 46
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
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
@@ -3028,18 +3074,6 @@
run.
-
-
-
- 6 November 2023 46
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
$deps_escape ["none"]
This variable determines which kind of escaping of space charac-
ters to use in dependency lists. The possible values are "none",
@@ -3060,6 +3094,18 @@
Name of file to receive list(s) of dependencies at the end of a
run, to be used if $dependents_list is set. If the filename is
"-", then the dependency list is set to stdout (i.e., normally
+
+
+
+ 24 December 2023 47
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
the screen).
@@ -3084,9 +3130,9 @@
$dvilualatex = "dvilualatex --src-specials
%O %S";
- To do a coordinated setting of all of $dvilualatex, $latex,
- $pdflatex, $lualatex, and $xelatex, see the section "Advanced
- Configuration".
+ To do a coordinated setting of all of $dvilualatex, $hilatex,
+ $latex, $pdflatex, $lualatex, and $xelatex, see the section "Ad-
+ vanced Configuration".
$dvi_mode [See below for default]
@@ -3093,21 +3139,9 @@
If one, generate a dvi version of the document by use of latex.
Equivalent to the -dvi option.
- If 2, generate a dvi version of the document by use of
+ If 2, generate a dvi version of the document by use of dviluala-
+ tex. Equivalent to the -dvilua option.
-
-
- 6 November 2023 47
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
- dvilualatex. Equivalent to the -dvilua option.
-
The variable $dvi_mode defaults to 0, but if no explicit re-
quests are made for other types of file (postscript, pdf), then
$dvi_mode will be set to 1. In addition, if a request for a
@@ -3126,6 +3160,18 @@
$dvi_previewer ["start xdvi %O %S" under UNIX]
The command to invoke a dvi-previewer. [Under MS-Windows the
+
+
+
+ 24 December 2023 48
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
default is "start"; then latexmk arranges to use the MS-Windows
start program, which will cause to be run whatever command the
system has associated with .dvi files.]
@@ -3161,17 +3207,6 @@
$dvipdf_silent_switch ["-q"]
Switch(es) for dvipdf program when silent mode is on.
-
-
- 6 November 2023 48
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
N.B. The standard dvipdf program runs silently, so adding the
silent switch has no effect, but is actually innocuous. But if
an alternative program is used, e.g., dvipdfmx, then the silent
@@ -3192,6 +3227,17 @@
Switch(es) for dvips program when pdf file is to be generated
from .ps file.
+
+
+ 24 December 2023 49
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
$dvips_silent_switch ["-q"]
Switch(es) for dvips program when silent mode is on.
@@ -3227,17 +3273,6 @@
variable $dvi_update_method. The default value is the one ap-
propriate for xdvi on a UNIX system.
-
-
- 6 November 2023 49
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
$emulate_aux [0]
Whether to emulate the use of aux directory when $aux_dir and
$out_dir are different, rather than using the -aux-directory op-
@@ -3256,8 +3291,20 @@
output directory provided to *latex is set to be the desired aux
directory. After that, any files that need to be in the output
directory will be moved there by latexmk. (These are the files
- with extensions .dvi, .ps, .pdf, .synctex, .synctex.gz, and, de-
- pending on the setting of the $fls_uses_out_dir variable, also
+ with extensions .dvi, .ps, .pdf, .synctex, .synctex.gz, and,
+
+
+
+ 24 December 2023 50
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
+ depending on the setting of the $fls_uses_out_dir variable, also
the .fls file.)
@@ -3293,27 +3340,58 @@
The regular expression itself is
+ ^Missing file\s+(.+)\s*$
+ But the corresponding string specification in the push statement
+ has to have the backslashes doubled.
- 6 November 2023 50
+ This regular expression matches a line that starts with 'No
+ file', then has one or more white space characters, then any
+ number of characters forming the filename, then possible white
+ space, and finally the end of the line. (See documentation on
+ Perl regular expressions for details.)
+ $filetime_causality_threshold [5]
+ The use of this variable is as follows: At a number of places,
+ latexmk needs to determine whether a particular file has been
+ produced during a just-concluded run of some rule/program or is
+ leftover from a previous run. (An example is the production of a
+ .bcf file by the biblatex package during a run of *latex to
+ 24 December 2023 51
+
+
+
+
+
LATEXMK(1) General Commands Manual LATEXMK(1)
- ^Missing file\s+(.+)\s*$
+ provide bibliographic information to the biber program. If a
+ .bcf file is not produced during a current run of *latex, but is
+ leftover from a previous run, then latexmk has to conclude that
+ the .tex document has changed so that biber is no longer to be
+ used.)
- But the corresponding string specification in the push statement
- has to have the backslashes doubled.
+ Latexmk's criterion that a file has been produced during a run
+ is that the modification time of the file is more recent than
+ the system time at the beginning of the run. Bascially, if the
+ modification time is earlier than this, then it is a leftover
+ from a previous run. However, a naive use of the criterion can,
+ among other things, run afoul of the granularity of how file
+ times are stored in some file systems, which means it is possi-
+ ble that the filesystem's reported time for a file might be a
+ second or more earlier than the actual modification time, the
+ exact difference being quite random.
- This regular expression matches a line that starts with 'No
- file', then has one or more white space characters, then any
- number of characters forming the filename, then possible white
- space, and finally the end of the line. (See documentation on
- Perl regular expressions for details.)
+ The variable $filetime_causality_threshold allows an appopriate
+ sloppiness in latexmk's use of file modification time. It can
+ be quite generous; it should merely be less than the time scale
+ on which a human user makes changes to source files for a docu-
+ ment (or to configuration files, etc).
$fls_uses_out_dir [0]
@@ -3346,31 +3424,31 @@
'out', 'toc', 'blg', 'ilg', 'log', 'xdv' )]
This contains a list of extensions for files that are generated
- during processing, and that should be deleted during a main
- clean up operation, as invoked by the command line option -c.
- (The use of -C or -gg gives this clean up and more.)
- The default values are extensions for standard files generated
- by *latex, bibtex, and the like. (Note that the clean up also
- deletes the fdb_latexmk file, but that's separately coded into
- latexmk, currently.)
- After initialization of latexmk and the processing of its com-
- mand line, the items in clean_ext are appended to @gener-
- ated_exts. So these two variables have the same meaning
+ 24 December 2023 52
- 6 November 2023 51
+LATEXMK(1) General Commands Manual LATEXMK(1)
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ during processing, and that should be deleted during a main
+ clean up operation, as invoked by the command line option -c.
+ (The use of -C or -gg gives this clean up and more.)
+ The default values are extensions for standard files generated
+ by *latex, bibtex, and the like. (Note that the clean up also
+ deletes the fdb_latexmk file, but that's separately coded into
+ latexmk, currently.)
- (contrary to older versions of latexmk).
+ After initialization of latexmk and the processing of its com-
+ mand line, the items in clean_ext are appended to @gener-
+ ated_exts. So these two variables have the same meaning (con-
+ trary to older versions of latexmk).
The items in @generated_exts are normally extensions of files,
whose base name is the same as the main tex file. But it is
@@ -3403,6 +3481,7 @@
If nonzero, process files regardless of timestamps, and is then
equivalent to the -g option.
+
%hash_calc_ignore_pattern
!!!This variable is for experts only!!!
@@ -3411,6 +3490,18 @@
changed. But consider for example a latex package that causes
an encapsulated postscript file (an "eps" file) to be made that
is to be read in on the next run. The file contains a comment
+
+
+
+ 24 December 2023 53
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
line giving its creation date and time. On the next run the
time changes, latex sees that the eps file has changed, and
therefore reruns latex. This causes an infinite loop, that is
@@ -3424,18 +3515,6 @@
This creates a rule for files with extension .eps about lines to
ignore. The left-hand side is a Perl idiom for setting an item
-
-
-
- 6 November 2023 52
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
in a hash. Note that the file extension is specified without a
period. The value, on the right-hand side, is a string contain-
ing a regular expression. (See documentation on Perl for how
@@ -3465,151 +3544,175 @@
delete $hash_calc_ignore_pattern{'eps'};
+ $hilatex ["hilatex %O %S"]
+ specifies the command line for the hilatex program.
+
+
+ $hnt_mode [0]
+ Whether to generate a hnt version of the document by use of hi-
+ latex. Can be turned on by the use of the -hnt option.
+
+
$jobname [""]
- This specifies the jobname, i.e., the basename that is used for
- generated files (.aux, .log, .dvi, .ps, .pdf, etc). If this
- variable is a null string, then the basename is the basename of
- the main tex file. (At present, the string in $jobname should
- not contain spaces.)
+ This specifies the jobname, i.e., the basename that is used for
- 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
- 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
- cases, you could set
- $jobname = "%A-$^O";
- in an initialization file. (Here $^O is a variable provided by
- perl that contains perl's name for the operating system.)
+ 24 December 2023 54
- Suppose you had .tex files test1.tex and test2.tex. Then when
- you run
- latexmk -pdf *.tex
- 6 November 2023 53
+LATEXMK(1) General Commands Manual LATEXMK(1)
+ generated files (.aux, .log, .dvi, .ps, .pdf, etc). If this
+ variable is a null string, then the basename is the basename of
+ the main tex file. (At present, the string in $jobname should
+ 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
+ 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
+ cases, you could set
+ $jobname = "%A-$^O";
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ in an initialization file. (Here $^O is a variable provided by
+ perl that contains perl's name for the operating system.)
+ Suppose you had .tex files test1.tex and test2.tex. Then when
+ you run
- both files will be compiled. The .aux, .log, and .pdf files
- will have basenames test1-MSWin32 ante test2-MSWin32 on a MS-
+ latexmk -pdf *.tex
+
+ 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,
and a variety of similar cases on linux systems.
$kpsewhich ["kpsewhich %S"]
- The program called to locate a source file when the name alone
- is not sufficient. Most filenames used by latexmk have suffi-
+ The program called to locate a source file when the name alone
+ is not sufficient. Most filenames used by latexmk have suffi-
cient path information to be found directly. But sometimes, no-
tably when a .bib or a .bst file is found from the log file of a
- bibtex or biber run, only the base name of the file is known,
+ bibtex or biber run, only the base name of the file is known,
but not its path. The program specified by $kpsewhich is used to
find it.
- (For advanced users: Because of the different way in which la-
+ (For advanced users: Because of the different way in which la-
texmk uses the command specified in $kpsewhich, some of the pos-
sibilities listed in the FORMAT OF COMMAND SPECIFICATIONS do not
- apply. The internal and start keywords are not available. A
+ apply. The internal and start keywords are not available. A
simple command specification with possible options and then "%S"
- is all that is guaranteed to work. Note that for other com-
+ is all that is guaranteed to work. Note that for other com-
mands, "%S" is substituted by a single source file. In contrast,
for $kpsewhich, "%S" may be substituted by a long list of space-
- separated filenames, each of which is quoted. The result on
+ separated filenames, each of which is quoted. The result on
STDOUT of running the command is then piped to latexmk.)
- See also the @BIBINPUTS variable for another way that latexmk
+ See also the @BIBINPUTS variable for another way that latexmk
also uses to try to locate files; it applies only in the case of
.bib files.
+
+
+
+
+ 24 December 2023 55
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
$kpsewhich_show [0]
- Whether to show diagnostics about invocations of kpsewhich: the
- command line use to invoke it and the results. These diagnos-
- tics are shown if $kpsewhich_show is non-zero or if diagnostics
- mode is on. (But in the second case, lots of other diagnostics
- are also shown.) Without these diagnostics there is nothing
- visible in latexmk's screen output about invocations of kpse-
+ Whether to show diagnostics about invocations of kpsewhich: the
+ command line use to invoke it and the results. These diagnos-
+ tics are shown if $kpsewhich_show is non-zero or if diagnostics
+ mode is on. (But in the second case, lots of other diagnostics
+ are also shown.) Without these diagnostics there is nothing
+ visible in latexmk's screen output about invocations of kpse-
which.
+
$landscape_mode [0]
If nonzero, run in landscape mode, using the landscape mode pre-
- viewers and dvi to postscript converters. Equivalent to the -l
+ viewers and dvi to postscript converters. Equivalent to the -l
option. Normally not needed with current previewers.
+
$latex ["latex %O %S"]
- Specifies the command line for the LaTeX processing program.
- Note that as with other programs, you can use this variable not
- just to change the name of the program used, but also specify
+ Specifies the command line for the LaTeX processing program.
+ Note that as with other programs, you can use this variable not
+ just to change the name of the program used, but also specify
options to the program. E.g.,
$latex = "latex --src-specials %O %S";
- To do a coordinated setting of all of $dvilualatex, $latex,
- $pdflatex, $lualatex, and $xelatex, see the section "Advanced
+ To do a coordinated setting of all of $dvilualatex, $hilatex,
+ $latex, $pdflatex, $lualatex, and $xelatex, see the section "Ad-
+ vanced Configuration".
+ %latex_input_extensions
+ This variable specifies the extensions tried by latexmk when it
+ finds that a LaTeX run resulted in an error that a file has not
+ been found, and the file is given without an extension. This
+ typically happens when LaTeX commands of the form \input{file}
+ or \includegraphics{figure}, when the relevant source file does
+ not exist.
- 6 November 2023 54
+ In this situation, latexmk searches for custom dependencies to
+ make the missing file(s), but restricts it to the extensions
+ specified by the variable %latex_input_extensions. The default
+ extensions are 'tex' and 'eps'.
+ (For Perl experts: %latex_input_extensions is a hash whose keys
+ are the extensions. The values are irrelevant.) Two subrou-
+ tines are provided for manipulating this and the related vari-
+ able %pdflatex_input_extensions, add_input_ext and remove_in-
+ put_ext. They are used as in the following examples are possi-
+ ble lines in an initialization file:
+ remove_input_ext( 'latex', 'tex' );
+ removes the extension 'tex' from latex_input_extensions
+ add_input_ext( 'latex', 'asdf' );
-LATEXMK(1) General Commands Manual LATEXMK(1)
- Configuration".
+ 24 December 2023 56
- %latex_input_extensions
- This variable specifies the extensions tried by latexmk when it
- finds that a LaTeX run resulted in an error that a file has not
- been found, and the file is given without an extension. This
- typically happens when LaTeX commands of the form \input{file}
- or \includegraphics{figure}, when the relevant source file does
- not exist.
- In this situation, latexmk searches for custom dependencies to
- make the missing file(s), but restricts it to the extensions
- specified by the variable %latex_input_extensions. The default
- extensions are 'tex' and 'eps'.
- (For Perl experts: %latex_input_extensions is a hash whose keys
- are the extensions. The values are irrelevant.) Two subrou-
- tines are provided for manipulating this and the related vari-
- able %pdflatex_input_extensions, add_input_ext and remove_in-
- put_ext. They are used as in the following examples are possi-
- ble lines in an initialization file:
- remove_input_ext( 'latex', 'tex' );
+LATEXMK(1) General Commands Manual LATEXMK(1)
- removes the extension 'tex' from latex_input_extensions
- add_input_ext( 'latex', 'asdf' );
-
- add the extension 'asdf to latex_input_extensions. (Naturally
+ add the extension 'asdf to latex_input_extensions. (Naturally
with such an extension, you should have made an appropriate cus-
tom dependency for latexmk, and should also have done the appro-
- priate programming in the LaTeX source file to enable the file
- to be read. The standard extensions are handled by LaTeX and
+ priate programming in the LaTeX source file to enable the file
+ to be read. The standard extensions are handled by LaTeX and
its graphics/graphicx packages.)
$latex_silent_switch ["-interaction=batchmode"]
- Switch(es) for the LaTeX processing program when silent mode is
+ Switch(es) for the LaTeX processing program when silent mode is
on.
- If you use MikTeX, you may prefer the results if you configure
- the options to include -c-style-errors, e.g., by the following
+ If you use MikTeX, you may prefer the results if you configure
+ the options to include -c-style-errors, e.g., by the following
line in an initialization file
$latex_silent_switch = "-interaction=batchmode -c-style-er-
@@ -3619,31 +3722,19 @@
$lpr ["lpr %O %S" under UNIX/Linux, "NONE lpr" under MS-Windows]
The command to print postscript files.
- Under MS-Windows (unlike UNIX/Linux), there is no standard pro-
+ Under MS-Windows (unlike UNIX/Linux), there is no standard pro-
gram for printing files. But there are ways you can do it. For
example, if you have gsview installed, you could use it with the
-
-
-
- 6 November 2023 55
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
option "/p":
$lpr = '"c:/Program Files/Ghostgum/gsview/gsview32.exe" /p';
- If gsview is installed in a different directory, you will need
- to make the appropriate change. Note the combination of single
- and double quotes around the name. The single quotes specify
- that this is a string to be assigned to the configuration vari-
- able $lpr. The double quotes are part of the string passed to
- the operating system to get the command obeyed; this is neces-
+ If gsview is installed in a different directory, you will need
+ to make the appropriate change. Note the combination of single
+ and double quotes around the name. The single quotes specify
+ that this is a string to be assigned to the configuration vari-
+ able $lpr. The double quotes are part of the string passed to
+ the operating system to get the command obeyed; this is neces-
sary because one part of the command name ("Program Files") con-
tains a space which would otherwise be misinterpreted.
@@ -3653,60 +3744,59 @@
$lpr_pdf ["NONE lpr_pdf"]
The printing program to print pdf files.
- Under MS-Windows you could set this to use gsview, if it is in-
+ Under MS-Windows you could set this to use gsview, if it is in-
stalled, e.g.,
$lpr = '"c:/Program Files/Ghostgum/gsview/gsview32.exe" /p';
- If gsview is installed in a different directory, you will need
- to make the appropriate change. Note the double quotes around
+ If gsview is installed in a different directory, you will need
+ to make the appropriate change. Note the double quotes around
the name: this is necessary because one part of the command name
("Program Files") contains a space which would otherwise be mis-
interpreted.
- $lualatex ["lualatex %O %S"]
- Specifies the command line for the LaTeX processing program that
- is to be used when the lualatex program is called for (e.g., by
- the option -lualatex.
- To do a coordinated setting of all of $dvilualatex, $latex,
- $pdflatex, $lualatex, and $xelatex, see the section "Advanced
- Configuration".
+ 24 December 2023 57
- %lualatex_input_extensions
- This variable specifies the extensions tried by latexmk when it
- finds that a lualatex run resulted in an error that a file has
- not been found, and the file is given without an extension.
- This typically happens when LaTeX commands of the form \in-
- put{file} or \includegraphics{figure}, when the relevant source
- file does not exist.
- In this situation, latexmk searches for custom dependencies to
- make the missing file(s), but restricts it to the extensions
- specified by the variable %pdflatex_input_extensions. The de-
- fault extensions are 'tex', 'pdf', 'jpg, and 'png'.
- See details of the %latex_input_extensions for other information
+LATEXMK(1) General Commands Manual LATEXMK(1)
- 6 November 2023 56
+ $lualatex ["lualatex %O %S"]
+ Specifies the command line for the LaTeX processing program that
+ is to be used when the lualatex program is called for (e.g., by
+ the option -lualatex.
+ To do a coordinated setting of all of $dvilualatex, $hilatex,
+ $latex, $pdflatex, $lualatex, and $xelatex, see the section "Ad-
+ vanced Configuration".
+ %lualatex_input_extensions
+ This variable specifies the extensions tried by latexmk when it
+ finds that a lualatex run resulted in an error that a file has
+ not been found, and the file is given without an extension.
+ This typically happens when LaTeX commands of the form \in-
+ put{file} or \includegraphics{figure}, when the relevant source
+ file does not exist.
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ In this situation, latexmk searches for custom dependencies to
+ make the missing file(s), but restricts it to the extensions
+ specified by the variable %pdflatex_input_extensions. The de-
+ fault extensions are 'tex', 'pdf', 'jpg, and 'png'.
-
+ See details of the %latex_input_extensions for other information
that equally applies to %lualatex_input_extensions.
$lualatex_silent_switch ["-interaction=batchmode"]
- Switch(es) for the lualatex program (specified in the variable
+ Switch(es) for the lualatex program (specified in the variable
$lualatex) when silent mode is on.
- See details of the $latex_silent_switch for other information
+ See details of the $latex_silent_switch for other information
that equally applies to $lualatex_silent_switch.
$make ["make"]
@@ -3716,105 +3806,114 @@
The index processing program.
$makeindex_fudge [0]
- When using makeindex, whether to change directory to $aux_dir
- before running makeindex. Set to 1 if $aux_dir is not an ex-
- plicit subdirectory of current directory, otherwise makeindex
+ When using makeindex, whether to change directory to $aux_dir
+ before running makeindex. Set to 1 if $aux_dir is not an ex-
+ plicit subdirectory of current directory, otherwise makeindex
will refuse to write its output and log files, for security rea-
sons.
$makeindex_silent_switch ["-q"]
- Switch(es) for the index processing program when silent mode is
+ Switch(es) for the index processing program when silent mode is
on.
$max_repeat [5]
- The maximum number of times latexmk will run *latex before de-
- ciding that there may be an infinite loop and that it needs to
- bail out, rather than rerunning *latex again to resolve cross-
- references, etc. The default value covers all normal cases.
+ The maximum number of times latexmk will run *latex before de-
+ ciding that there may be an infinite loop and that it needs to
+ bail out, rather than rerunning *latex again to resolve cross-
- (Note that the "etc" covers a lot of cases where one run of *la-
- tex generates files to be read in on a later run.)
- $MSWin_back_slash [1]
- This configuration variable only has an effect when latexmk is
- running under MS-Windows. 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 almost all programs and for almost all filenames under MS-
- Windows, both "\" and "/" are acceptable as the directory sepa-
- rator 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 latexmk makes the sub-
- stitution from "/" to "\", by default.
+ 24 December 2023 58
- However there are also programs on MS-Windows for which a back
- slash "\" is interpreted differently than as a directory
- 6 November 2023 57
+LATEXMK(1) General Commands Manual LATEXMK(1)
+ references, etc. The default value covers all normal cases.
+ (Note that the "etc" covers a lot of cases where one run of *la-
+ tex generates files to be read in on a later run.)
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ $MSWin_back_slash [1]
+ This configuration variable only has an effect when latexmk is
+ 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 almost all programs and for almost all filenames under MS-
+ Windows, both "\" and "/" are acceptable as the directory sepa-
+ rator 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 latexmk makes the sub-
+ stitution from "/" to "\", by default.
- 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 $MSWin_back_slash
+ 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
+ This variable applies to latexmk only in continuous-preview
mode. If $new_viewer_always is 0, latexmk will check for a pre-
- viously running previewer on the same file, and if one is run-
- ning will not start a new one. If $new_viewer_always is non-
- zero, this check will be skipped, and latexmk will behave as if
+ viously running previewer on the same file, and if one is run-
+ ning will not start a new one. If $new_viewer_always is non-
+ zero, this check will be skipped, and latexmk will behave as if
no viewer is running.
$out_dir [""]
If non-blank, this variable specifies the output directory.
- This is the directory in which final output files are written
- (dvi, ps, pdf, synctex, synctex.gz). In addition, if the aux
- directory equals the output directory, as is the case by de-
- fault, then other generated files are in effect written to the
+ This is the directory in which final output files are written
+ (dvi, ps, pdf, synctex, synctex.gz). In addition, if the aux
+ directory equals the output directory, as is the case by de-
+ fault, then other generated files are in effect written to the
output directory.
If $out_dir is blank, the output directory is the current direc-
- tory at the invocation of *latex; this is equivalent to setting
+ tory at the invocation of *latex; this is equivalent to setting
$out_dir to '.'.
- See the section AUXILIARY AND OUTPUT DIRECTORIES for more de-
+ See the section AUXILIARY AND OUTPUT DIRECTORIES for more de-
tails.
+ 24 December 2023 59
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
$pdf_mode [0]
- If zero, do NOT generate a pdf version of the document. If
- equal to 1, generate a pdf version of the document using pdfla-
- tex, using the command specified by the $pdflatex variable. If
- equal to 2, generate a pdf version of the document from the ps
- file, by using the command specified by the $ps2pdf variable.
- If equal to 3, generate a pdf version of the document from the
- dvi file, by using the command specified by the $dvipdf vari-
+ If zero, do NOT generate a pdf version of the document. If
+ equal to 1, generate a pdf version of the document using pdfla-
+ tex, using the command specified by the $pdflatex variable. If
+ equal to 2, generate a pdf version of the document from the ps
+ file, by using the command specified by the $ps2pdf variable.
+ If equal to 3, generate a pdf version of the document from the
+ dvi file, by using the command specified by the $dvipdf vari-
able. If equal to 4, generate a pdf version of the document us-
ing lualatex, using the command specified by the $lualatex vari-
- able. If equal to 5, generate a pdf version (and an xdv ver-
- sion) of the document using xelatex, using the commands speci-
+ able. If equal to 5, generate a pdf version (and an xdv ver-
+ sion) of the document using xelatex, using the commands speci-
fied by the $xelatex and xdvipdfmx variables.
- In $pdf_mode=2, it is ensured that .dvi and .ps files are also
- made. In $pdf_mode=3, it is ensured that a .dvi file is also
+ In $pdf_mode=2, it is ensured that .dvi and .ps files are also
+ made. In $pdf_mode=3, it is ensured that a .dvi file is also
made. But this may be overridden by the document.
$pdflatex ["pdflatex %O %S"]
@@ -3821,170 +3920,157 @@
Specifies the command line for the LaTeX processing program in a
version that makes a pdf file instead of a dvi file.
-
-
- 6 November 2023 58
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
An example use of this variable is to add certain options to the
command line for the program, e.g.,
$pdflatex = "pdflatex --shell-escape %O %S";
- (In some earlier versions of latexmk, you needed to use an as-
- signment to $pdflatex to allow the use of lualatex or xelatex
+ (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-
- ables for the use of lualatex or xelatex. See $lualatex and
+ ables for the use of lualatex or xelatex. See $lualatex and
$xelatex.)
- To do a coordinated setting of all of $dvilualatex, $latex,
- $pdflatex, $lualatex, and $xelatex, see the section "Advanced
- Configuration".
+ To do a coordinated setting of all of $dvilualatex, $hilatex,
+ $latex, $pdflatex, $lualatex, and $xelatex, see the section "Ad-
+ vanced Configuration".
%pdflatex_input_extensions
- This variable specifies the extensions tried by latexmk when it
- finds that a pdflatex run resulted in an error that a file has
- not been found, and the file is given without an extension.
- This typically happens when LaTeX commands of the form \in-
- put{file} or \includegraphics{figure}, when the relevant source
+ This variable specifies the extensions tried by latexmk when it
+ finds that a pdflatex run resulted in an error that a file has
+ not been found, and the file is given without an extension.
+ This typically happens when LaTeX commands of the form \in-
+ put{file} or \includegraphics{figure}, when the relevant source
file does not exist.
- In this situation, latexmk searches for custom dependencies to
- make the missing file(s), but restricts it to the extensions
- specified by the variable %pdflatex_input_extensions. The de-
+ In this situation, latexmk searches for custom dependencies to
+ make the missing file(s), but restricts it to the extensions
+ specified by the variable %pdflatex_input_extensions. The de-
fault extensions are 'tex', 'pdf', 'jpg, and 'png'.
See details of the %latex_input_extensions for other information
that equally applies to %pdflatex_input_extensions.
- $pdflatex_silent_switch ["-interaction=batchmode"]
- Switch(es) for the pdflatex program (specified in the variable
- $pdflatex) when silent mode is on.
- See details of the $latex_silent_switch for other information
- that equally applies to $pdflatex_silent_switch.
- $pdf_previewer ["start acroread %O %S"]
- The command to invoke a pdf-previewer.
- On MS-Windows, the default is changed to "cmd /c start """; un-
- der more recent versions of Windows, this will cause to be run
- whatever command the system has associated with .pdf files. But
- this may be undesirable if this association is to acroread --
- see the notes in the explanation of the -pvc option.]
+ 24 December 2023 60
- On OS-X the default is changed to "open %S", which results in
- OS-X starting up (and detaching) the viewer associated with the
- file. By default, for pdf files this association is to OS-X's
- preview, which is quite satisfactory.
- WARNING: Problem under MS-Windows: if acroread is used as the
- 6 November 2023 59
+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.
+ See details of the $latex_silent_switch for other information
+ that equally applies to $pdflatex_silent_switch.
+ $pdf_previewer ["start acroread %O %S"]
+ The command to invoke a pdf-previewer.
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ On MS-Windows, the default is changed to "cmd /c start """; un-
+ der more recent versions of Windows, this will cause to be run
+ whatever command the system has associated with .pdf files. But
+ this may be undesirable if this association is to acroread --
+ see the notes in the explanation of the -pvc option.]
+ On OS-X the default is changed to "open %S", which results in
+ OS-X starting up (and detaching) the viewer associated with the
+ file. By default, for pdf files this association is to OS-X's
+ preview, which is quite satisfactory.
- pdf previewer, and it is actually viewing a pdf file, the pdf
- file cannot be updated. Thus makes acroread a bad choice of
- previewer if you use latexmk's previous-continuous mode (option
+ WARNING: Problem under MS-Windows: if acroread is used as the
+ pdf previewer, and it is actually viewing a pdf file, the pdf
+ file cannot be updated. Thus makes acroread a bad choice of
+ previewer if you use latexmk's previous-continuous mode (option
-pvc) under MS-windows. This problem does not occur if, for ex-
ample, SumatraPDF or gsview is used to view pdf files.
- Important note: Normally you will want to have a previewer run
+ Important note: Normally you will want to have a previewer run
detached, so that latexmk doesn't wait for the previewer to ter-
- minate before continuing its work. So normally you should pre-
- fix the command by "start ", which flags to latexmk that it
- should do the detaching of the previewer itself (by whatever
- method is appropriate to the operating system). But sometimes
+ minate before continuing its work. So normally you should pre-
+ fix the command by "start ", which flags to latexmk that it
+ should do the detaching of the previewer itself (by whatever
+ method is appropriate to the operating system). But sometimes
letting latexmk do the detaching is not appropriate (for a vari-
- ety of non-trivial reasons), so you should put the "start " bit
+ ety of non-trivial reasons), so you should put the "start " bit
in yourself, whenever it is needed.
$pdf_update_command [""]
- When the pdf previewer is set to be updated by running a com-
- mand, this is the command that is run. See the information for
+ When the pdf previewer is set to be updated by running a com-
+ mand, this is the command that is run. See the information for
the variable $pdf_update_method.
$pdf_update_method [1 under UNIX, 3 under MS-Windows]
- How the pdf viewer updates its display when the pdf file has
- changed. See the information on the variable $dvi_update_method
+ How the pdf viewer updates its display when the pdf file has
+ changed. See the information on the variable $dvi_update_method
for the codes. (Note that information needs be changed slightly
- so that for the value 4, to run a command to do the update, the
- command is specified by the variable $pdf_update_command, and
- for the value 2, to specify update by signal, the signal is
+ so that for the value 4, to run a command to do the update, the
+ command is specified by the variable $pdf_update_command, and
+ for the value 2, to specify update by signal, the signal is
specified by $pdf_update_signal.)
Note that acroread under MS-Windows (but not UNIX) locks the pdf
file, so the default value is then 3.
- Arranging to use a command to get a previewer explicitly updated
- requires three variables to be set. For example:
- $pdf_previewer = "start xpdf -remote %R %O %S";
- $pdf_update_method = 4;
- $pdf_update_command = "xpdf -remote %R -reload";
- The first setting arranges for the xpdf program to be used in
- its "remote server mode", with the server name specified as the
- rootname of the TeX file. The second setting arranges for up-
- dating to be done in response to a command, and the third set-
- ting sets the update command.
+ 24 December 2023 61
- $pdf_update_signal [Under UNIX: SIGHUP, which is a system-dependent
- value]
- The number of the signal that is sent to the pdf viewer when it
- is updated by sending a signal -- see the information on the
- variable $pdf_update_method. The default value is the one ap-
- propriate for gv on a UNIX system.
+LATEXMK(1) General Commands Manual LATEXMK(1)
- 6 November 2023 60
+ Arranging to use a command to get a previewer explicitly updated
+ requires three variables to be set. For example:
+ $pdf_previewer = "start xpdf -remote %R %O %S";
+ $pdf_update_method = 4;
+ $pdf_update_command = "xpdf -remote %R -reload";
+ The first setting arranges for the xpdf program to be used in
+ its "remote server mode", with the server name specified as the
+ rootname of the TeX file. The second setting arranges for up-
+ dating to be done in response to a command, and the third set-
+ ting sets the update command.
+ $pdf_update_signal [Under UNIX: SIGHUP, which is a system-dependent
+ value]
+ The number of the signal that is sent to the pdf viewer when it
+ is updated by sending a signal -- see the information on the
+ variable $pdf_update_method. The default value is the one ap-
+ propriate for gv on a UNIX system.
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
$pid_position[1 under UNIX, -1 under MS-Windows]
- The variable $pid_position is used to specify which word in
- lines of the output from $pscmd corresponds to the process ID.
- The first word in the line is numbered 0. The default value of
+ The variable $pid_position is used to specify which word in
+ lines of the output from $pscmd corresponds to the process ID.
+ The first word in the line is numbered 0. The default value of
1 (2nd word in line) is correct for Solaris 2.6, Linux, and OS-X
with their default settings of $pscmd.
- Setting the variable to -1 is used to indicate that $pscmd is
+ Setting the variable to -1 is used to indicate that $pscmd is
not to be used.
$postscript_mode [0]
- If nonzero, generate a postscript version of the document.
+ If nonzero, generate a postscript version of the document.
Equivalent to the -ps option.
- If some other request is made for which a postscript file is
+ If some other request is made for which a postscript file is
needed, then $postscript_mode will be set to 1.
$pre_tex_code ['']
- Sets TeX code to be executed before inputting the source file.
- This works if the relevant one of $latex, etc contains a suit-
+ Sets TeX code to be executed before inputting the source file.
+ This works if the relevant one of $latex, etc contains a suit-
able command line with a %P or %U substitution. For example you
could do
@@ -3991,7 +4077,7 @@
$latex = 'latex %O %P';
$pre_tex_code = '\AtBeginDocument{An initial message\par}';
- To set all of $latex, $pdflatex, $lualatex, and $xelatex you
+ To set all of $latex, $pdflatex, $lualatex, and $xelatex you
could use the subroutine alt_tex_cmds:
&alt_tex_cmds;
@@ -3999,55 +4085,53 @@
+
+
+ 24 December 2023 62
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
$preview_continuous_mode [0]
- If nonzero, run a previewer to view the document, and continue
+ If nonzero, run a previewer to view the document, and continue
running latexmk to keep .dvi up-to-date. Equivalent to the -pvc
- option. Which previewer is run depends on the other settings,
+ option. Which previewer is run depends on the other settings,
see the command line options -view=, and the variable $view.
$preview_mode [0]
If nonzero, run a previewer to preview the document. Equivalent
- to the -pv option. Which previewer is run depends on the other
- settings, see the command line options -view=, and the variable
+ to the -pv option. Which previewer is run depends on the other
+ settings, see the command line options -view=, and the variable
$view.
$printout_mode [0]
- If nonzero, print the document using the command specified in
+ If nonzero, print the document using the command specified in
the $lpr variable. Equivalent to the -p option. This is recom-
- mended not to be set from an RC file, otherwise you could waste
+ mended not to be set from an RC file, otherwise you could waste
lots of paper.
-
-
-
-
- 6 November 2023 61
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
$print_type = ["auto"]
- Type of file to printout: possibilities are "auto", "dvi",
+ Type of file to printout: possibilities are "auto", "dvi",
"none", "pdf", or "ps". See the option -print= for the meaning
of the "auto" value.
$pscmd Command used to get all the processes currently run by the user.
- The -pvc option uses the command specified by the variable
- $pscmd to determine if there is an already running previewer,
- and to find the process ID (needed if latexmk needs to signal
+ The -pvc option uses the command specified by the variable
+ $pscmd to determine if there is an already running previewer,
+ and to find the process ID (needed if latexmk needs to signal
the previewer about file changes).
Each line of the output of this command is assumed to correspond
- to one process. See the $pid_position variable for how the
+ to one process. See the $pid_position variable for how the
process number is determined.
- The default for pscmd is "NONE" under MS-Windows and cygwin
- (i.e., the command is not used), "ps -ww -u $ENV{USER}" under
- OS-X, and "ps -f -u $ENV{USER}" under other operating systems
+ The default for pscmd is "NONE" under MS-Windows and cygwin
+ (i.e., the command is not used), "ps -ww -u $ENV{USER}" under
+ OS-X, and "ps -f -u $ENV{USER}" under other operating systems
(including Linux). In these specifications "$ENV{USER}" is sub-
stituted by the username.
@@ -4056,74 +4140,75 @@
$ps_filter [empty]
The postscript file filter to be run on the newly produced post-
- script file before other processing. Equivalent to specifying
+ script file before other processing. Equivalent to specifying
the -pF option.
$ps_previewer ["start gv %O %S", but start %O %S under MS-Windows]
- The command to invoke a ps-previewer. (The default under MS-
+ The command to invoke a ps-previewer. (The default under MS-
Windows will cause to be run whatever command the system has as-
sociated with .ps files.)
- Note that gv could be used with the -watch option updates its
- display whenever the postscript file changes, whereas ghostview
- does not. However, different versions of gv have slightly dif-
- ferent ways of writing this option. You can configure this
- variable appropriately.
+ Note that gv could be used with the -watch option updates its
+ display whenever the postscript file changes, whereas ghostview
- WARNING: Linux systems may have installed one (or more) versions
- of gv under different names, e.g., ggv, kghostview, etc, but
- perhaps not one actually called gv.
- Important note: Normally you will want to have a previewer run
- detached, so that latexmk doesn't wait for the previewer to ter-
- minate before continuing its work. So normally you should pre-
- fix the command by "start ", which flags to latexmk that it
- should do the detaching of the previewer itself (by whatever
- method is appropriate to the operating system). But sometimes
- letting latexmk do the detaching is not appropriate (for a vari-
- ety of non-trivial reasons), so you should put the "start " bit
- in yourself, whenever it is needed.
+ 24 December 2023 63
- 6 November 2023 62
+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.
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ WARNING: Linux systems may have installed one (or more) versions
+ of gv under different names, e.g., ggv, kghostview, etc, but
+ perhaps not one actually called gv.
+ Important note: Normally you will want to have a previewer run
+ detached, so that latexmk doesn't wait for the previewer to ter-
+ minate before continuing its work. So normally you should pre-
+ fix the command by "start ", which flags to latexmk that it
+ should do the detaching of the previewer itself (by whatever
+ method is appropriate to the operating system). But sometimes
+ letting latexmk do the detaching is not appropriate (for a vari-
+ ety of non-trivial reasons), so you should put the "start " bit
+ in yourself, whenever it is needed.
- $ps_previewer_landscape ["start gv -swap %O %S", but start %O %S under
+
+ $ps_previewer_landscape ["start gv -swap %O %S", but start %O %S under
MS-Windows]
The command to invoke a ps-previewer in landscape mode.
$ps_update_command [""]
- When the postscript previewer is set to be updated by running a
- command, this is the command that is run. See the information
+ When the postscript previewer is set to be updated by running a
+ command, this is the command that is run. See the information
for the variable $ps_update_method.
$ps_update_method [0 under UNIX, 1 under MS-Windows]
- How the postscript viewer updates its display when the .ps file
- has changed. See the information on the variable $dvi_up-
- date_method for the codes. (Note that information needs be
+ How the postscript viewer updates its display when the .ps file
+ has changed. See the information on the variable $dvi_up-
+ date_method for the codes. (Note that information needs be
changed slightly so that for the value 4, to run a command to do
- the update, the command is specified by the variable $ps_up-
- date_command, and for the value 2, to specify update by signal,
+ the update, the command is specified by the variable $ps_up-
+ date_command, and for the value 2, to specify update by signal,
the signal is specified by $ps_update_signal.)
- $ps_update_signal [Under UNIX: SIGHUP, which is a system-dependent
+ $ps_update_signal [Under UNIX: SIGHUP, which is a system-dependent
value]
- The number of the signal that is sent to the pdf viewer when it
- is updated by sending a signal -- see $ps_update_method. The
+ The number of the signal that is sent to the pdf viewer when it
+ is updated by sending a signal -- see $ps_update_method. The
default value is the one appropriate for gv on a UNIX system.
$pvc_timeout [0]
- If this variable is nonzero, there will be a timeout in pvc
- mode after a period of inactivity. Inactivity means a period
- when latexmk has detected no file changes and hence has not
+ If this variable is nonzero, there will be a timeout in pvc
+ mode after a period of inactivity. Inactivity means a period
+ when latexmk has detected no file changes and hence has not
taken any actions like compiling the document. The period of in-
activity is in the variable $pvc_timeout_mins.
@@ -4132,102 +4217,102 @@
The period of inactivity, in minutes, after which pvc mode times
out. This is used if $pvc_timeout is nonzero.
- $pvc_view_file_via_temporary [1]
- The same as $always_view_file_via_temporary, except that it only
- applies in preview-continuous mode (-pvc option).
- $quote_filenames [1]
- This specifies whether substitutions for placeholders in command
- specifications (as in $pdflatex) are surrounded by double
- quotes. If this variable is 1 (or any other value Perl regards
- as true), then quoting is done. Otherwise quoting is omitted.
- The quoting method used by latexmk is tested to work correctly
- under UNIX systems (including Linux and Mac OS-X) and under MS-
- Windows. It allows the use of filenames containing special
- characters, notably spaces. (But note that many versions of
- *latex cannot correctly deal with TeX files whose names contain
- spaces. Latexmk's quoting only ensures that such filenames are
- correctly treated by the operating system in passing arguments
- to programs.)
+ 24 December 2023 64
- 6 November 2023 63
+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).
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ $quote_filenames [1]
+ This specifies whether substitutions for placeholders in command
+ specifications (as in $pdflatex) are surrounded by double
+ quotes. If this variable is 1 (or any other value Perl regards
+ as true), then quoting is done. Otherwise quoting is omitted.
+ The quoting method used by latexmk is tested to work correctly
+ under UNIX systems (including Linux and Mac OS-X) and under MS-
+ Windows. It allows the use of filenames containing special
+ characters, notably spaces. (But note that many versions of
+ *latex cannot correctly deal with TeX files whose names contain
+ spaces. Latexmk's quoting only ensures that such filenames are
+ correctly treated by the operating system in passing arguments
+ to programs.)
$rc_report [1]
- After initialization, whether to give a list of the RC files
+ After initialization, whether to give a list of the RC files
read.
$recorder [1]
- Whether to use the -recorder option to *latex. Use of this op-
- tion results in a file of extension .fls containing a list of
- the files that these programs have read and written. Latexmk
+ Whether to use the -recorder option to *latex. Use of this op-
+ tion results in a file of extension .fls containing a list of
+ the files that these programs have read and written. Latexmk
will then use this file to improve its detection of source files
and generated files after a run of *latex.
- It is generally recommended to use this option (or to configure
- the $recorder variable to be on.) But it only works if *latex
- supports the -recorder option, which is true for most current
+ It is generally recommended to use this option (or to configure
+ the $recorder variable to be on.) But it only works if *latex
+ supports the -recorder option, which is true for most current
implementations
- Note about the name of the .fls file: Most implementations of
- *latex produce an .fls file with the same basename as the main
+ Note about the name of the .fls file: Most implementations of
+ *latex produce an .fls file with the same basename as the main
document's LaTeX, e.g., for Document.tex, the .fls file is Docu-
- ment.fls. However, some implementations instead produce files
+ ment.fls. However, some implementations instead produce files
named for the program, i.e., latex.fls or pdflatex.fls. In this
- second case, latexmk copies the latex.fls or pdflatex.fls to a
- file with the basename of the main LaTeX document, e.g., Docu-
+ second case, latexmk copies the latex.fls or pdflatex.fls to a
+ file with the basename of the main LaTeX document, e.g., Docu-
ment.fls.
$search_path_separator [See below for default]
The character separating paths in the environment variables TEX-
- INPUTS, BIBINPUTS, and BSTINPUTS. This variable is mainly used
- by latexmk when the -outdir, -output-directory, -auxdir, and/or
- -aux-directory options are used. In that case latexmk needs to
+ INPUTS, BIBINPUTS, and BSTINPUTS. This variable is mainly used
+ by latexmk when the -outdir, -output-directory, -auxdir, and/or
+ -aux-directory options are used. In that case latexmk needs to
communicate appropriately modified search paths to bibtex,
dvipdf, dvips, and *latex.
- [Comment to technically savvy readers: *latex doesn't actually
- need the modified search path. But, surprisingly, dvipdf and
- dvips do, because sometimes graphics files get generated in the
- output or aux directories.]
+ [Comment to technically savvy readers: *latex doesn't actually
+ need the modified search path. But, surprisingly, dvipdf and
- The default under MSWin and Cygwin is ';' and under UNIX-like
- operating systems (including Linux and OS-X) is ':'. Normally
- the defaults give correct behavior. But there can be difficul-
- ties if your operating system is of one kind, but some of your
- software is running under an emulator for the other kind of op-
- erating system; in that case you'll need to find out what is
- needed, and set $search_path_separator explicitly. (The same
- goes, of course, for unusual operating systems that are not in
- the MSWin, Linux, OS-X, Unix collection.)
- $show_time [0]
- Whether to show time used, both the total and for individual
- steps.
- Note: On MS Windows, this is clock time. On other OSs it is the
- CPU time used (by latexmk and the child processes it invokes).
+ 24 December 2023 65
- 6 November 2023 64
+LATEXMK(1) General Commands Manual LATEXMK(1)
+ dvips do, because sometimes graphics files get generated in the
+ output or aux directories.]
-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-
+ ties if your operating system is of one kind, but some of your
+ software is running under an emulator for the other kind of op-
+ erating system; in that case you'll need to find out what is
+ needed, and set $search_path_separator explicitly. (The same
+ goes, of course, for unusual operating systems that are not in
+ the MSWin, Linux, OS-X, Unix collection.)
+ $show_time [0]
+ Whether to show time used, both the total and for individual
+ steps.
+ Note: On MS Windows, this is clock time. On other OSs it is the
+ CPU time used (by latexmk and the child processes it invokes).
The OS-dependence is because of a limitation of Windows. If you
wish to force the use of clock instead of CPU time, you can set
@@ -4236,40 +4321,63 @@
$silence_logfile_warnings [0]
- Whether after a run of *latex to summarize warnings in the log
- file about undefined citations and references. Setting $si-
+ Whether after a run of *latex to summarize warnings in the log
+ file about undefined citations and references. Setting $si-
lence_logfile_warnings=0 gives the summary of warnings (provided
- silent mode isn't also set), and this is useful to locate unde-
- fined citations and references without searching through the
- much more verbose log file or the screen output of *latex. But
- the summary can also be excessively annoying. The default is
- not to give these warnings. The command line options -si-
- lence_logfile_warning_list and -silence_logfile_warning_list-
+ silent mode isn't also set), and this is useful to locate unde-
+ fined citations and references without searching through the
+ much more verbose log file or the screen output of *latex. But
+ the summary can also be excessively annoying. The default is
+ not to give these warnings. The command line options -si-
+ lence_logfile_warning_list and -silence_logfile_warning_list-
also set this variable.
- Note that multiple occurrences for the same undefined object on
+ Note that multiple occurrences for the same undefined object on
the same page and same line will be compressed to a single warn-
ing.
+
$silent [0]
- Whether to run silently. Setting $silent to 1 has the same ef-
+ Whether to run silently. Setting $silent to 1 has the same ef-
fect as the -quiet of -silent options on the command line.
+
$sleep_time [2]
- The time to sleep (in seconds) between checking for source file
- changes when running with the -pvc option. This is subject to a
- minimum of one second delay, except that zero delay is also al-
- lowed.
+ The time to sleep (in seconds) between checking for source-file
+ changes when running with the -pvc option. If non-zero, it is
+ subject to a minimum value give by the $min_sleep_time variable.
+ But a zero value is also allowed.
- A value of exactly 0 gives no delay, and typically results in
- 100% CPU usage, which may not be desirable.
+
+
+ 24 December 2023 66
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
+ A value of exactly 0 gives no delay between checks for source-
+ file changes; it typically results in 100% CPU usage, which may
+ not be desirable.
+
+ In old versions of latexmk, the default value of $sleep_time of
+ 2 wB-pvctmodegand theeamountlofcCPUrusage.beOnemodernpocomputers
+ in
+ with fast multi-core CPUs, a smaller value, e.g., 0.1 can give
+ good results, especially when working with small documents whose
+ compilation may take well under a second.
+
+
$texfile_search [""]
- This is an obsolete variable, replaced by the @default_files
+ This is an obsolete variable, replaced by the @default_files
variable.
- For backward compatibility, if you choose to set $tex-
- file_search, it is a string of space-separated filenames, and
+ For backward compatibility, if you choose to set $tex-
+ file_search, it is a string of space-separated filenames, and
then latexmk replaces @default_files with the filenames in $tex-
file_search to which is added "*.tex".
@@ -4277,160 +4385,147 @@
See the documentation for $compiling_cmd.
$tmpdir [See below for default]
- Directory to store temporary files that latexmk may generate
+ Directory to store temporary files that latexmk may generate
while running.
- The default under MSWindows (including cygwin), is to set $tm-
- pdir to the value of the first of whichever of the system
+ The default under MSWindows (including cygwin), is to set $tm-
+ pdir to the value of the first of whichever of the system envi-
+ ronment variables TMPDIR or TEMP exists, otherwise to the cur-
+ rent directory. Under other operating systems (expected to be
+ UNIX/Linux, including OS-X), the default is the value of the
+ system environment variable TMPDIR if it exists, otherwise
+ "/tmp".
+ $use_make_for_missing_files [0]
+ Whether to use make to try and make files that are missing after
+ a run of *latex, and for which a custom dependency has not been
+ found. This is generally useful only when latexmk is used as
+ part of a bigger project which is built by using the make pro-
+ gram.
+ Note that once a missing file has been made, no further calls to
+ make will be made on a subsequent run of latexmk to update the
+ file. Handling this problem is the job of a suitably defined
+ Makefile. See the section "USING latexmk WITH make" for how to
+ do this. The intent of calling make from latexmk is merely to
+ detect dependencies.
- 6 November 2023 65
+ $view ["default"]
+ Which kind of file is to be previewed if a previewer is used.
+ The possible values are "default", "dvi", "ps", "pdf". The
+ value of "default" means that the "highest" of the kinds of file
+ 24 December 2023 67
-LATEXMK(1) General Commands Manual LATEXMK(1)
- environment variables TMPDIR or TEMP exists, otherwise to the
- current directory. Under other operating systems (expected to
- be UNIX/Linux, including OS-X), the default is the value of the
- system environment variable TMPDIR if it exists, otherwise
- "/tmp".
- $use_make_for_missing_files [0]
- Whether to use make to try and make files that are missing after
- a run of *latex, and for which a custom dependency has not been
- found. This is generally useful only when latexmk is used as
- part of a bigger project which is built by using the make pro-
- gram.
+LATEXMK(1) General Commands Manual LATEXMK(1)
- Note that once a missing file has been made, no further calls to
- make will be made on a subsequent run of latexmk to update the
- file. Handling this problem is the job of a suitably defined
- Makefile. See the section "USING latexmk WITH make" for how to
- do this. The intent of calling make from latexmk is merely to
- detect dependencies.
- $view ["default"]
- Which kind of file is to be previewed if a previewer is used.
- The possible values are "default", "dvi", "ps", "pdf". The
- value of "default" means that the "highest" of the kinds of file
generated is to be used (among .dvi, .ps and .pdf).
$warnings_as_errors [0]
- Normally latexmk copies the behavior of latex in treating unde-
- fined references and citations and multiply defined references
- as conditions that give a warning but not an error. The vari-
+ Normally latexmk copies the behavior of latex in treating unde-
+ fined references and citations and multiply defined references
+ as conditions that give a warning but not an error. The vari-
able $warnings_as_errors controls whether this behavior is modi-
fied.
- When the variable is non-zero, latexmk at the end of its run
- will return a non-zero status code to the operating system if
- any of the files processed gives a warning about problems with
+ When the variable is non-zero, latexmk at the end of its run
+ will return a non-zero status code to the operating system if
+ any of the files processed gives a warning about problems with
citations or references (i.e., undefined citations or references
or multiply defined references). This is after latexmk has com-
- pleted all the runs it needs to try and resolve references and
- citations. Thus $warnings_as_errors being nonzero causes la-
+ pleted all the runs it needs to try and resolve references and
+ citations. Thus $warnings_as_errors being nonzero causes la-
texmk to treat such warnings as errors, but only when they occur
on the last run of *latex and only after processing is complete.
- A non-zero value $warnings_as_errors can be set by the command-
+ A non-zero value $warnings_as_errors can be set by the command-
line option -Werror.
The default behavior is normally satisfactory in the usual edit-
- compile-edit cycle. But, for example, latexmk can also be used
- 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-
- ings as errors that require the overall build process to be
+ compile-edit cycle. But, for example, latexmk can also be used
+ 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-
+ ings as errors that require the overall build process to be
aborted. Of course, since multiple runs of *latex are generally
- needed to resolve references and citations, what matters is not
+ needed to resolve references and citations, what matters is not
+ the warnings on the first run, but the warnings on the last run;
+ latexmk takes this into account appropriately.
+ In addition, when preview-continuous mode is used, a non-zero
+ value for $warnings_as_errors changes the use of the commands
+ $failure_cmd, $warning_cmd, and $success_cmd after a complia-
+ tion. If there are citation or reference warnings, but no other
+ errors, the behavior is as follows. If $warning_cmd is set, it
+ is used. If it is not set, then then if $warnings_as_errors is
+ non-zero and $failure_cmd is set, then $failure_cmd. Otherwise
+ $success_cmd is used, if it is set. (The foregoing explanation
+ is rather complicated, because latexmk has to deal with the case
+ that one or more of the commands isn't set.)
- 6 November 2023 66
+ $xdv_mode [0]
+ If one, generate an xdv version of the document by use of xela-
+ tex.
+ $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).
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ 24 December 2023 68
- the warnings on the first run, but the warnings on the last run;
- latexmk takes this into account appropriately.
- In addition, when preview-continuous mode is used, a non-zero
- value for $warnings_as_errors changes the use of the commands
- $failure_cmd, $warning_cmd, and $success_cmd after a complia-
- tion. If there are citation or reference warnings, but no other
- errors, the behavior is as follows. If $warning_cmd is set, it
- is used. If it is not set, then then if $warnings_as_errors is
- non-zero and $failure_cmd is set, then $failure_cmd. Otherwise
- $success_cmd is used, if it is set. (The foregoing explanation
- is rather complicated, because latexmk has to deal with the case
- that one or more of the commands isn't set.)
- $xdv_mode [0]
- If one, generate an xdv version of the document by use of xela-
- tex.
+LATEXMK(1) General Commands Manual LATEXMK(1)
- $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).
-
$xdvipdfmx_silent_switch ["-q"]
Switch(es) for the xdvipdfmx program when silent mode is on.
$xelatex ["xelatex %O %S"]
- Specifies the command line for the LaTeX processing program of
- when the xelatex program is called for. See the documentation
- of the -xelatex option for some special properties of latexmk's
+ Specifies the command line for the LaTeX processing program of
+ when the xelatex program is called for. See the documentation
+ of the -xelatex option for some special properties of latexmk's
use of xelatex.
- Note about xelatex: latexmk uses xelatex to make an .xdv rather
- than .pdf file, with the .pdf file being created in a separate
+ Note about xelatex: latexmk uses xelatex to make an .xdv rather
+ than .pdf file, with the .pdf file being created in a separate
step. This is enforced by the use of the -no-pdf option. If %O
- is part of the command for invoking xelatex, then latexmk will
+ is part of the command for invoking xelatex, then latexmk will
insert the -no-pdf option automatically, otherwise you must pro-
- vide the option yourself. See the documentation for the -pdfxe
+ vide the option yourself. See the documentation for the -pdfxe
option for why latexmk makes a .xdv file rather than a .pdf file
when xelatex is used.
- To do a coordinated setting of all of $dvilualatex, $latex,
- $pdflatex, $lualatex, and $xelatex, see the section "Advanced
- Configuration".
+ To do a coordinated setting of all of $dvilualatex, $hilatex,
+ $latex, $pdflatex, $lualatex, and $xelatex, see the section "Ad-
+ vanced Configuration".
%xelatex_input_extensions
- This variable specifies the extensions tried by latexmk when it
- finds that an xelatex run resulted in an error that a file has
- not been found, and the file is given without an extension.
- This typically happens when LaTeX commands of the form \in-
- put{file} or \includegraphics{figure}, when the relevant source
-
-
-
- 6 November 2023 67
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
+ This variable specifies the extensions tried by latexmk when it
+ finds that an xelatex run resulted in an error that a file has
+ not been found, and the file is given without an extension.
+ This typically happens when LaTeX commands of the form \in-
+ put{file} or \includegraphics{figure}, when the relevant source
file does not exist.
- In this situation, latexmk searches for custom dependencies to
- make the missing file(s), but restricts it to the extensions
- specified by the variable %xelatex_input_extensions. The de-
+ In this situation, latexmk searches for custom dependencies to
+ make the missing file(s), but restricts it to the extensions
+ specified by the variable %xelatex_input_extensions. The de-
fault extensions are 'tex', 'pdf', 'jpg, and 'png'.
See details of the %latex_input_extensions for other information
@@ -4437,10 +4532,10 @@
that equally applies to %xelatex_input_extensions.
$xelatex_silent_switch ["-interaction=batchmode"]
- Switch(es) for the xelatex program (specified in the variable
+ Switch(es) for the xelatex program (specified in the variable
$xelatex) when silent mode is on.
- See details of the $latex_silent_switch for other information
+ See details of the $latex_silent_switch for other information
that equally applies to $xelatex_silent_switch.
@@ -4447,17 +4542,27 @@
CUSTOM DEPENDENCIES
- In any RC file a set of custom dependencies can be set up to convert a
+ In any RC file a set of custom dependencies can be set up to convert a
file with one extension to a file with another. An example use of this
would be to allow latexmk to convert a .fig file to .eps to be included
in the .tex file.
+
+ 24 December 2023 69
+
+
+
+
+
+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
- defining the custom dependencies. (See the section "Old Method of
- Defining Custom Dependencies" for details.) This method still works,
+ directly manipulate the @cus_dep_list array that contains information
+ defining the custom dependencies. (See the section "Old Method of
+ Defining Custom Dependencies" for details.) This method still works,
but is no longer preferred.
A better method is to use the subroutines that allow convenient manipu-
@@ -4470,7 +4575,7 @@
The arguments are as follows:
from extension:
- The extension of the file we are converting from (e.g. "fig").
+ The extension of the file we are converting from (e.g. "fig").
It is specified without a period.
to extension:
@@ -4477,99 +4582,87 @@
The extension of the file we are converting to (e.g. "eps"). It
is specified without a period.
- must: If non-zero, the file from which we are converting must exist,
- if it doesn't exist latexmk will give an error message and exit
+ must: If non-zero, the file from which we are converting must exist,
+ if it doesn't exist latexmk will give an error message and exit
unless the -f option is specified. If must is zero and the file
+ we are converting from doesn't exist, then no action is taken.
+ Generally, the appropriate value of must is zero.
+ function:
+ The name of the subroutine that latexmk should call to perform
+ the file conversion. The first argument to the subroutine is
+ the base name of the file to be converted without any extension.
+ The subroutines are declared in the syntax of Perl. The func-
+ tion should return 0 if it was successful and a nonzero number
+ if it failed.
- 6 November 2023 68
+ Naturally add_cus_dep adds a custom dependency with the specified from
+ and to extensions. If a custom dependency has been previously defined
+ (e.g., in an rcfile that was read earlier), then it is replaced by the
+ new one.
+ The subroutine remove_cus_dep removes the specified custom dependency.
+ The subroutine show_cus_dep causes a list of the currently defined cus-
+ tom dependencies to be sent to the screen output.
+ How custom dependencies are used:
+ An instance of a custom dependency rule is created whenever latexmk de-
+ tects that a run of *latex needs to read a file, like a graphics file,
+ whose extension is the to-extension of a custom dependency. Then la-
+ texmk examines whether a file exists with the same name, but with the
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ 24 December 2023 70
- we are converting from doesn't exist, then no action is taken.
- Generally, the appropriate value of must is zero.
- function:
- The name of the subroutine that latexmk should call to perform
- the file conversion. The first argument to the subroutine is
- the base name of the file to be converted without any extension.
- The subroutines are declared in the syntax of Perl. The func-
- tion should return 0 if it was successful and a nonzero number
- if it failed.
- Naturally add_cus_dep adds a custom dependency with the specified from
- and to extensions. If a custom dependency has been previously defined
- (e.g., in an rcfile that was read earlier), then it is replaced by the
- new one.
- The subroutine remove_cus_dep removes the specified custom dependency.
- The subroutine show_cus_dep causes a list of the currently defined cus-
- tom dependencies to be sent to the screen output.
+LATEXMK(1) General Commands Manual LATEXMK(1)
- How custom dependencies are used:
- An instance of a custom dependency rule is created whenever latexmk de-
- tects that a run of *latex needs to read a file, like a graphics file,
- whose extension is the to-extension of a custom dependency. Then la-
- texmk examines whether a file exists with the same name, but with the
- corresponding from-extension, as specified in the custom-dependency.
- If it does, then a corresponding instance of the custom dependency is
- created, after which the rule is invoked whenever the destination file
+ corresponding from-extension, as specified in the custom-dependency.
+ If it does, then a corresponding instance of the custom dependency is
+ created, after which the rule is invoked whenever the destination file
(the one with the to-extension) is out-of-date with respect to the cor-
responding source file.
- To make the new destination file, the Perl subroutine specified in the
+ To make the new destination file, the Perl subroutine specified in the
rule is invoked, with an argument that is the base name of the files in
- question. Simple cases just involve a subroutine invoking an external
- program; this can be done by following the templates below, even by
- those without knowledge of the Perl programming language. Of course,
+ question. Simple cases just involve a subroutine invoking an external
+ program; this can be done by following the templates below, even by
+ those without knowledge of the Perl programming language. Of course,
experts could do something much more elaborate.
- One item in the specification of each custom-dependency rule, labeled
- "must" above, specifies how the rule should be applied when the source
+ One item in the specification of each custom-dependency rule, labeled
+ "must" above, specifies how the rule should be applied when the source
file fails to exist.
- When latex reports that an input file (e.g., a graphics file) does not
+ When latex reports that an input file (e.g., a graphics file) does not
exist, latexmk tries to find a source file and a custom dependency that
can be used to make it. If it succeeds, then it creates an instance of
- the custom dependency and invokes it to make the missing file, after
+ the custom dependency and invokes it to make the missing file, after
which the next pass of latex etc will be able to read the newly created
file.
- Note for advanced usage: The operating system's environment variable
+ 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
-
-
-
- 6 November 2023 69
-
-
-
-
-
-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-
+ tex etc. Correspondingly, when a missing file is reported, latexmk
+ 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.
Function to implement custom dependency, traditional method:
- The function that implements a custom dependency gets the information
+ The function that implements a custom dependency gets the information
on the files to be processed in two ways. The first is through its one
- argument; the argument contains the base name of the source and desti-
+ argument; the argument contains the base name of the source and desti-
nation files. The second way is described later.
- A simple and typical example of code in an initialization rcfile using
+ A simple and typical example of code in an initialization rcfile using
the first method is:
add_cus_dep( 'fig', 'eps', 0, 'fig2eps' );
@@ -4577,33 +4670,45 @@
system( "fig2dev -Leps \"$_[0].fig\" \"$_[0].eps\"" );
}
- The first line adds a custom dependency that converts a file with ex-
+ The first line adds a custom dependency that converts a file with ex-
tension "fig", as created by the xfig program, to an encapsulated post-
- script file, with extension "eps". The remaining lines define a sub-
- routine that carries out the conversion. If a rule for converting
- "fig" to "eps" files already exists (e.g., from a previously read-in
- initialization file), the latexmk will delete this rule before making
+ script file, with extension "eps". The remaining lines define a sub-
+ routine that carries out the conversion. If a rule for converting
+ "fig" to "eps" files already exists (e.g., from a previously read-in
+ initialization file), the latexmk will delete this rule before making
the new one.
- 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
- of each of the files (possibly with a path component). This argument
- is referred to by Perl as $_[0]. In the example above, the subroutine
+
+
+
+ 24 December 2023 71
+
+
+
+
+
+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
+ of each of the files (possibly with a path component). This argument
+ is referred to by Perl as $_[0]. In the example above, the subroutine
uses the Perl command system to invoke the program fig2dev. The double
quotes around the string are a Perl idiom that signify that each string
- of the form of a variable name, $_[0] in this case, is to be substi-
+ of the form of a variable name, $_[0] in this case, is to be substi-
tuted by its value.
- If the return value of the subroutine is non-zero, then latexmk will
- assume an error occurred during the execution of the subroutine. In
- the above example, no explicit return value is given, and instead the
- return value is the value returned by the last (and only) statement,
+ If the return value of the subroutine is non-zero, then latexmk will
+ assume an error occurred during the execution of the subroutine. In
+ the above example, no explicit return value is given, and instead the
+ return value is the value returned by the last (and only) statement,
i.e., the invocation of system, which returns the value 0 on success.
- If you use pdflatex, lualatex or xelatex instead of latex, then you
- will probably prefer to convert your graphics files to pdf format, in
- which case you would replace the above code in an initialization file
+ If you use pdflatex, lualatex or xelatex instead of latex, then you
+ will probably prefer to convert your graphics files to pdf format, in
+ which case you would replace the above code in an initialization file
by
add_cus_dep( 'fig', 'pdf, 0, 'fig2pdf' );
@@ -4611,59 +4716,60 @@
system( "fig2dev -Lpdf \"$_[0].fig\" \"$_[0].pdf\"" );
}
- Note 1: In the command lines given in the system commands in the above
+ 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
+ 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.
+ Note 2: One case in which the quotes are important is when the files
+ are in a subdirectory and your operating system is Microsoft Windows.
+ Then the separator character for directory components can be either a
+ forward slash '/' or Microsoft's more usual backward slash '\'. For-
+ ward slashes are generated by latexmk, to maintain its sanity from
+ software like MiKTeX that mixes both directory separators; but their
+ correct use normally requires quoted filenames. (See a log file from a
+ run of MiKTeX (at least in v. 2.9) for an example of the use of both
+ directory separators.)
+ Note 3: The subroutines implementing custom dependencies in the exam-
+ ples given just have a single line invoking an external program.
+ That's the usual situation. But since the subroutines are in the Perl
+ language, you can implement much more complicated processing if you
+ need it.
- 6 November 2023 70
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ 24 December 2023 72
- 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
- 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.
- Note 2: One case in which the quotes are important is when the files
- are in a subdirectory and your operating system is Microsoft Windows.
- Then the separator character for directory components can be either a
- forward slash '/' or Microsoft's more usual backward slash '\'. For-
- ward slashes are generated by latexmk, to maintain its sanity from
- software like MiKTeX that mixes both directory separators; but their
- correct use normally requires quoted filenames. (See a log file from a
- run of MiKTeX (at least in v. 2.9) for an example of the use of both
- directory separators.)
- Note 3: The subroutines implementing custom dependencies in the exam-
- ples given just have a single line invoking an external program.
- That's the usual situation. But since the subroutines are in the Perl
- language, you can implement much more complicated processing if you
- need it.
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
Removing custom dependencies, and when you might need to do this:
- If you have some general custom dependencies defined in the system or
- user initialization file, you may find that for a particular project
- they are undesirable. So you might want to delete the unneeded ones.
- A situation where this would be desirable is where there are multiple
- custom dependencies with the same from-extension or the same to-exten-
- sion. In that case, latexmk might choose a different one from the one
+ If you have some general custom dependencies defined in the system or
+ user initialization file, you may find that for a particular project
+ they are undesirable. So you might want to delete the unneeded ones.
+ A situation where this would be desirable is where there are multiple
+ custom dependencies with the same from-extension or the same to-exten-
+ sion. In that case, latexmk might choose a different one from the one
you want for a specific project. As an example, to remove any "fig" to
"eps" rule you would use:
remove_cus_dep( 'fig', 'eps' );
- If you have complicated sets of custom dependencies, you may want to
- get a listing of the custom dependencies. This is done by using the
+ If you have complicated sets of custom dependencies, you may want to
+ get a listing of the custom dependencies. This is done by using the
line
show_cus_dep();
@@ -4674,57 +4780,56 @@
Function implementing custom dependency, alternative methods:
So far the examples for functions to implement custom dependencies have
used the argument of the function to specify the base name of converted
- file. This method has been available since very old versions of la-
+ file. This method has been available since very old versions of la-
texmk, and many examples can be found, e.g., on the web.
- However in later versions of latexmk the internal structure of the
+ 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".
+ Examples of their use is given in the following examples, concerning
+ multiple index files and glossaries.
+ The only index-file conversion built-in to latexmk is from an ".idx"
+ file written on one run of *latex to an ".ind" file to be read in on a
+ subsequent run. But with the index.sty package, for example, you can
+ create extra indexes with extensions that you configure. Latexmk does
+ not know how to deduce the extensions from the information it has. But
+ you can easily write a custom dependency. For example if your latex
+ file uses the command "\newindex{special}{ndx}{nnd}{Special index}" you
+ will need to get latexmk to convert files with the extension .ndx to
+ .nnd. The most elementary method is to define a custom dependency as
+ follows:
- 6 November 2023 71
+ add_cus_dep( 'ndx', 'nnd', 0, 'ndx2nnd' );
+ sub ndx2nnd {
+ return system( "makeindex -o \"$_[0].nnd\" \"$_[0].ndx\"" );
+ }
+ push @generated_exts, 'ndx', 'nnd';
+ 24 December 2023 73
-LATEXMK(1) General Commands Manual LATEXMK(1)
- implementation of its "rules" for the steps of processing, including
- custom dependencies, became much more powerful. The function imple-
- menting a custom dependency is executed within a special context where
- a number of extra variables and subroutines are defined. Publicly doc-
- umented ones, intended to be long-term stable, are listed below, under
- the heading "Variables and subroutines for processing a rule".
- Examples of their use is given in the following examples, concerning
- multiple index files and glossaries.
+LATEXMK(1) General Commands Manual LATEXMK(1)
- The only index-file conversion built-in to latexmk is from an ".idx"
- file written on one run of *latex to an ".ind" file to be read in on a
- subsequent run. But with the index.sty package, for example, you can
- create extra indexes with extensions that you configure. Latexmk does
- not know how to deduce the extensions from the information it has. But
- you can easily write a custom dependency. For example if your latex
- file uses the command "\newindex{special}{ndx}{nnd}{Special index}" you
- will need to get latexmk to convert files with the extension .ndx to
- .nnd. The most elementary method is to define a custom dependency as
- follows:
- add_cus_dep( 'ndx', 'nnd', 0, 'ndx2nnd' );
- sub ndx2nnd {
- return system( "makeindex -o \"$_[0].nnd\" \"$_[0].ndx\"" );
- }
- push @generated_exts, 'ndx', 'nnd';
-
- Notice the added line compared with earlier examples. The extra line
+ Notice the added line compared with earlier examples. The extra line
gets the extensions "ndx" and "nnd" added to the list of extensions for
generated files; then the extra index files will be deleted by clean-up
operations
- But if you have yet more indexes with yet different extensions, e.g.,
- "adx" and "and", then you will need a separate function for each pair
- of extensions. This is quite annoying. You can use the Run_subst
+ But if you have yet more indexes with yet different extensions, e.g.,
+ "adx" and "and", then you will need a separate function for each pair
+ of extensions. This is quite annoying. You can use the Run_subst
function to simplify the definitions to use a single function:
add_cus_dep( 'ndx', 'nnd', 0, 'dx2nd' );
@@ -4743,49 +4848,48 @@
}
push @generated_exts, 'ndx', 'nnd', 'adx', 'and';
- This last example uses the command specification in $makeindex, and so
-
-
-
- 6 November 2023 72
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
- any customization you have made for the standard index also applies to
+ This last example uses the command specification in $makeindex, and so
+ any customization you have made for the standard index also applies to
your extra indexes.
Similar techniques can be applied for glossaries.
Those of you with experience with Makefiles, may get concerned that the
- .ndx file is written during a run of *latex and is always later than
+ .ndx file is written during a run of *latex and is always later than
the .nnd last read in. Thus the .nnd appears to be perpetually out-of-
- date. This situation, of circular dependencies, is endemic to latex,
- and is one of the issues that latexmk is programmed to overcome. It
- examines the contents of the files (by use of a checksum), and only
+ date. This situation, of circular dependencies, is endemic to latex,
+ and is one of the issues that latexmk is programmed to overcome. It
+ examines the contents of the files (by use of a checksum), and only
does a remake when the file contents have actually changed.
- Of course if you choose to write random data to the .nnd (or the .aux
- file, etc) that changes on each new run, then you will have a problem.
+ Of course if you choose to write random data to the .nnd (or the .aux
+ file, etc) that changes on each new run, then you will have a problem.
For real experts: See the %hash_calc_ignore_pattern if you have to deal
with such problems.
Old Method of Defining Custom Dependencies:
- In much older versions of latexmk, the only method of defining custom
- dependencies was to directly manipulate the table of custom dependen-
+ In much older versions of latexmk, the only method of defining custom
+ dependencies was to directly manipulate the table of custom dependen-
cies. This is contained in the @cus_dep_list array. It is an array of
- strings, and each string in the array has four items in it, each sepa-
- rated by a space, the from-extension, the to-extension, the "must"
- item, and the name of the subroutine for the custom dependency. These
+ strings, and each string in the array has four items in it, each sepa-
+ rated by a space, the from-extension, the to-extension, the "must"
+ item, and the name of the subroutine for the custom dependency. These
were all defined above.
+
+
+ 24 December 2023 74
+
+
+
+
+
+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
+ lows. It is the code in an RC file to ensure automatic conversion of
.fig files to .eps files:
push @cus_dep_list, "fig eps 0 fig2eps";
@@ -4793,82 +4897,81 @@
return system( "fig2dev -Lps \"$_[0].fig\" \"$_[0].eps\"" );
}
- This method still works, and is almost equivalent to the code given
- earlier that used the add_cus_dep subroutine. However, the old method
- doesn't delete any previous custom-dependency for the same conversion.
+ This method still works, and is almost equivalent to the code given
+ earlier that used the add_cus_dep subroutine. However, the old method
+ doesn't delete any previous custom-dependency for the same conversion.
So the new method is preferable.
Advanced configuration: Some extra resources and advanced tricks
- For most purposes, simple configuration for latexmk along the lines of
- the examples given is sufficient. But sometimes you need something
- harder. In this section, I indicate some extra possibilities. Gener-
- ally to use these, you need to be fluent in the Perl language, since
+ For most purposes, simple configuration for latexmk along the lines of
+ the examples given is sufficient. But sometimes you need something
+ harder. In this section, I indicate some extra possibilities. Gener-
+ ally to use these, you need to be fluent in the Perl language, since
this is what is used in the rc files.
- See also the section DEALING WITH ERRORS, PROBLEMS, ETC. See also the
+ See also the section DEALING WITH ERRORS, PROBLEMS, ETC. See also the
examples in the directory example_rcfiles in the latexmk distributions.
- Even if none of the examples apply to your case, they may give you
+ Even if none of the examples apply to your case, they may give you use-
+ ful ideas
+ Utility subroutines
+ ensure_path( var, values ...)
- 6 November 2023 73
+ The first parameter is the name of one of the system's environ-
+ ment variables for search paths. The remaining parameters are
+ values that should be in the variable. For each of the value
+ parameters, if it isn't already in the variable, then it is
+ prepended to the variable; in that case the environment variable
+ is created if it doesn't already exist. For separating values,
+ the character appropriate the the operating system is used --
+ see the configuration variable $search_path_separator.
+ Example:
+ ensure_path( 'TEXINPUTS', './custom_cls_sty_files//' );
+ (In this example, the trailing '//' is documented by TeX systems
+ to mean that *latex search for files in the specified directory
+ and in all subdirectories.)
+ Technically ensure_path works by setting Perl's variable
+ $ENV{var}, where var is the name of the target variable. The
+ changed value is then passed as an environment variable to any
+ invoked programs.
-LATEXMK(1) General Commands Manual LATEXMK(1)
- useful ideas
+ 24 December 2023 75
- Utility subroutines
- ensure_path( var, values ...)
- The first parameter is the name of one of the system's environ-
- ment variables for search paths. The remaining parameters are
- values that should be in the variable. For each of the value
- parameters, if it isn't already in the variable, then it is
- prepended to the variable; in that case the environment variable
- is created if it doesn't already exist. For separating values,
- the character appropriate the the operating system is used --
- see the configuration variable $search_path_separator.
- Example:
- ensure_path( 'TEXINPUTS', './custom_cls_sty_files//' );
- (In this example, the trailing '//' is documented by TeX systems
- to mean that *latex search for files in the specified directory
- and in all subdirectories.)
+LATEXMK(1) General Commands Manual LATEXMK(1)
- Technically ensure_path works by setting Perl's variable
- $ENV{var}, where var is the name of the target variable. The
- changed value is then passed as an environment variable to any
- invoked programs.
-
Variables and subroutines for processing a rule
A step in the processing is called a rule. One possibility to implement
- the processing of a rule is by a Perl subroutine. This is always the
- case for custom dependencies. Also, for any other rule, you can use a
- subroutine by prefixing the command specification by the word "inter-
+ the processing of a rule is by a Perl subroutine. This is always the
+ case for custom dependencies. Also, for any other rule, you can use a
+ subroutine by prefixing the command specification by the word "inter-
nal" -- see the section FORMAT OF COMMAND SPECIFICATIONS.
- When you use a subroutine for processing a rule, all the possibilities
+ When you use a subroutine for processing a rule, all the possibilities
of Perl programming are available, of course. In addition, some of la-
- texmk's internal variables and subroutines are available. The ones
- listed below are intended to be available to (advanced) users, and
+ texmk's internal variables and subroutines are available. The ones
+ listed below are intended to be available to (advanced) users, and
their specifications will generally have stability under upgrades. Gen-
- erally, the variables should be treated as read-only: Changing their
- values can have bad consequences, since it is liable to mess up the
+ erally, the variables should be treated as read-only: Changing their
+ values can have bad consequences, since it is liable to mess up the
consistency of what latexmk is doing.
- $rule This variable has the name of the rule, as known to latexmk.
- Note that the exact contents of this variable for a given rule
+ $rule This variable has the name of the rule, as known to latexmk.
+ Note that the exact contents of this variable for a given rule
may be dependent on the version of latexmk
$$Psource
@@ -4875,34 +4978,21 @@
This gives the name of the primary source file. Note the double
dollar signs.
-
-
-
-
- 6 November 2023 74
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
$$Pdest
- This gives the name of the main output file if any. Note the
+ This gives the name of the main output file if any. Note the
double dollar signs.
pushd( path ), popd()
- These subroutines are used when it is needed to temporarily
+ These subroutines are used when it is needed to temporarily
change the working directory, as in
pushd( 'some_directory' );
- ... Processing done with 'some_directory' as the working
+ ... Processing done with 'some_directory' as the working
directory
popd()
- They perform exactly the same function as the commands of the
+ They perform exactly the same function as the commands of the
same names in operating system command shells like bash on Unix,
and cmd.exe on the Windows.
@@ -4909,84 +4999,95 @@
rdb_add_generated( file, ... )
This subroutine is to be used in the context of a rule, that is,
- from within a subroutine that is carrying out processing of a
+ from within a subroutine that is carrying out processing of a
rule. Such is the case for the subroutine implementing a custom
- dependency, or the subroutine invoked by using the "internal"
- keyword in the command specification like that in the variable
+ dependency, or the subroutine invoked by using the "internal"
+ keyword in the command specification like that in the variable
$latex.
- Its arguments are a sequence of filenames which are generated
- during the running of the rule. The names might arise from an
+ Its arguments are a sequence of filenames which are generated
+ during the running of the rule. The names might arise from an
analysis of the results of the run, e.g., in a log file, or from
- knowledge of properties of the specific rule. Calling
- rdb_add_generated with these filenames ensures that these files
- are flagged as generated by the rule in latexmk's internal data
- structures. Basically, no action is taken if the files have al-
- ready been flagged as generated.
- A main purpose of using this subroutine is for the situation
- when a generated file is also the source file for some rule, so
- that latexmk can correctly link the dependency information in
- its network of rules.
- Note: Unlike some other subroutines in this section, there is no
- argument for a rule for rdb_add_generated. Instead, the subrou-
- tine is to be invoked during the processing of a rule when la-
- texmk has set up an appropriate context (i.e., appropriate vari-
- ables). In contrast, subroutines with a rule argument can be
- used also outside a rule context.
+ 24 December 2023 76
- rdb_ensure_file( $rule, file )
- This subroutine ensures that the given file is among the source
- files for the specified rule. It is typically used when, during
- the processing of a rule, it is known that a particular extra
- file is among the dependencies that latexmk should know, but its
- 6 November 2023 75
+LATEXMK(1) General Commands Manual LATEXMK(1)
+ knowledge of properties of the specific rule. Calling
+ rdb_add_generated with these filenames ensures that these files
+ are flagged as generated by the rule in latexmk's internal data
+ structures. Basically, no action is taken if the files have al-
+ ready been flagged as generated.
+ A main purpose of using this subroutine is for the situation
+ when a generated file is also the source file for some rule, so
+ that latexmk can correctly link the dependency information in
+ its network of rules.
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ Note: Unlike some other subroutines in this section, there is no
+ argument for a rule for rdb_add_generated. Instead, the subrou-
+ tine is to be invoked during the processing of a rule when la-
+ texmk has set up an appropriate context (i.e., appropriate vari-
+ ables). In contrast, subroutines with a rule argument can be
+ used also outside a rule context.
- default methods don't find the dependency. Almost always the
- first argument is the name of the rule currently being pro-
+ rdb_ensure_file( $rule, file )
+ This subroutine ensures that the given file is among the source
+ files for the specified rule. It is typically used when, during
+ the processing of a rule, it is known that a particular extra
+ file is among the dependencies that latexmk should know, but its
+ default methods don't find the dependency. Almost always the
+ first argument is the name of the rule currently being pro-
cessed, so it is then appropriate to specify it by $rule.
- For examples of its use, see some of the files in the directory
- example_rcfiles of latexmk's distribution. Currently the cases
- that use this subroutine are bib2gls-latexmkrc, exceltex_la-
- texmkrc and texinfo-latexmkrc. These illustrate typical cases
- where latexmk's normal processing fails to detect certain extra
+ For examples of its use, see some of the files in the directory
+ example_rcfiles of latexmk's distribution. Currently the cases
+ that use this subroutine are bib2gls-latexmkrc, exceltex_la-
+ texmkrc and texinfo-latexmkrc. These illustrate typical cases
+ where latexmk's normal processing fails to detect certain extra
source files.
Note that rdb_ensure_file only has one filename argument, unlike
other subroutines in this section. If you want to apply its ac-
- tion to multiple files, you will need one call to rdb_en-
+ tion to multiple files, you will need one call to rdb_en-
sure_file for each file.
rdb_remove_files( $rule, file, ... )
- This subroutine removes one or more files from the dependency
+ This subroutine removes one or more files from the dependency
list for the given rule.
rdb_remove_generated( file, ... )
This subroutine is to be used in the context of a rule, that is,
- from within a subroutine that is carrying out processing of a
- rule. It performs the opposite action to rdb_add_generated.
- Its effect is to ensure that the given filenames are not listed
- in latexmk's internal data structures as being generated by the
+ from within a subroutine that is carrying out processing of a
+ rule. It performs the opposite action to rdb_add_generated.
+ Its effect is to ensure that the given filenames are not listed
+ in latexmk's internal data structures as being generated by the
rule.
+
+
+ 24 December 2023 77
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
rdb_list_source( $rule )
- This subroutine returns the list of source files (i.e., the de-
+ This subroutine returns the list of source files (i.e., the de-
pendency list) for the given rule.
@@ -4994,9 +5095,9 @@
rdb_set_source( $rule, @files )
- This subroutine sets the dependency list for the given rule to
+ This subroutine sets the dependency list for the given rule to
be the specified files. Files that are already in the list have
- unchanged information. Files that were not in the list are
+ unchanged information. Files that were not in the list are
added to it. Files in the previous dependency list that are not
in the newly specified list of files are removed from the depen-
dency list.
@@ -5004,59 +5105,58 @@
Run_subst( command_spec )
This subroutine runs the command specified by command_spec. The
- specification is a string in the format listed in the section
- "Format of Command Specifications". An important action of the
+ specification is a string in the format listed in the section
+ "Format of Command Specifications". An important action of the
Run_subst is to make substitutions of placeholders, e.g., %S and
- %D for source and destination files; these get substituted
+ %D for source and destination files; these get substituted be-
+ fore the command is run. In addition, the command after substi-
+ tution is printed to the screen unless latexmk is running in
+ silent mode.
+ Coordinated Setting of Commands for *latex
+ To set all of $dvilualatex, $hilatex, $latex, $pdflatex, $lualatex, and
+ $xelatex to a common pattern, you can use one of the following subrou-
+ tines, std_tex_cmds, alt_tex_cmds, and set_tex_cmds.
- 6 November 2023 76
+ To get the standard commands, use
+ &std_tex_cmds;
+ This results in $latex = 'latex %O %S', and similarly for $dvilualatex,
+ $hilatex, $pdflatex, $lualatex, and $xelatex. Note the ampersand in
+ the invocation; this indicates to Perl that a subroutine is being
+ called. (The use of this subroutine enables you to override previous
+ redefinitions of the $latex, etc variables, which might have occurred
+ in an earlier-read rc file.)
+ To be able to use the string provided by the -pretex option (if any),
+ you can use
+ &alt_tex_cmds;
-LATEXMK(1) General Commands Manual LATEXMK(1)
+ This results in $latex = 'latex %O %P', etc. Again note the ampersand
+ in the invocation; this indicates to Perl that a subroutine is being
+ called.
+ A more general way of specifying the variables is using
- before the command is run. In addition, the command after sub-
- stitution is printed to the screen unless latexmk is running in
- silent mode.
- Coordinated Setting of Commands for *latex
- To set all of $dvilualatex, $latex, $pdflatex, $lualatex, and $xelatex
- to a common pattern, you can use one of the following subroutines,
- std_tex_cmds, alt_tex_cmds, and set_tex_cmds.
+ 24 December 2023 78
- To get the standard commands, use
- &std_tex_cmds;
- This results in $latex = 'latex %O %S', and similarly for $dvilualatex,
- $pdflatex, $lualatex, and $xelatex. Note the ampersand in the invoca-
- tion; this indicates to Perl that a subroutine is being called. (The
- use of this subroutine enables you to override previous redefinitions
- of the $latex, etc variables, which might have occurred in an earlier-
- read rc file.)
- To be able to use the string provided by the -pretex option (if any),
- you can use
- &alt_tex_cmds;
+LATEXMK(1) General Commands Manual LATEXMK(1)
- This results in $latex = 'latex %O %P', etc. Again note the ampersand
- in the invocation; this indicates to Perl that a subroutine is being
- called.
- A more general way of specifying the variables is using
-
set_tex_cmds( 'CMD_SPEC' );
- Here CMD_SPEC is the command line without the program name. This re-
- sults in $latex = 'latex CMD_SPEC', and similarly for $pdflatex, etc.
- (An ampersand preceding the subroutine name is not necessary here,
+ Here CMD_SPEC is the command line without the program name. This re-
+ sults in $latex = 'latex CMD_SPEC', and similarly for $pdflatex, etc.
+ (An ampersand preceding the subroutine name is not necessary here,
since the parentheses show Perl that a subroutine is being invoked.)
An example that provides the --interaction=batchmode option to the *la-
@@ -5064,68 +5164,69 @@
set_tex_cmds( '--interaction=batchmode %O %S' );
- This results in $latex = 'latex --interaction=batchmode %O %S ', etc.
- Note that when '%O' appears after the added option, as here, options
+ This results in $latex = 'latex --interaction=batchmode %O %S ', etc.
+ Note that when '%O' appears after the added option, as here, options
provided on the command line to latexmk can override the supplied one.
A more general command line can be set up by using the placeholder '%C'
in CMD_SPEC. The '%C' is substituted by the basic name of the command,
i.e., whichever of 'latex', 'pdflatex', etc is appropriate. (More than
- one occurrence of '%C' is allowed.) For example to use the develop-
+ one occurrence of '%C' is allowed.) For example to use the develop-
ment/pre-release versions of latex, etc, which have names, 'latex-dev',
'pdflatex-dev', etc, you could use
-
-
- 6 November 2023 77
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
set_tex_cmds( '%C-dev %O %S' );
This results in $latex = 'latex-dev %O %S', etc. (The pre-release pro-
- grams latex-dev etc are provided in current distributions of TeXLive
+ grams latex-dev etc are provided in current distributions of TeXLive
and MiKTeX.)
Advanced configuration: Using latexmk with make
- This section is targeted only at advanced users who use the make pro-
+ This section is targeted only at advanced users who use the make pro-
gram for complex projects, as for software development, with the depen-
dencies specified by a Makefile.
- Now the basic task of latexmk is to run the appropriate programs to
- make a viewable version of a LaTeX document. However, the usual make
- program is not suited to this purpose for at least two reasons. First
+ Now the basic task of latexmk is to run the appropriate programs to
+ make a viewable version of a LaTeX document. However, the usual make
+ program is not suited to this purpose for at least two reasons. First
is that the use of LaTeX involves circular dependencies (e.g., via .aux
files), and these cannot be handled by the standard make program. Sec-
- ond is that in a large document the set of source files can change
- quite frequently, particularly with included graphics files; in this
- situation keeping a Makefile manually updated is inappropriate and er-
+ ond is that in a large document the set of source files can change
+ quite frequently, particularly with included graphics files; in this
+ situation keeping a Makefile manually updated is inappropriate and er-
ror-prone, especially when the dependencies can be determined automati-
cally. Latexmk solves both of these problems robustly.
- Thus for many standard LaTeX documents latexmk can be used by itself
- without the make program. In a complex project it simply needs to be
- suitably configured. A standard configuration would be to define cus-
- tom dependencies to make graphics files from their source files (e.g.,
- as created by the xfig program). Custom dependencies are latexmk's
+ Thus for many standard LaTeX documents latexmk can be used by itself
+ without the make program. In a complex project it simply needs to be
+ suitably configured. A standard configuration would be to define cus-
+ tom dependencies to make graphics files from their source files (e.g.,
+ as created by the xfig program). Custom dependencies are latexmk's
equivalent of pattern rules in Makefiles.
- Nevertheless there are projects for which a Makefile is appropriate,
+ Nevertheless there are projects for which a Makefile is appropriate,
+
+
+
+ 24 December 2023 79
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
and it is useful to know how to use latexmk from a Makefile. A typical
example would be to generate documentation for a software project. Po-
- tentially the interaction with the rest of the rules in the Makefile
+ tentially the interaction with the rest of the rules in the Makefile
could be quite complicated, for example if some of the source files for
a LaTeX document are generated by the project's software.
In this section, I give a couple of examples of how latexmk can be use-
- fully invoked from a Makefile. The examples use specific features of
- current versions of GNU make, which is the default on both linux and
+ fully invoked from a Makefile. The examples use specific features of
+ current versions of GNU make, which is the default on both linux and
OS-X systems. They may need modifications for other versions of make.
The simplest method is simply to delegate all the relevant tasks to la-
@@ -5137,45 +5238,33 @@
%.pdf : %.tex FORCE_MAKE
latexmk -pdf -dvi- -ps- $<
- (Note: the last line must be introduced by a tab for the Makefile to
- function correctly!) Naturally, if making try.pdf from its associated
- LaTeX file try.tex were the only task to be performed, a direct use of
-
-
-
- 6 November 2023 78
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
- latexmk without a Makefile would normally be better. The benefit of
- using a Makefile for a LaTeX document would be in a larger project,
+ (Note: the last line must be introduced by a tab for the Makefile to
+ function correctly!) Naturally, if making try.pdf from its associated
+ LaTeX file try.tex were the only task to be performed, a direct use of
+ latexmk without a Makefile would normally be better. The benefit of
+ using a Makefile for a LaTeX document would be in a larger project,
where lines such as the above would be only be a small part of a larger
Makefile.
The above example has a pattern rule for making a .pdf file from a .tex
- file, and it is defined to use latexmk in the obvious way. There is a
+ file, and it is defined to use latexmk in the obvious way. There is a
conventional default target named "all", with a prerequisite of
- try.pdf. So when make is invoked, by default it makes try.pdf. The
- only complication is that there may be many source files beyond
+ try.pdf. So when make is invoked, by default it makes try.pdf. The
+ only complication is that there may be many source files beyond
try.tex, but these aren't specified in the Makefile, so changes in them
- will not by themselves cause latexmk to be invoked. Instead, the pat-
- tern rule is equipped with a "phony" prerequisite FORCE_MAKE; this has
- the effect of causing the rule to be always out-of-date, so that 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
+ 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 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.
- But something better is needed in more complicated situations, for ex-
+ 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-
+ in the Makefile. To do this, one can use a Makefile like the follow-
ing:
TARGETS = document1.pdf document2.pdf
@@ -5183,6 +5272,18 @@
LATEXMK = latexmk -recorder -use-make -deps \
-e 'warn qq(In Makefile, turn off custom dependencies\n);' \
-e '@cus_dep_list = ();' \
+
+
+
+ 24 December 2023 80
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
-e 'show_cus_dep();'
all : $(TARGETS)
$(foreach file,$(TARGETS),$(eval -include $(DEPS_DIR)/$(file)P))
@@ -5194,64 +5295,64 @@
%.pdf : %.fig
fig2dev -Lpdf $< $@
- (Again, the lines containing the commands for the rules should be
+ (Again, the lines containing the commands for the rules should be
started with tabs.) This example was inspired by how GNU automake han-
dles automatic dependency tracking of C source files.
- After each run of latexmk, dependency information is put in a file in
- the .deps subdirectory. The Makefile causes these dependency files to
+ After each run of latexmk, dependency information is put in a file in
+ the .deps subdirectory. The Makefile causes these dependency files to
be read by make, which now has the full dependency information for each
- target .pdf file. To make things less trivial it is specificed that
- two files document1.pdf and document2.pdf are the targets. The depen-
+ target .pdf file. To make things less trivial it is specificed that
+ two files document1.pdf and document2.pdf are the targets. The depen-
dency files are .deps/document1.pdfP and .deps/document2.pdfP.
- There is now no need for the phony prerequisite for the rule to make
-
-
-
- 6 November 2023 79
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
+ There is now no need for the phony prerequisite for the rule to make
.pdf files from .tex files. But I have added a rule to make .pdf files
- from .fig files produced by the xfig program; these are commonly used
- for graphics insertions in LaTeX documents. Latexmk is arranged to
+ from .fig files produced by the xfig program; these are commonly used
+ for graphics insertions in LaTeX documents. Latexmk is arranged to
output a dependency file after each run. It is given the -recorder op-
- tion, which improves its detection of files generated during a run of
- pdflatex; such files should not be in the dependency list. The -e op-
- tions are used to turn off all custom dependencies, and to document
- this. Instead the -use-make is used to delegate the making of missing
+ tion, which improves its detection of files generated during a run of
+ pdflatex; such files should not be in the dependency list. The -e op-
+ tions are used to turn off all custom dependencies, and to document
+ this. Instead the -use-make is used to delegate the making of missing
files to make itself.
- Suppose in the LaTeX file there is a command \includegraphics{graph},
- and an xfig file "graph.fig" exists. On a first run, pdflatex reports
- a missing file, named "graph". Latexmk succeeds in making "graph.pdf"
+ Suppose in the LaTeX file there is a command \includegraphics{graph},
+ and an xfig file "graph.fig" exists. On a first run, pdflatex reports
+ a missing file, named "graph". Latexmk succeeds in making "graph.pdf"
by calling "make graph.pdf", and after completion of its work, it lists
"fig.pdf" among the dependents of the file latexmk is making. Then let
- "fig.fig" be updated, and then let make be run. Make first remakes
+ "fig.fig" be updated, and then let make be run. Make first remakes
"fig.pdf", and only then reruns latexmk.
- Thus we now have a method by which all the subsidiary processing is
+ Thus we now have a method by which all the subsidiary processing is
delegated to make.
- Escaping of characters in dependency lists: There are certain special
- characters that need to be escaped when names of files and directories
- containing them appear in a dependency list used by a make program.
+ Escaping of characters in dependency lists: There are certain special
+ characters that need to be escaped when names of files and directories
+ containing them appear in a dependency list used by a make program.
Generally, such special characters are best avoided.
- By default, latexmk does no escaping of this kind, and the user will
+ By default, latexmk does no escaping of this kind, and the user will
have to arrange to deal with the issue separately, if the relevant spe-
- cial characters are used. Note that the rules for escaping depend on
+ cial characters are used. Note that the rules for escaping depend on
which make program is used, and on its version.
- One special case is of spaces, since those are particularly prevalent,
- notably in standard choices of name for a user's home directory. So
- latexmk does provide an option to escape spaces. See the option
+
+
+
+ 24 December 2023 81
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
+ One special case is of spaces, since those are particularly prevalent,
+ notably in standard choices of name for a user's home directory. So
+ latexmk does provide an option to escape spaces. See the option
-deps_escape=... and the variable $deps_escape for details.
@@ -5258,11 +5359,11 @@
NON_ASCII CHARACTERS IN FILENAMES, RC FILES, ETC
Modern operating systems and file systems allow non-ASCII characters in
- the names of files and directories that encompass the full Unicode
+ the names of files and directories that encompass the full Unicode
range. Mostly, latexmk deals with these correctly. However, there are
- some situations in which there are problems, notably on Microsoft Win-
+ some situations in which there are problems, notably on Microsoft Win-
dows. Prior to version 4.77, latexmk had problems with non-ASCII file-
- names on Windows, even though there were no corresponding problems on
+ names on Windows, even though there were no corresponding problems on
macOS and Linux. These problems are corrected in the present version.
DETAILS TO BE FILLED IN
@@ -5273,48 +5374,49 @@
latex(1), bibtex(1), lualatex(1), pdflatex(1), xelatex(1).
-
-
- 6 November 2023 80
-
-
-
-
-
-LATEXMK(1) General Commands Manual LATEXMK(1)
-
-
BUGS (SELECTED)
Sometimes a viewer (gv) tries to read an updated .ps or .pdf file after
- its creation is started but before the file is complete. Work around:
+ its creation is started but before the file is complete. Work around:
manually refresh (or reopen) display. Or use one of the other preview-
ers and update methods.
- (The following isn't really a bug, but concerns features of preview-
- ers.) Preview continuous mode only works perfectly with certain pre-
- viewers: Xdvi on UNIX/Linux works for dvi files. Gv on UNIX/Linux
- works for both postscript and pdf. Ghostview on UNIX/Linux needs a
- manual update (reopen); it views postscript and pdf. Gsview under MS-
- Windows works for both postscript and pdf, but only reads the updated
- file when its screen is refreshed. Acroread under UNIX/Linux views
- pdf, but the file needs to be closed and reopened to view an updated
- version. Under MS-Windows, acroread locks its input file and so the
- pdf file cannot be updated. (Remedy: configure latexmk to use suma-
+ (The following isn't really a bug, but concerns features of preview-
+ ers.) Preview continuous mode only works perfectly with certain pre-
+ viewers: Xdvi on UNIX/Linux works for dvi files. Gv on UNIX/Linux
+ works for both postscript and pdf. Ghostview on UNIX/Linux needs a
+ manual update (reopen); it views postscript and pdf. Gsview under MS-
+ Windows works for both postscript and pdf, but only reads the updated
+ file when its screen is refreshed. Acroread under UNIX/Linux views
+ pdf, but the file needs to be closed and reopened to view an updated
+ version. Under MS-Windows, acroread locks its input file and so the
+ pdf file cannot be updated. (Remedy: configure latexmk to use suma-
trapdf instead.)
THANKS TO
- Authors of previous versions. Many users with their feedback, and es-
+ Authors of previous versions. Many users with their feedback, and es-
pecially David Coppit (username david at node coppit.org) who made many
- useful suggestions that contributed to version 3, and Herbert Schulz.
- (Please note that the e-mail addresses are not written in their stan-
+ useful suggestions that contributed to version 3, and Herbert Schulz.
+ (Please note that the e-mail addresses are not written in their stan-
dard form to avoid being harvested too easily.)
AUTHOR
- Current version, by John Collins (Version 4.81). Report bugs etc to
+ Current version, by John Collins (Version 4.82). Report bugs etc to
his e-mail (jcc8 at psu.edu).
- Released version can be obtained from CTAN:
- <http://www.ctan.org/pkg/latexmk/>, and from the author's website
+ Released version can be obtained from CTAN:
+
+
+
+ 24 December 2023 82
+
+
+
+
+
+LATEXMK(1) General Commands Manual LATEXMK(1)
+
+
+ <http://www.ctan.org/pkg/latexmk/>, and from the author's website
<https://www.cantab.net/users/johncollins/latexmk/>.
Modifications and enhancements by Evan McLean (Version 2.0)
Original script called "go" by David J. Musliner (RCS Version 3.2)
@@ -5341,6 +5443,36 @@
- 6 November 2023 81
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 24 December 2023 83
+
+
Modified: trunk/Master/texmf-dist/scripts/latexmk/latexmk.pl
===================================================================
--- trunk/Master/texmf-dist/scripts/latexmk/latexmk.pl 2023-12-26 21:02:15 UTC (rev 69220)
+++ trunk/Master/texmf-dist/scripts/latexmk/latexmk.pl 2023-12-26 21:04:28 UTC (rev 69221)
@@ -1,6 +1,8 @@
#!/usr/bin/env perl
use warnings;
+
+
## Copyright John Collins 1998-2023
## (username jcc8 at node psu.edu)
## (and thanks to David Coppit (username david at node coppit.org)
@@ -40,10 +42,14 @@
## 20 = probable bug
## or retcode from called program.
-$my_name = 'latexmk';
-$My_name = 'Latexmk';
-$version_num = '4.81';
-$version_details = "$My_name, John Collins, 6 Nov. 2023. Version $version_num";
+BEGIN {
+ # Make sure the following are available when printing diagnostics in BEGIN
+ # blocks.
+ $my_name = 'latexmk';
+ $My_name = 'Latexmk';
+ $version_num = '4.82';
+ $version_details = "$My_name, John Collins, 24 Dec. 2023. Version $version_num";
+}
use Config;
use File::Basename;
@@ -81,9 +87,25 @@
use Cwd "chdir"; # Ensure $ENV{PWD} tracks cwd.
use Digest::MD5;
-# **WARNING**: Don't import time; that overrides core function time(), and messes up
-# somethings
+our %HiRes_non_imports;
use Time::HiRes;
+BEGIN {
+ # Import some HiRes functions to override standard ones.
+ # However, Time::HiRes's documentation says that some of its functions
+ # may be unimplemented on some systems.
+ # So take precautions in case the ones I need aren't implemented.
+ # I must do the import in a BEGIN block, i.e., during compilation
+ # phase, else calls to time() etc get compiled to use std time(), i.e.,
+ # CORE::time(), instead of the HiRes versions.
+ %HiRes_non_imports = ();
+ foreach ( ( qw( time stat sleep ) ) ) {
+ if ( ! eval{ Time::HiRes->import($_); 1; } ) {
+ $HiRes_non_imports{$_} = 1;
+ warn "$My_name: Cannot import Time::HiRes::$_ on this system\n",
+ "$@";
+ }
+ }
+}
#################################################
#
@@ -365,6 +387,14 @@
# Use to limit number of (potentially) wrapped lines to combine into single line.
$max_log_construct = 600;
+# Whether to search for ^^ notation in log file for non-7-bit characters,
+# and convert to bytes. (Note: ^^ notation is produced by hilatex in
+# TeXLive 2023, and by pdflatex in MiKTeX 22.1 if no special option is
+# used (-enable-8bit-chars). (Also pdflatex in TeXLive 2023 (and earlier)
+# gives it if -translate-file=empty is used.)
+# Should also do same with aux files, but I've not done that yet. ????
+# fls file is always UTF-8.
+$conv_hathat = 1;
#########################################################################
## Default parsing and file-handling settings
@@ -483,10 +513,11 @@
$tex_distribution = '';
# List of known *latex rules:
-%possible_primaries = ( 'dvilualatex' => 'primary', 'latex' => 'primary',
+%possible_primaries = ( 'dvilualatex' => 'primary', 'hilatex' => 'primary',
+ 'latex' => 'primary',
'lualatex' => 'primary', 'pdflatex' => 'primary',
'xelatex' => 'primary' );
-&std_tex_cmds;
+std_tex_cmds();
# Possible code to execute by *latex before inputting source file.
# Not used by default.
@@ -493,6 +524,7 @@
$pre_tex_code = '';
## Default switches:
+$hilatex_default_switches = '';
$latex_default_switches = '';
$pdflatex_default_switches = '';
$dvilualatex_default_switches = '';
@@ -502,6 +534,7 @@
$xelatex_default_switches = '-no-pdf';
## Switch(es) to make them silent:
+$hilatex_silent_switch = '-interaction=batchmode';
$latex_silent_switch = '-interaction=batchmode';
$pdflatex_silent_switch = '-interaction=batchmode';
$dvilualatex_silent_switch = '-interaction=batchmode';
@@ -533,6 +566,15 @@
# Possible extensions for main output file of *latex:
%allowed_output_ext = ( ".dvi" => 1, ".xdv" => 1, ".pdf" => 1 );
+# Extensions etc, of special use by latexmk
+$save_error_suffix = '-SAVE-ERROR'; # Suffix to be added to filename, when an
+ # erroneous file is saved insted of being deleted.
+$fdb_ext = 'fdb_latexmk'; # Extension for the file for latexmk's
+ # file-database
+ # Make it long to avoid possible collisions.
+$fdb_ver = 4; # Version number for kind of fdb_file.
+
+
# Variables relevant to specifying cleanup.
# The first set of variables is intended to be user configurable.
#
@@ -564,7 +606,8 @@
# bbl files get special treatment because their deletion is conditional
# and because of the possibility of extra bibtex/biber rules with
# non-standard basename.
- at generated_exts = ( 'aux', 'bcf', 'fls', 'idx', 'ind', 'lof', 'lot',
+ at generated_exts = ( 'aux', 'bcf', 'bcf'.$save_error_suffix, 'fls',
+ 'idx', 'ind', 'lof', 'lot',
'out', 'run.xml', 'toc',
'blg', 'ilg', 'log',
'xdv'
@@ -576,7 +619,7 @@
# Extensions of files to be deleted by -C, but aren't normally included
# in the small clean up by -c. Analogous to @generated_exts and $clean_ext,
# except that pattern rules (with %R) aren't applied.
- at final_output_exts = ( 'dvi', 'dviF', 'ps', 'psF', 'pdf',
+ at final_output_exts = ( 'dvi', 'dviF', 'hnt', 'ps', 'psF', 'pdf',
'synctex', 'synctex.gz' );
$clean_full_ext = "";
@@ -725,6 +768,7 @@
# in case the values of $latex and/or $pdflatex change after an option
# is added.
@extra_dvilualatex_options = ();
+ at extra_hilatex_options = ();
@extra_latex_options = ();
@extra_pdflatex_options = ();
@extra_lualatex_options = ();
@@ -819,7 +863,7 @@
# file(s) being made: priority 'ps', 'pdf', 'dvi'
# Viewers. These are system dependent, so default to none:
-$pdf_previewer = $ps_previewer = $ps_previewer_landscape = $dvi_previewer = $dvi_previewer_landscape = "NONE";
+$pdf_previewer = $ps_previewer = $ps_previewer_landscape = $dvi_previewer = $dvi_previewer_landscape = $hnt_previewer = "NONE";
$dvi_update_signal = undef;
$ps_update_signal = undef;
@@ -918,9 +962,15 @@
# Latexmk does tests on whether a particular generated file, e.g., log or
# fls, has been generated on a current run of a rule, especially *latex, or
-# is leftover from previous runs. This is done by finding whether or not
-# the modification time of the file is at least as recent as the system
-# time at the start of the run. A file with a modification time
+# is leftover from previous runs. An expected file can fail to be
+# generated or generated in other than the expected place because of errors
+# or because of misconfiguration of latexmk. There are also files (notably
+# bcf files) that are generated or not according to the current set of
+# packages, options, etc used by a document.
+#
+# The test for whether a file was generated on the current run of a rule is
+# that the modification time of the file is at least as recent as the
+# system time at the start of the run. A file with a modification time
# significantly less than the time at the start of the run is presumably
# left over from a previous run and not generated in the currrent run. (An
# allowance is made in this comparison for the effects of granularity of
@@ -928,50 +978,63 @@
# earlier than the system time at which the file was last modified.)
#
# But generated files may be on a file system hosted by a server computer
-# that is different than the computer running latexmk. There may there may
-# be an offset between the time on the two computers; this can make it
-# appear that the generated files were made before the run. Most of the
-# time, this problem does not arise, since (a) typical usage of latexmk is
-# with a local file system, and (b) current-day computers and operating
-# systems have their time synchronized accurately with a time server.
+# that is different than the computer running latexmk. There may be an
+# offset between the time on the two computers; this can make it
+# incorrectly appear that the generated files were made before the
+# run. Most of the time, this problem does not arise, since (a) typical
+# usage of latexmk is with a local file system, and (b) current-day
+# computers and operating systems have their time synchronized accurately
+# with a time server. Difficulties are most acute with small documents
+# compiled on a fast computer, e.g., with sub-second compilation times.
#
-# But when latexmk sees symptoms of an excessive offset, it measures the
-# offset between the filesystem time and the system time. This involves
-# writing a temporary file, getting its modification time, and deleting
-# it. The following variables are used for this purpose.
-
+# When latexmk sees symptoms of an excessive offset, it measures the offset
+# between the filesystem time and the system time. This involves writing a
+# temporary file, getting its modification time, and deleting it. Then
+# when testing for whether a file was made on the current run or not, an
+# allowance is then made for the measured time offset between the two
+# computers.
#
-our $filetime_offset_measured = 0; # Measurement not yet done.
-our $filetime_offset = 0; # Filetime relative to system time.
-our $filetime_offset_report_threshold = 10; # Threshold beyond which filetime offsets
- # are reported; large offsets indicate
- # incorrect system time on at least one system.
-# The following variable gives the threshold for detection of left-over
-# file. It allows for (a) different granularity between system time and
-# filesystem time, (b) for some mismatch between file and system time.
-# Note that the making or not making of a file is controlled by the
-# state of the document being compiled and by latexmk's configuration.
-# So a file that is left over from a previous run and not overwritten
-# on the current run will have a file time at least many seconds less
-# than the current time, corresponding to the time scale for a human
-# run-edit-run cycle.
+# Note that typically an invocation of latexmk's processing of a document
+# occurs after some human action, e.g., editting a document or a
+# configuration file. So a file that is left over from a previous run and
+# not overwritten on the current run will have a file time at least many
+# seconds less than the current time, corresponding to the time scale for a
+# human run-edit-run cycle. So one does NOT have to particularly precise
+# about time differences.
#
-# Note that the making or not making of a file is controlled by the
-# state of the document being compiled and by latexmk's configuration.
-# So a file that is left over from a previous run and not overwritten
-# on the current run will have a file time at least many seconds less
-# than the current time, corresponding to the time scale for a human
-# run-edit-run cycle. So one does NOT have to tune this variable
-# precisely.
-#
-# Concerning granularity of file system
-# FAT file system: 2 sec granularity. Others 1 sec or less.
-# Perl CORE's mtime in stat: 1 sec.
-# Perl CORE's time(): 1 sec. Time::HiRes::time(): Much less than 1 sec.
+# Granularity of file system etc:
+# FAT file system: 2 sec granularity. Others 1 sec or often much less.
+#
+# Functions available to latexmk from Perl:
+# mtime from Perl's CORE::stat: 1 sec, but 2 sec on FAT file system;
+# mtime from Time_HiRes::stat: can be much less than 1 sec, if the
+# combination of Perl, the OS and the file system support it.
+# system time from CORE::time(): 1 sec;
+# system time from Time::HiRes::time(): Much less than 1 sec.
+# Variables controlling the assessment of time offset between file system
+# and computer:
+
our $filetime_causality_threshold = 5;
+ # This is the size of time differences below which latexmk doesn't
+ # worry. It allows for (a) different granularity between system time
+ # and filesystem time, (b) for a modest mismatch between file and system
+ # time. This allowance can be generous; it merely needs to be below the
+ # human time-scale for editing documents, reconfiguring (or
+ # misconfiguring) latexmk, etc.
+our $filetime_offset_measured = 0; # Measurement not yet done.
+our $filetime_offset = 0; # Filetime relative to system time.
+ # Assume zero to start (corresponding to
+ # local file system).
+ # Will be updated if necessary.
+our $filetime_offset_report_threshold = 10; # Threshold beyond which filetime offsets
+ # are reported at end of run; large
+ # offsets indicate incorrect system
+ # time on at least one system.
+
+
################################################################
################################################################
@@ -1008,6 +1071,7 @@
$ps_previewer_landscape = $ps_previewer;
$dvi_previewer = 'start %O %S';
$dvi_previewer_landscape = "$dvi_previewer";
+ $hnt_previewer = 'start %O %S';
# Viewer update methods:
# 0 => auto update: viewer watches file (e.g., gv)
# 1 => manual update: user must do something: e.g., click on window.
@@ -1020,6 +1084,7 @@
# specified by the variables $dvi_update_command,
# $ps_update_command, $pdf_update_command
$dvi_update_method = 1;
+ $hnt_update_method = 1;
$ps_update_method = 1;
$pdf_update_method = 3; # acroread locks the pdf file
}
@@ -1110,6 +1175,7 @@
$ps_previewer_landscape = $ps_previewer;
$dvi_previewer = "$start_NT %O %S";
$dvi_previewer_landscape = $dvi_previewer;
+ $hnt_previewer = "$start_NT %O %S";
# Viewer update methods:
# 0 => auto update: viewer watches file (e.g., gv)
# 1 => manual update: user must do something: e.g., click on window.
@@ -1119,6 +1185,7 @@
# 3 => viewer can't update, because it locks the file and the file
# cannot be updated. (acroread under MSWIN)
$dvi_update_method = 1;
+ $hnt_update_method = 1;
$ps_update_method = 1;
$pdf_update_method = 3; # acroread locks the pdf file
}
@@ -1129,6 +1196,7 @@
$pdf_previewer = q[sh -c 'start %S'];
$ps_previewer = q[sh -c 'start %S'];
$dvi_previewer = q[sh -c 'start %S'];
+ $hnt_previewer = q[sh -c 'start %S'];
$ps_previewer_landscape = $ps_previewer;
$dvi_previewer_landscape = "$dvi_previewer";
}
@@ -1253,6 +1321,8 @@
# does not deal with changed dvi files, as far as I can see.
$pdf_previewer = 'open %S';
$pdf_update_method = 1; # manual
+ $hnt_previewer = 'open %S';
+ $hnt_update_method = 1; # manual
$dvi_previewer = $dvi_previewer_landscape = 'NONE';
$ps_previewer = $ps_previewer_landscape = 'NONE';
# Others
@@ -1310,11 +1380,6 @@
# This variable is obsolete, and only in here for
# backward compatibility.
-$fdb_ext = 'fdb_latexmk'; # Extension for the file for latexmk's
- # file-database
- # Make it long to avoid possible collisions.
-$fdb_ver = 4; # Version number for kind of fdb_file.
-
$jobname = ''; # Jobname: as with current tex, etc indicates
# basename of generated files. Defined so
# that --jobname=STRING on latexmk's command
@@ -1347,7 +1412,10 @@
$max_logfile_warnings = 7; # Max. # number of log file warnings to report
$rc_report = 1; # Whether to report on rc files read
$aux_out_dir_report = 0; # Whether to report on aux_dir & out_dir after
- # initialization and normalization
+ # initialization and normalization.
+ # When $aux_out_dir_report is set to 2, latexmk
+ # does no further processing after the report of
+ # the aux and out directories.
$kpsewhich_show = 0; # Show calls to and results from kpsewhich
$landscape_mode = 0; # default to portrait mode
@@ -1380,7 +1448,7 @@
# Which kinds of file do I have requests to make?
-our ($dvi_mode, $pdf_mode, $postscript_mode, $xdv_mode,
+our ($dvi_mode, $hnt_mode, $pdf_mode, $postscript_mode, $xdv_mode,
$cleanup_mode, $force_mode, $go_mode, $landscape_mode, $preview_mode, $preview_continuous_mode, $printout_mode );
# If no requests at all are made, then I will make dvi file
# If particular requests are made then other files may also have to be
@@ -1390,6 +1458,7 @@
# 0: no request for dvi file
# 1: use latex to make dvi file
# 2: use dvilualatex to make dvi file
+$hnt_mode = 0; # No hnt file requested
$postscript_mode = 0; # No postscript file requested
$pdf_mode = 0; # No pdf file requested to be made by pdflatex
# Possible values:
@@ -1402,6 +1471,7 @@
$xdv_mode = 0; # No xdv file requested
$view = 'default'; # Default preview is of highest of dvi, ps, pdf
+$min_sleep_time = 0.01; # Minimum non-zero sleep time
$sleep_time = 2; # time to sleep b/w checks for file changes in -pvc mode
$banner = 0; # Non-zero if we have a banner to insert
$banner_scale = 220; # Original default scale
@@ -1460,8 +1530,8 @@
# Whether times computed are clock times (HiRes) since Epoch, or are
# processing times for this process and child processes, as reported by
# times(). Second is the best, if accurate. But on MSWin32, times()
-# appears not to included subprocess times, so we use clock time instead.
-our $times_are_clock = ($^O eq "MSWin32" );
+# appears not to include subprocess times, so we use clock time instead.
+our $times_are_clock = ($^O eq "MSWin32" ? 1 : 0);
# Data for 1 run and global (ending in '0'):
@@ -1830,6 +1900,8 @@
# of the current rule. That must not trigger
# another run.
# The values for the hash are currently unused, only the keys.
+ # (Some packages that exhibit the
+ # rewrite-before-read behavior: pythontex, showexpl.)
# 4: {Hash source_rule -> last_pass }
# This lists rules that are to be considered source
# rules for the current rule, separately from the
@@ -1861,7 +1933,17 @@
# way is that the source_rule passes files (or
# other information) to the current rule, and that
# the current rule is to be rerun whenever the
- # source_rule has been run.
+ # source_rule has been run.
+ # 5: {Hash keys -> values}
+ # Used for any extra information needed for a specific
+ # rule. The first one I'll set up is for cached
+ # datasource information for the biber rule. The
+ # key is 'bcf_datasources', and the value is a
+ # reference to a hash mapping filename
+ # specifications in the bcf file to actual files
+ # (if found).
+ # The aim of this item is for flexible
+ # rule-dependent add-ons.
%fdb_current = (); # Hash of information for all files used.
# It maps filename to a reference to an array
@@ -2037,9 +2119,11 @@
$dependents_list = 1;
}
elsif (/^-diagnostics/) { $diagnostics = 1; }
+ elsif (/^-dir-report-only$/) { $aux_out_dir_report = 2; }
elsif (/^-dir-report$/) { $aux_out_dir_report = 1; }
elsif (/^-dir-report-$/) { $aux_out_dir_report = 0; }
elsif (/^-dvi$/) { $dvi_mode = 1;
+ $hnt_mode = 0;
if ( ($pdf_mode != 2) && ($pdf_mode != 3) ) {
# if pdf_mode is not via dvi or pdf, turn it off
$pdf_mode = 0;
@@ -2046,6 +2130,7 @@
}
}
elsif (/^-dvilua$/) { $dvi_mode = 2;
+ $hnt_mode = 0;
if ( ($pdf_mode != 2) && ($pdf_mode != 3) ) {
# if pdf_mode is not via dvi or pdf, turn it off
$pdf_mode = 0;
@@ -2068,6 +2153,9 @@
$go_mode = 3;
}
elsif ( /^-h$/ || /^-help$/ ) { &print_help; exit;}
+ elsif (/^-hnt$/) { $hnt_mode = 1;
+ $dvi_mode = $postscript_mode = $pdf_mode = 0;
+ }
elsif (/^-jobname=(.*)$/) {
$jobname = $1;
}
@@ -2077,6 +2165,7 @@
$pdf_mode = 0;
$postscript_mode = 0;
$dvi_mode = 1;
+ $hnt_mode = 0;
}
elsif (/^-latex=(.*)$/) {
$latex = $1;
@@ -2094,7 +2183,7 @@
{ $silence_logfile_warnings = 1; }
elsif ( /^-lualatex$/ || /^-pdflualatex$/ ) {
$pdf_mode = 4;
- $dvi_mode = $postscript_mode = 0;
+ $dvi_mode = $hnt_mode = $postscript_mode = 0;
}
# See below for -lualatex=...
# See above for -M
@@ -2130,6 +2219,7 @@
my $format = $1;
if ($format eq 'dvi' ) {
$dvi_mode = 1;
+ $hnt_mode = 0;
if ( ($pdf_mode != 2) && ($pdf_mode != 3) ) {
# if pdf_mode is not via dvi or pdf, turn it off
$pdf_mode = 0;
@@ -2137,7 +2227,7 @@
}
elsif ($format eq 'pdf' ) {
$pdf_mode = 1;
- $dvi_mode = $postscript_mode = 0;
+ $dvi_mode = $hnt_mode = $postscript_mode = 0;
}
else {
warn "$My_name: unknown format in option '$_'\n";
@@ -2149,16 +2239,16 @@
$preview_mode = 0;
}
elsif (/^-p-$/) { $printout_mode = 0; }
- elsif (/^-pdf$/) { $pdf_mode = 1; $dvi_mode = $postscript_mode = 0; }
+ elsif (/^-pdf$/) { $pdf_mode = 1; $dvi_mode = $hnt_mode = $postscript_mode = 0; }
elsif (/^-pdf-$/) { $pdf_mode = 0; }
- elsif (/^-pdfdvi$/){ $pdf_mode = 3; }
- elsif (/^-pdflua$/){ $pdf_mode = 4; $dvi_mode = $postscript_mode = 0; }
- elsif (/^-pdfps$/) { $pdf_mode = 2; }
- elsif (/^-pdfxe$/) { $pdf_mode = 5; $dvi_mode = $postscript_mode = 0; }
+ elsif (/^-pdfdvi$/){ $pdf_mode = 3; $hnt_mode = 0; }
+ elsif (/^-pdflua$/){ $pdf_mode = 4; $dvi_mode = $hnt_mode = $postscript_mode = 0; }
+ elsif (/^-pdfps$/) { $pdf_mode = 2; $hnt_mode = 0; }
+ elsif (/^-pdfxe$/) { $pdf_mode = 5; $dvi_mode = $hnt_mode = $postscript_mode = 0; }
elsif (/^-pdflatex$/) {
$pdflatex = "pdflatex %O %S";
$pdf_mode = 1;
- $dvi_mode = $postscript_mode = 0;
+ $dvi_mode = $hnt_mode = $postscript_mode = 0;
}
elsif (/^-pdflatex=(.*)$/) {
$pdflatex = $1;
@@ -2246,6 +2336,7 @@
elsif (/^-verbose$/) { $silent = 0; }
elsif (/^-view=default$/) { $view = "default";}
elsif (/^-view=dvi$/) { $view = "dvi";}
+ elsif (/^-view=hnt$/) { $view = "hnt";}
elsif (/^-view=none$/) { $view = "none";}
elsif (/^-view=ps$/) { $view = "ps";}
elsif (/^-view=pdf$/) { $view = "pdf"; }
@@ -2254,7 +2345,7 @@
elsif (/^-xdv-$/) { $xdv_mode = 0; }
elsif ( /^-xelatex$/ || /^-pdfxelatex$/ ) {
$pdf_mode = 5;
- $dvi_mode = $postscript_mode = 0;
+ $dvi_mode = $hnt_mode = $postscript_mode = 0;
}
# See above for -xelatex=...
elsif (/^-e$/) {
@@ -2318,6 +2409,7 @@
)
{
push @extra_dvilualatex_options, $original;
+ push @extra_hilatex_options, $original;
push @extra_latex_options, $original;
push @extra_pdflatex_options, $original;
push @extra_lualatex_options, $original;
@@ -2490,6 +2582,7 @@
# Add common options
add_option( $dvilualatex_default_switches, \$dvilualatex );
+add_option( $hilatex_default_switches, \$hilatex );
add_option( $latex_default_switches, \$latex );
add_option( $pdflatex_default_switches, \$pdflatex );
add_option( $lualatex_default_switches, \$lualatex );
@@ -2496,6 +2589,7 @@
add_option( $xelatex_default_switches, \$xelatex );
foreach (@extra_dvilualatex_options) { add_option( $_, \$dvilualatex ); }
+foreach (@extra_hilatex_options) { add_option( $_, \$hilatex ); }
foreach (@extra_latex_options) { add_option( $_, \$latex ); }
foreach (@extra_pdflatex_options) { add_option( $_, \$pdflatex ); }
foreach (@extra_lualatex_options) { add_option( $_, \$lualatex ); }
@@ -2527,6 +2621,7 @@
if ( $silent ) {
add_option( "$dvilualatex_silent_switch", \$dvilualatex );
+ add_option( "$hilatex_silent_switch", \$hilatex );
add_option( "$latex_silent_switch", \$latex );
add_option( "$pdflatex_silent_switch", \$pdflatex );
add_option( "$lualatex_silent_switch", \$lualatex );
@@ -2540,7 +2635,7 @@
}
if ( $recorder ) {
- add_option( "-recorder", \$dvilualatex, \$latex, \$pdflatex, \$lualatex, \$xelatex );
+ add_option( "-recorder", \$dvilualatex, \$hilatex, \$latex, \$pdflatex, \$lualatex, \$xelatex );
}
# If the output and/or aux directories are specified, fix the *latex
@@ -2552,20 +2647,21 @@
if ( $jobname ne '' ) {
# Since $jobname may include placeholder(s), put %R placeholder
# in option, and let %R be substituted by actual jobname at runtime.
- add_option( "--jobname=%R", \$dvilualatex, \$latex, \$lualatex, \$pdflatex, \$xelatex );
+ add_option( "--jobname=%R", \$dvilualatex, \$hilatex, \$latex, \$lualatex, \$pdflatex, \$xelatex );
}
# Make sure we make the kind of file we want to view:
if ( ($view eq 'dvi') && ($dvi_mode == 0) ) { $dvi_mode = 1; }
-if ($view eq 'ps') { $postscript_mode = 1; }
+if ( ($view eq 'hnt') && ($hnt_mode == 0) ) { $hnt_mode = 1; }
+if ( $view eq 'ps' ) { $postscript_mode = 1; }
if ( ($view eq 'pdf') && ($pdf_mode == 0) ) {
$pdf_mode = 1;
}
# Make sure that we make something if all requests are turned off
-unless ( $dvi_mode || $pdf_mode || $postscript_mode || $printout_mode || $xdv_mode ) {
+unless ( $dvi_mode || $hnt_mode || $pdf_mode || $postscript_mode || $printout_mode || $xdv_mode ) {
print "No specific requests made, so using default for $invoked_name.\n";
- ($dvi_mode, $postscript_mode, $pdf_mode, $xdv_mode )
+ ($dvi_mode, $hnt_mode, $postscript_mode, $pdf_mode, $xdv_mode )
= @{$compilation_defaults{$invoked_name}};
}
@@ -2576,8 +2672,9 @@
# that was requested by user.
# No explicit request means view dvi.
$view = "dvi";
+ if ( $hnt_mode ) { $view = "hnt"; }
+ if ( $pdf_mode ) { $view = "pdf"; }
if ( $postscript_mode ) { $view = "ps"; }
- if ( $pdf_mode ) { $view = "pdf"; }
}
# Determine requests.
@@ -2648,7 +2745,7 @@
if ( $preview_continuous_mode || $preview_mode ) { $one_time{'view'} = 1; }
$can_switch = $allow_switch;
-if ( $dvi_mode || $postscript_mode || $xdv_mode
+if ( $dvi_mode || $hnt_mode || $postscript_mode || $xdv_mode
|| ( $printout_mode && ($print_type eq 'ps') || ($print_type eq 'dvi') )
|| ( ($preview_mode || $preview_continuous_mode) && ( ($view eq 'ps') || ($view eq 'dvi') ) )
) {
@@ -2669,17 +2766,15 @@
add_option( "$dvips_pdf_switch", \$dvips );
}
-# Note sleep has granularity of 1 second.
-# Sleep periods 0 < $sleep_time < 1 give zero delay,
-# which is probably not what the user intended.
-# Sleep periods less than zero give infinite delay
+# Note that 100% CPU usage may not be terribly bad with a multi-core CPU,
+# and an SSD, especially when the OS caches file metadata reliably.
if ( $sleep_time == 0 ) {
warn "$My_name: sleep_time was configured to zero.\n",
" Do you really want to do this? It can give 100% CPU usage.\n";
}
-elsif ( $sleep_time < 1 ) {
- warn "$My_name: Correcting nonzero sleep_time of less than 1 sec to 1 sec.\n";
- $sleep_time = 1;
+elsif ( $sleep_time < $min_sleep_time ) {
+ warn "$My_name: Correcting nonzero sleep_time of less than $min_sleep_time sec to $min_sleep_time sec.\n";
+ $sleep_time = $min_sleep_time;
}
@@ -2779,6 +2874,7 @@
local $out_dir = $out_dir;
local $dvilualatex = $dvilualatex;
+ local $hilatex = $hilatex;
local $latex = $latex;
local $lualatex = $lualatex;
local $pdflatex = $pdflatex;
@@ -2992,8 +3088,12 @@
}
if ( !$force_mode ) {
warn
- "$My_name: If appropriate, the -f option can be used to get latexmk\n",
- " to try to force complete processing.\n";
+ "$My_name: Sometimes, the -f option can be used to get latexmk\n",
+ " to try to force complete processing.\n",
+ " But normally, you will need to correct the file(s) that caused the\n",
+ " error, and then rerun latexmk.\n",
+ " In some cases, it is best to clean out generated files before rerunning\n",
+ " latexmk after you've corrected the files.\n";
}
exit 12;
}
@@ -3028,7 +3128,7 @@
# Initialize timing for one run.
@timings1 = ();
$processing_time1 = processing_time();
- $clock1 = Time::HiRes::time();
+ $clock1 = time();
}
############################
@@ -3055,7 +3155,7 @@
", of which invoked processes = $invoked_time, other = ",
sprintf( '%.2f', $processing_time-$invoked_time ), ".\n";
print "Elapsed clock time = ",
- sprintf( '%.2f', Time::HiRes::time()-$clock1 ), ".\n";
+ sprintf( '%.2f', time()-$clock1 ), ".\n";
print "Number of rules run = ", 1+$#timings1, "\n";
}
@@ -3315,6 +3415,9 @@
print "$My_name: Cwd: '", good_cwd(), "'\n";
print "$My_name: Normalized aux dir and out dir: '$aux_dir', '$out_dir'\n";
print "$My_name: and combining forms: '$aux_dir1', '$out_dir1'\n";
+ if ($aux_out_dir_report == 2) {
+ exit 0;
+ }
}
} #END normalize_aux_out_ETC
@@ -3338,13 +3441,13 @@
# the relevant files (.pdf, .ps, .dvi, .xdv, .fls to the output
# directory after running *latex.
add_option( "-output-directory=%V",
- \$dvilualatex, \$latex, \$pdflatex, \$lualatex, \$xelatex );
+ \$dvilualatex, \$hilatex, \$latex, \$pdflatex, \$lualatex, \$xelatex );
}
}
else {
if ( $out_dir && ($out_dir ne '.') ) {
add_option( "-output-directory=%W",
- \$dvilualatex, \$latex, \$pdflatex, \$lualatex, \$xelatex );
+ \$dvilualatex, \$hilatex, \$latex, \$pdflatex, \$lualatex, \$xelatex );
}
if ( $aux_dir ne $out_dir ) {
# N.B. If $aux_dir and $out_dir are the same, then the
@@ -3351,7 +3454,7 @@
# -output-directory option is sufficient, especially because
# the -aux-directory exists only in MiKTeX, not in TeXLive.
add_option( "-aux-directory=%V",
- \$dvilualatex, \$latex, \$pdflatex, \$lualatex, \$xelatex );
+ \$dvilualatex, \$hilatex, \$latex, \$pdflatex, \$lualatex, \$xelatex );
}
}
} #END set_aux_out_options
@@ -3360,7 +3463,7 @@
sub fix_cmds {
# If commands do not have placeholders for %S etc, put them in
- foreach ($latex, $lualatex, $pdflatex, $xelatex, $lpr, $lpr_dvi, $lpr_pdf,
+ foreach ($hilatex, $latex, $lualatex, $pdflatex, $xelatex, $lpr, $lpr_dvi, $lpr_pdf,
$pdf_previewer, $ps_previewer, $ps_previewer_landscape,
$dvi_previewer, $dvi_previewer_landscape,
$kpsewhich
@@ -3414,10 +3517,13 @@
# (The rule database may get overridden/extended after the fdb_latexmk
# file is read, and after running commands to adjust to dependencies
# determined from document.
+
%rule_db = ();
%target_rules = ();
%target_files = ();
-
+ %actives = ();
+ %from_rules = ();
+
local %rule_list = ();
&rdb_set_rule_templates;
@@ -3474,10 +3580,12 @@
elsif ($pdf_mode == 4) { $current_primary = 'lualatex'; }
elsif ($pdf_mode == 5) { rdb_activate( 'xdvipdfmx' ); $current_primary = 'xelatex'; }
if ($dvi_mode == 2) { $current_primary = 'dvilualatex'; }
+ if ($hnt_mode) { $current_primary = 'hilatex'; }
rdb_activate( $current_primary );
if ($dvi_mode) { $target_files{$dvi_final} = 1; }
+ if ($hnt_mode) { $target_files{$hnt_final} = 1; }
if ($postscript_mode) { $target_files{$ps_final} = 1; }
if ($pdf_mode) { $target_files{$pdf_final} = 1; }
if ($xdv_mode) { $target_files{$xdv_final} = 1; }
@@ -3518,7 +3626,7 @@
my $viewer_update_signal = undef;
my $viewer_update_command = undef;
- if ( ($view eq 'dvi') || ($view eq 'pdf') || ($view eq 'ps') ) {
+ if ( ($view eq 'dvi') || ($view eq 'hnt') || ($view eq 'pdf') || ($view eq 'ps') ) {
$view_file = ${$view.'_final'};
$viewer = ${$view.'_previewer'};
$viewer_update_method = ${$view.'_update_method'};
@@ -3532,6 +3640,7 @@
%rule_list = (
'dvilualatex' => [ 'primary', "$dvilualatex", '', "%T", $dvi_name, "%R", 1, [$aux_main, $log_name], [$aux_main] ],
+ 'hilatex' => [ 'primary', "$hilatex", '', "%T", $hnt_name, "%R", 1, [$aux_main, $log_name], [$aux_main] ],
'latex' => [ 'primary', "$latex", '', "%T", $dvi_name, "%R", 1, [$aux_main, $log_name], [$aux_main] ],
'lualatex' => [ 'primary', "$lualatex", '', "%T", $pdf_name, "%R", 1, [$aux_main, $log_name], [$aux_main] ],
'pdflatex' => [ 'primary', "$pdflatex", '', "%T", $pdf_name, "%R", 1, [$aux_main, $log_name], [$aux_main] ],
@@ -3770,7 +3879,7 @@
my @files_to_delete = ();
@dirs = ($aux_dir1);
if ($out_dir1 ne $aux_dir1) { push @dirs, $out_dir1; }
-
+
push @files_to_delete, &get_small_cleanup;
if ($kind == 1) {
foreach my $dir1 (@dirs) {
@@ -3785,6 +3894,8 @@
# sort deletes contents of directory before attempting to delete the
# directory:
unlink_or_move( reverse sort @files_to_delete );
+
+
# If the fdb file (or log, fls and/or aux files) exist, it/they will have
# been used to make a changed rule database. But a cleanup implies
@@ -4188,7 +4299,7 @@
$quell_uptodate_msgs = 1;
- if ( ($view eq 'dvi') || ($view eq 'pdf') || ($view eq 'ps') ) {
+ if ( ($view eq 'dvi') || ($view eq 'hnt') || ($view eq 'pdf') || ($view eq 'ps') ) {
print "Viewing $view\n";
}
elsif ( $view eq 'none' ) {
@@ -4579,7 +4690,7 @@
sub traceback {
# Call: traceback()
# or traceback( message )
- # NOT &traceback!!!
+ # NOT &traceback, normally!!!
my $msg = shift;
if ($msg) { warn "$msg\n"; }
warn "Traceback:\n";
@@ -4676,7 +4787,10 @@
" and turn on showing of dependency list\n",
" -dF <filter> - Filter to apply to dvi file\n",
" -dir-report - Before processing a tex file, report aux and out dir settings\n",
- " -dir-report- - Before processing a tex file, do not report aux and out dir settings\n",
+ " -dir-report- - Before processing a tex file, do not report aux and out dir\n",
+ " settings\n",
+ " -dir-report-only - Report aux and out dir settings after initialization\n",
+ " and previous option processing, and then stop\n",
" -dvi - generate dvi by latex\n",
" -dvilua - generate dvi by dvilualatex\n",
" -dvi- - turn off required dvi\n",
@@ -4695,6 +4809,7 @@
" -g - process at least one run of all rules\n",
" -g- - Turn off -g and -gg\n",
" -h - print help\n",
+ " -hnt - generate hnt by hilatex\n",
" -help - print help\n",
" -indexfudge or -makeindexfudge - change directory to output directory when running makeindex\n",
" -indexfudge- or -makeindexfudge- - don't change directory when running makeindex\n",
@@ -4795,6 +4910,7 @@
" -version - display program version\n",
" -view=default - viewer is default (dvi, ps, pdf)\n",
" -view=dvi - viewer is for dvi\n",
+ " -view=hnt - viewer is for hnt\n",
" -view=none - no viewer is used\n",
" -view=ps - viewer is for ps\n",
" -view=pdf - viewer is for pdf\n",
@@ -4823,6 +4939,7 @@
sub print_commands {
print "Commands used by $my_name:\n",
+ " To run hilatex, I use \"$hilatex\"\n",
" To run latex, I use \"$latex\"\n",
" To run pdflatex, I use \"$pdflatex\"\n",
" To run dvilualatex, I use \"$dvilualatex\"\n",
@@ -4844,6 +4961,7 @@
" To view a dvi file, I use \"$dvi_previewer\"\n",
" To view a dvi file in landscape format, ",
"I use \"$dvi_previewer_landscape\"\n",
+ " To view an hnt file, I use \"$hnt_previewer\"\n",
" To print a ps file, I use \"$lpr\"\n",
" To print a dvi file, I use \"$lpr_dvi\"\n",
" To print a pdf file, I use \"$lpr_pdf\"\n",
@@ -4865,44 +4983,147 @@
} #END view_file_via_temporary
#************************************************************
-#### Tex-related utilities
+#### Tex-related utilities #######################
+
#**************************************************
+sub after_biber {
+ # Analyze results of biber run, take appropriate actions on dependencies.
+ # Assumes rule context for biber
+ # Call
+ # after_biber( \$return ),
+ # where $return is code returned by running of biber (maybe modified by
+ # caller, which is normally rdb_run1). Can adjust its value to provoke
+ # better diagnosis of results of run to caller.
+ use strict;
+ # Rule variables used:
+ our ( $rule, $Pbase, $Pdest, $PHextra, $Plast_message, $Plast_result,
+ $Pout_of_date, $Psource, $PHsource );
+ # Global variables used
+ our ( %current_primaries, $diagnostics, $My_name, $save_error_suffix,
+ $silent );
+ my $Preturn = $_[0];
+ my @biber_datasource = ( );
+ my @biber_remote = ();
+ my @warnings = ();
+ my $add_bcf_datasources = 0;
+
+ my $retcode = check_biber_log( $$Pbase, \@biber_datasource, \@biber_remote );
+ if ($$Preturn) {
+ print
+ "$My_name: Error return from '$rule'\n",
+ "I will add to its source list, anything cached from analysis of bcf file.\n";
+ $add_bcf_datasources = 1;
+ }
+ if ( ! -e $$Psource ) {
+ $retcode = 10;
+ if (!$silent) {
+ print "Source '$$Psource' for '$rule' doesn't exist,\n",
+ "so I'll force *latex to run to try and make it.\n";
+ }
+ rdb_for_some( [keys %current_primaries], sub{ $$Pout_of_date = 1; } );
+ }
+ rdb_set_source_here( @biber_datasource, $$Psource );
+
+ if ($retcode == 6) {
+ # Missing control file. Need to remake it (if possible)
+ # Don't treat missing bbl file as error.
+ print "$My_name: bibtex control file missing. Since that can\n",
+ " be recreated, I'll try to do so.\n";
+ $$Preturn = -2;
+ rdb_for_some( [keys %current_primaries], sub{ $$Pout_of_date = 1; } );
+ }
+ elsif ($retcode == 4) {
+ $$Plast_result = 2;
+ $$Plast_message = "Could not find all biber source files for '$$Pbase'";
+ push @warnings, "Not all biber source files found for '$$Pbase'";
+ }
+ elsif ($retcode == 3) {
+ $$Plast_result = 2;
+ $$Plast_message = "Could not open biber log file for '$$Pbase'";
+ $add_bcf_datasources = 1;
+ push @warnings, $$Plast_message;
+ }
+ elsif ($retcode == 2) {
+ $$Plast_message = "Biber errors: See file '$$Pbase.blg'";
+ push @warnings, $$Plast_message;
+ }
+ elsif ($retcode == 1) {
+ push @warnings, "Biber warnings for '$$Pbase'";
+ }
+ elsif ($retcode == 11) {
+ $$Plast_message = "Biber: malformed bcf file '$$Psource'";
+ push @warnings, $$Plast_message;
+ my $save_bcf = "$$Psource$save_error_suffix";
+ warn "$My_name: biber found malformed bcf file '$$Psource'.\n",
+ " I'll delete any bbl file '$$Pdest', and\n",
+ " rename the bcf file to '$save_bcf'\n";
+ # Malformed bcf file is a downstream consequence, normally,
+ # of an error in *latex run.
+ # Current version of biber deletes bbl file.
+ # Older versions (pre-2016) made an incorrect bbl file, which
+ # tended to cause latex errors, and give a self-perpetuating error.
+ # Ensure the bbl file doesn't exist.
+ # I could delete the bcf file, since it is not usable. But in
+ # non-trivial cases, the user may want to examine the file, so
+ # I'll rename it instead. (Trivial common case: *latex exited
+ # early because of an error, and the resulting bcf file is
+ # incomplete. I should have deleted the file after the error
+ # run of *latex, since there is then no value in the bcf for
+ # diagnostics.)
+ unlink $$Pdest;
+ rename $$Psource, $save_bcf;
+ }
+ if ($add_bcf_datasources) {
+ my $PA_bcf_datasources = $$PHextra{bcf_datasources};
+ if ( ref($PA_bcf_datasources) eq 'ARRAY' ) {
+ rdb_ensure_files_here( @$PA_bcf_datasources );
+ }
+ }
+} #END after_biber
+
+#**************************************************
+
sub check_biber_log {
# Check for biber warnings, and report source files.
- # Usage: check_biber_log( base_of_biber_run, \@biber_datasource )
+ # Usage: check_biber_log( base_of_biber_run, \@datasource, \@remote )
+ # I use a hash for the collection of significant warnings. It maps
+ # categories of warnings to array references (or c.) to allow
+ # flexibility in what I report.
+ # (Return codes compatible with check_bibtex_log, but only used when applicable.)
# return 0: OK;
# 1: biber warnings;
# 2: biber errors;
# 3: could not open .blg file;
# 4: failed to find one or more source files, except for bibfile;
- # 5: failed to find bib file;
- # 6: missing file, one of which is control file
- # 10: only error is missing \citation commands.
+ # 6: missing file;
# 11: Malformed bcf file (normally due to error in pdflatex run)
- # Side effect: add source files @biber_datasource
- # N.B. @biber_datasource is already initialized by caller.
+ # Side effect: add source files to @datasource
+ # N.B. @datasource is already initialized by caller.
# So do **not** initialize it here.
- my $base = $_[0];
- my $Pbiber_datasource = $_[1];
+ use strict;
+ # Global variables used
+ our ($My_name, $silent);
+
+ my ($base, $PAdatasource, $PAremote ) = @_;
my $blg_name = "$base.blg";
open( my $blg_file, "<", $blg_name )
or return 3;
my $have_warning = 0;
my $have_error = 0;
- my $missing_citations = 0;
my $no_citations = 0;
my $error_count = 0; # From my counting of error messages
my $warning_count = 0; # From my counting of warning messages
# The next two occur only from biber
- my $bibers_error_count = 0; # From biber's counting of errors
- my $bibers_warning_count = 0; # From biber's counting of warnings
+ my $biber_error_count = 0; # From biber's counting of errors
+ my $biber_warning_count = 0; # From biber's counting of warnings
my $not_found_count = 0;
my $control_file_missing = 0;
my $control_file_malformed = 0;
- my %remote = (); # List of extensions of remote files
my @not_found = (); # Files, normally .bib files, not found.
+ my @missing_citations = ();
+
while (<$blg_file>) {
$_ = utf8_to_mine($_);
if (/> WARN /) {
@@ -4910,7 +5131,9 @@
$have_warning = 1;
$warning_count ++;
}
- elsif (/> (FATAL|ERROR) /) {
+ # Note that WARN is not exclusive with some of the following,
+ # so we can't use elsif here
+ if (/> (FATAL|ERROR) /) {
print "Biber error: $_";
if ( /> (FATAL|ERROR) - Cannot find file '([^']+)'/ #'
|| /> (FATAL|ERROR) - Cannot find '([^']+)'/ ) { #'
@@ -4930,16 +5153,11 @@
else {
$have_error = 1;
$error_count ++;
- if ( /> (FATAL|ERROR) - The file '[^']+' does not contain any citations!/ ) { #'
- $no_citations++;
- }
}
}
elsif ( /> INFO - Data source '([^']*)' is a remote BibTeX data source - fetching/
){
- my $spec = $1;
- my ( $base, $path, $ext ) = fileparseA( $spec );
- $remote{$ext} = 1;
+ push @$PAremote, $1;
}
elsif ( /> INFO - Found .* '([^']+)'\s*$/
|| /> INFO - Found '([^']+)'\s*$/
@@ -4946,10 +5164,11 @@
|| /> INFO - Reading '([^']+)'\s*$/
|| /> INFO - Processing .* file '([^']+)'.*$/
|| /> INFO - Config file is '([^']+)'.*$/
+ || /> WARN - Data source .*'([^']+)'.*$/
) {
my $file = $1;
my ( $base, $path, $ext ) = fileparseA( $file );
- if ($remote{$ext} && ( $base =~ /^biber_remote_data_source/ ) && 1) {
+ if ( $base =~ /^biber_remote_data_source/ ) {
# Ignore the file, which appears to be a temporary local copy
# of a remote file. Treating the file as a source file will
# be misleading, since it will normally have been deleted by
@@ -4963,33 +5182,32 @@
# copy of a remote file).
# So I have included a condition above that the file must
# exist to be included in the source-file list.
- push @$Pbiber_datasource, $file;
+ push @$PAdatasource, $file;
}
}
+ elsif ( /> WARN - I didn't find a database entry for '([^']+)'/ ) {
+ push @missing_citations, $1;
+ }
elsif ( /> INFO - WARNINGS: ([\d]+)\s*$/ ) {
- $bibers_warning_count = $1;
+ $biber_warning_count = $1;
}
elsif ( /> INFO - ERRORS: ([\d]+)\s*$/ ) {
- $bibers_error_count = $1;
+ $biber_error_count = $1;
}
}
close $blg_file;
- @$Pbiber_datasource = uniqs( @$Pbiber_datasource );
+ @$PAdatasource = uniqs( @$PAdatasource );
+ @$PAremote = uniqs( @$PAremote );
@not_found = uniqs( @not_found );
- push @$Pbiber_datasource, @not_found;
+ push @$PAdatasource, @not_found;
if ($control_file_malformed){return 11;}
- if ( ($#not_found < 0) && ($#$Pbiber_datasource >= 0) ) {
- print "$My_name: Found biber source file(s) [@$Pbiber_datasource]\n"
+ if ( ($#not_found < 0) && ($#$PAdatasource >= 0) ) {
+ print "$My_name: Found biber source file(s) [",
+ join( ', ', @$PAdatasource), "]\n"
unless $silent;
}
- elsif ( ($#not_found == 0) && ($not_found[0] =~ /\.bib$/) ) {
- # Special treatment if sole missing file is bib file
- # I don't want to treat that as an error
- print "$My_name: Biber did't find bib file [$not_found[0]]\n";
- return 5;
- }
else {
warn "$My_name: Failed to find one or more biber source files:\n";
foreach (@not_found) { warn " '$_'\n"; }
@@ -5002,13 +5220,9 @@
}
return 4;
}
-# print "$My_name: #Biber errors = $error_count, warning messages = $warning_count,\n ",
-# "missing citation messages = $missing_citations, no_citations = $no_citations\n";
- if ( ! $have_error && $no_citations ) {
- # If the only errors are missing citations, or lack of citations, that should
- # count as a warning.
- # HOWEVER: biber doesn't generate a new bbl. So it is an error condition.
- return 10;
+ if ( @missing_citations ) {
+ @missing_citations = uniqs( @missing_citations );
+ show_array( "$My_name: Biber reported missing citations", @missing_citations );
}
if ($have_error) {return 2;}
if ($have_warning) {return 1;}
@@ -5018,6 +5232,12 @@
#**************************************************
sub run_bibtex {
+ use strict;
+ # Rule variables used
+ our ( $rule, $Pdest, $Psource );
+ # Global variables used
+ our ( $bibtex_fudge, $My_name, $silent );
+
my $return = 999;
# Prevent changes we make to environment becoming global:
local %ENV = %ENV;
@@ -5067,44 +5287,77 @@
#**************************************************
-sub run_makeindex {
- my $return = 999;
- my ( $base, $path, $ext ) = fileparseA( $$Psource );
+sub after_bibtex {
+ # Analyze results of bibtex run, take appropriate actions on dependencies.
+ # Assumes rule context for bibtex
+ # Call
+ # after_bibtex( \$return ),
+ # where $return is code returned by running of bibtex (maybe modified by
+ # caller, which is normally rdb_run1). Can adjust its value to provoke
+ # better diagnosis of results of run to caller.
- # Define source and dest base to include extension, no path.
- my $source_base = $base.$ext;
- my $dest_base = basename( $$Pdest );
- if ( $path && $makeindex_fudge ) {
- my $cwd = good_cwd();
- pushd( $path );
+ use strict;
+ # Rule variables used
+ our ( $rule, $Pbase, $Pdest, $Plast_message, $Plast_result,
+ $Pout_of_date, $Psource );
+ # Global variables used
+ our ( %current_primaries, $diagnostics, $failure, $My_name, $silent );
+
+ my $Preturn = $_[0];
+ my $retcode = check_bibtex_log($$Pbase);
+ my @warnings = ();
+
+ if ( ! -e $$Psource ) {
+ $retcode = 10;
if (!$silent) {
- print "$My_name: Change directory to '$path'.\n";
+ print "Source '$$Psource' for '$rule' doesn't exist,\n",
+ "so I'll force *latex to run to try and make it.\n";
}
- # Override standard substitutions for source, dest, and base names in
- # default external command:
- $return = &Run_subst( undef, undef, '', $source_base, $dest_base, $base );
- popd();
- if (!$silent) {
- print "$My_name: Change directory back to '$cwd'\n";
+ rdb_for_some( [keys %current_primaries], sub{ $$Pout_of_date = 1; } );
+ }
+ if ($retcode == 3) {
+ $$Plast_result = 2;
+ $$Plast_message = "Could not open bibtex log file for '$$Pbase'";
+ push @warnings, $$Plast_message;
+ }
+ elsif ($retcode == 2) {
+ $$Plast_message = "Bibtex errors: See file '$$Pbase.blg'";
+ $failure = 1;
+ push @warnings, $$Plast_message;
+ }
+ elsif ($retcode == 1) {
+ push @warnings, "Bibtex warnings for '$$Pbase'";
+ }
+ elsif ($retcode == 10) {
+ push @warnings, "Bibtex found no citations for '$$Pbase',\n",
+ " or had missing aux or bib file(s)\n";
+ if (! -e $$Pdest ) {
+ print "$My_name: Bibtex did not produce '$$Pdest'. But that\n",
+ " was because of missing files, so I will continue.\n";
+ $$Preturn = -2;
}
+ else {
+ $$Preturn = 0;
+ }
}
- else {
- # Use default substitutions etc for rule:
- $return = Run_subst();
- }
- return $return;
-} #END run_makeindex
-
+} #END after_bibtex
+
#**************************************************
sub check_bibtex_log {
- # Check for bibtex warnings:
+ # Check for bibtex warnings and errors:
# Usage: check_bibtex_log( base_of_bibtex_run )
+ # (Return codes compatible with check_biber_log, but only used when applicable.)
# return 0: OK, 1: bibtex warnings, 2: bibtex errors,
# 3: could not open .blg file.
# 10: only error is missing \citation commands or a missing aux file
# (which would normally be corrected after a later run of
# *latex).
+ use strict;
+ # Variable used in context of a rule action
+ our ( $Pout_of_date );
+ # Global variables used
+ our ( %current_primaries, $My_name );
my $base = $_[0];
my $blg_name = "$base.blg";
@@ -5112,8 +5365,9 @@
or return 3;
my $have_warning = 0;
my $have_error = 0;
- my $missing_citations = 0;
+ my $no_citations = 0;
my @missing_aux = ();
+ my @missing_bib = ();
my $error_count = 0;
while (<$blg_file>) {
$_ = utf8_to_mine($_);
@@ -5125,8 +5379,11 @@
push @missing_aux, $1;
}
elsif ( /^I found no \\citation commands---while reading file/ ) {
- $missing_citations++;
+ $no_citations++;
}
+ elsif ( /^I couldn't open database file (.*\.bib)/ ) {
+ push @missing_bib, $1;
+ }
elsif (/There (were|was) (\d+) error message/) {
$error_count = $2;
#print "Bibtex error: count=$error_count $_";
@@ -5134,7 +5391,7 @@
}
}
close $blg_file;
- my $missing = $missing_citations + $#missing_aux + 1;
+ my $weak_errors = $no_citations + $#missing_aux + 1 + $#missing_bib + 1;
if ( $#missing_aux > -1 ) {
# Need to make the missing files.
print "$My_name: One or more aux files is missing for bibtex. I'll try\n",
@@ -5142,17 +5399,21 @@
rdb_for_some( [keys %current_primaries], sub{ $$Pout_of_date = 1; } );
}
#print "Bibtex errors = $error_count, missing aux files and citations = $missing\n";
- if ($have_error && ($error_count <= $missing )
- && ($missing > 0) ) {
- # If the only error is a missing citation line, that should only
- # count as a warning.
- # Also a missing aux file should be innocuous; it will be created on
- # next run of *latex. ?? HAVE I HANDLED THAT CORRECTLY?
+ if ($have_error && ($error_count <= $weak_errors )
+ && ($weak_errors > 0) ) {
+ # If the only error(s), are:
+ # lack of any \citation commands in aux file
+ # missing aux file(s)
+ # missing bib file(s)
+ # that should count as a warning.
+ # Note that a missing aux file is generally innocuous, that's
+ # commonly because the document has an include of a file in a
+ # subdirectory, an aux dir is in use, and the sub directory hasn't
+ # yet been made in the aux dir. That situation should be handled
+ # by latexmk by creating the directory and rerunning *latex.
# But have to deal with the problem that bibtex gives a non-zero
- # exit code. So leave things as they are so that the user gets
- # a better diagnostic ??????????????????????????
-# $have_error = 0;
-# $have_warning = 1;
+ # exit code.
+ # Let caller know:
return 10;
}
if ($have_error) {return 2;}
@@ -5162,6 +5423,36 @@
#**************************************************
+sub run_makeindex {
+ my $return = 999;
+ my ( $base, $path, $ext ) = fileparseA( $$Psource );
+
+ # Define source and dest base to include extension, no path.
+ my $source_base = $base.$ext;
+ my $dest_base = basename( $$Pdest );
+ if ( $path && $makeindex_fudge ) {
+ my $cwd = good_cwd();
+ pushd( $path );
+ if (!$silent) {
+ print "$My_name: Change directory to '$path'.\n";
+ }
+ # Override standard substitutions for source, dest, and base names in
+ # default external command:
+ $return = &Run_subst( undef, undef, '', $source_base, $dest_base, $base );
+ popd();
+ if (!$silent) {
+ print "$My_name: Change directory back to '$cwd'\n";
+ }
+ }
+ else {
+ # Use default substitutions etc for rule:
+ $return = Run_subst();
+ }
+ return $return;
+} #END run_makeindex
+
+#**************************************************
+
sub normalize_force_directory {
# Usage, normalize_force_directory( dir, filename )
# Filename is assumed to be relative to dir (terminated with directory separator).
@@ -5214,6 +5505,7 @@
}
$dvi_name = "%Z%R.dvi";
$dviF_name = "%Z%R.dviF";
+ $hnt_name = "%Z%R.hnt";
$ps_name = "%Z%R.ps";
$psF_name = "%Z%R.psF";
$pdf_name = "%Z%R.pdf";
@@ -5224,7 +5516,7 @@
$xdv_name = "%Y%R.xdv";
foreach ( $aux_main, $log_name, $fdb_name, $fls_name, $fls_name_alt,
- $dvi_name, $ps_name, $pdf_name, $xdv_name, $dviF_name, $psF_name ) {
+ $dvi_name, $hnt_name, $ps_name, $pdf_name, $xdv_name, $dviF_name, $psF_name ) {
s/%R/$root_filename/g;
s/%Y/$aux_dir1/;
s/%Z/$out_dir1/;
@@ -5231,6 +5523,7 @@
}
$dvi_final = $dvi_name;
+ $hnt_final = $hnt_name;
$ps_final = $ps_name;
$pdf_final = $pdf_name;
$xdv_final = $xdv_name;
@@ -5257,12 +5550,11 @@
# *latex always produces a log file unless there is a bad error, so
# this gives the best chance of diagnosing errors.
my $where_log = &find_set_log;
-
if ( $emulate_aux && ($aux_dir ne $out_dir) ) {
# Move output files from aux_dir to out_dir
# Move fls file also, if the configuration is for fls in out_dir.
# Omit 'xdv', that goes to aux_dir (as with MiKTeX). It's not final output.
- foreach my $ext ( 'fls', 'dvi', 'pdf', 'ps', 'synctex', 'synctex.gz' ) {
+ foreach my $ext ( 'fls', 'dvi', 'hnt', 'pdf', 'ps', 'synctex', 'synctex.gz' ) {
if ( ($ext eq 'fls') && ! $fls_uses_out_dir ) {next;}
my $from = "$aux_dir1$root_filename.$ext";
my $to = "$out_dir1$root_filename.$ext" ;
@@ -5621,7 +5913,7 @@
# data structure until block is ended.)
my %new_conversions = ();
my $log_silent = ($silent || $silence_logfile_warnings);
- @warning_list = ();
+ @warning_list = (); # Warnings about undefined citations and the like
LINE:
for (@$PAlines) {
@@ -5712,7 +6004,7 @@
push @multiply_defined_references, $2;
$mult_defined++;
}
- elsif (/^LaTeX Warning: (Citation `([^']+)' on page .* undefined on input line .*)\./) {
+ elsif (/^LaTeX Warning: (Citation [`|']([^']+)' on page .* undefined on input line .*)\./) {
push @warning_list, $1;
push @undefined_citations, $2;
$bad_citation++;
@@ -6062,22 +6354,40 @@
# Quote inside filename. Probably misparse.
next INCLUDE_NAME;
}
+ # Most (but not all) implementations of TeX, put a non-empty path
+ # in name of file read in .log file. Flag the situation of no path
+ # separator in the file name: There's a high potential for misparse.
+ # Do this before normalizing filename, and analyzing its components.
+ my $no_path = ( $include_name !~ m'[/|\\]' );
$include_name = normalize_filename( $include_name, @pwd_log );
if ( ! defined $include_name ) { next INCLUDE_NAME; }
+ if ( ! -e $include_name ) { next INCLUDE_NAME; }
my ($base, $path, $ext) = fileparseB( $include_name );
if ( ($path eq './') || ($path eq '.\\') ) {
$include_name = $base.$ext;
}
- if ( $include_name !~ m'[/|\\]' ) {
- # Filename does not include a path character
- # High potential for misparsed line
+ if ( $no_path ) {
$dependents{$include_name} = 2;
} else {
$dependents{$include_name} = 3;
}
if ( $ext eq '.bbl' ) {
- print "$My_name: Found input bbl file '$include_name'\n"
- unless $silent;
+ if ( -e $include_name ) {
+ print "$My_name: Found input bbl file '$include_name'\n"
+ unless $silent;
+ }
+ else {
+ warn "$My_name: Bbl file '$include_name' is listed in .log file\n",
+ " as having been read, but it doesn't exist\n";
+ if ( ($path eq '') && ($aux_dir ne '' ) && ( -e "%aux_dir1$include_name" ) ) {
+ warn " But it's in '$aux_dir'\n",
+ " There's probably a bug in .log file writing\n";
+ $include_name = "%aux_dir1$include_name";
+ }
+ else {
+ next;
+ }
+ }
push @bbl_files, $include_name;
}
} # INCLUDE_NAME
@@ -6154,9 +6464,6 @@
# exists, then the missing file does not correspond
# to the missing file, unless the .tex file was
# created during the run.
- # OLD $dependents{"$path$base.tex"} = 4;
- # OLD delete $dependents{$candidate};
- # NEW:
$dependents{"$path$base.tex"} = 4;
}
push @missing, $candidate;
@@ -6279,6 +6586,11 @@
my ($file, $PAlines, $PHinfo) = @_;
# Where lines are wrapped at. We'll sometimes override.
+ # Note that TeXLive's hilatex, at least in TL 2023, with HINT 2.0,
+ # doesn't obey max_print_line environment or the corresponding
+ # -cnf-line option. They work for pdflatex.
+ # Similarly for MiKTeX 23.10.12's hilatex, which reports the same version of
+ # HINT.
local $log_wrap = $log_wrap;
# Lines held for wrapping:
@@ -6315,6 +6627,8 @@
# luatex: UTF-8 but with wrapping at APPROXIMATELY
# $log_wrap bytes. Rest as pdftex
# xetex: UTF-8 with wrapping at $log_wrap codepoints.
+ # hilatex: (TL 2023, HINT 2.0) Pure 7-bit ASCII with ^^
+ # encoding of non-ASCII. Wrapping at 79 bytes.
# So we read file as bytes. Then
# first line gives which program was used and hence whether to wrap
# according to byte or codepoint count.
@@ -6341,7 +6655,9 @@
}
$lua_mode = ( $engine =~ /lua.*tex/i );
# TeXLive's *tex take log wrap value from environment variable max_print_line, if it exists:
- if ( ($tex_distribution =~ /TeX\s*Live/) && $ENV{max_print_line} ) {
+ if ( ($tex_distribution =~ /TeX\s*Live/) &&
+ $ENV{max_print_line} ) {
+ # See comment earlier about hilatex.
$log_wrap = $ENV{max_print_line};
print "$My_name: changed column for log file wrapping from standard to $log_wrap\n".
" from env. var. max_print_line, which is obeyed by your TeXLive programs\n"
@@ -6401,7 +6717,10 @@
&$Pwrap_sub();
}
close($fh);
- foreach (@$PAlines) { $_ = utf8_to_mine($_); }
+ foreach (@$PAlines) {
+ hathat_to_binary( $_ ) if ( $conv_hathat && /\^\^/ );
+ $_ = utf8_to_mine($_);
+ }
push @$PAlines, ""; # Blank line to terminate. So multiline blocks
# are always terminated by non-block line, rather than eof.
$$PHinfo{max_len} = $max_len;
@@ -6586,6 +6905,28 @@
#************************************************************
+sub hathat_to_binary {
+ # Convert ^^ notation to bytes (log files from non-8bit configured latex).
+ # In-line conversion.
+ # Usage, e.g., hathat_to_binary( $line ) or hathat_to_binary( @array ).
+ #
+ foreach (@_){
+ next unless /\^\^/;
+ while ( /(\^\^([[:xdigit:]]{2}))/g ) {
+ my $match = $1;
+ my $hex = $2;
+ my $pos = pos($_); # Regex analyzer positioned after match
+ my $before = $pos - length($match);
+ pos($_) = $before;
+ my $subst = chr hex $hex;
+ s/\G\Q$match/$subst/;
+ pos($_) = $before + length($subst);
+ }
+ }
+}
+
+#==============================================
+
sub dirname_no_tail {
my $dirname = $_[0];
foreach ($dirname) {
@@ -6818,6 +7159,12 @@
push @$Paux_files, $aux_file;
AUX_LINE:
while (<$aux_fh>) {
+ if ( /\^\^/ ) {
+ warn "$My_name: Line in '$aux_file' uses ^^ notation, which may\n".
+ " cause trouble to bibtex:\n $_";
+ # At least I need to be able to handle the line:
+ hathat_to_binary( $_ ) if $conv_hathat;
+ }
$_ = utf8_to_mine($_);
s/\s$//;
if ( /^\\bibdata\{(.*)\}/ ) {
@@ -6863,69 +7210,145 @@
#************************************************************
sub parse_bcf {
- # Parse bcf file for bib and other source files.
- # Usage: parse_bcf( $bcf_file, \@new_bib_files )
+ # Parse bcf file for bib and other source files, and
+ # do an elementary test for completeness.
+ # Usage: parse_bcf( $bcf_file, \$status, \%bib_files, \@found,
+ # \@not_found, \@remote )
# If can't open bcf file, then
- # Return 0 and leave @new_bib_files empty
- # Else set @new_bib_files from information in the
- # bcf files
- # And:
- # Return 1 if no problems
- # Return 2 with @new_bib_files empty if there are no relevant source
- # file lines.
- # Return 3 if I couldn't locate all the bib_files
+ # Return with $status = 0 and the hash and arrays empy.
+ #
+ # Else set the hash and the arrays from information in the bcf_file,
+ # set $status to
+ # 1 if no problems
+ # 2 if there were no relevant datasource lines
+ # Note this is not an error! *latex & biber will not report an
+ # error, and will simply result in an empty b
+ # 3 if I couldn't locate all the bib_files
+ # 100 plus one of the codes 1..3 if the bcf file appears
+ # incomplete.
+ #
# A full parse of .bcf file as XML would need an XML parsing module, which
# is not in a default installation of Perl, notably in TeXLive's perl for
# Win32 platform. To avoid requiring the installation, just search the
# .bcf file for the relevant lines.
+ #
+ # !!!!!!!!!!!!!!!!!??????????? Allow for remote bib files.
- my $bcf_file = $_[0];
- my $Pbib_files = $_[1];
- # Default return value
- @$Pbib_files = ();
- # Map file specs (from datasource lines) to actual filenames:
- local %bib_files = ();
- my @not_found_bib = ();
+ use strict;
+ # Global variables used
+ our ( $My_name, $silent );
+
+ my ($bcf_file, $Pstatus, $PHbib_files, $PAfound, $PAnot_found, $PAremote ) = @_;
+ $$Pstatus = 0;
+ my %glob_names = ();
+ my @found = ();
+ my @not_found = ();
+ my %remote = ();
+
+ my $incomplete = 0; # Values 0 or 1
+
open(my $bcf_fh, $bcf_file)
|| do {
- warn "$My_name: Couldn't find bcf file '$bcf_file'\n";
- return 0;
+ warn "$My_name: Couldn't find bcf file '$bcf_file'\n";
};
+ $$Pstatus = 1;
while ( <$bcf_fh> ) {
$_ = utf8_to_mine($_);
- if ( /^\s*<bcf:datasource type=\"file\"\s+datatype=\"bibtex\"\s+glob=\"false\">(.+)<\/bcf:datasource>/ ) {
- $bib_files{$1} = '';
+ if (eof($bcf_fh)) {
+ if ( ! /^\s*<\/bcf:controlfile>/ ) {
+ warn "$My_name: Incomplete (and hence corrupt) bcf file '$bcf_file'\n";
+ $incomplete = 1;
+ }
}
+ if ( /^\s*<bcf:datasource type=\"file\"\s+datatype=\"bibtex\"\s*(.*)>(.+)<\/bcf:datasource>/ ) {
+ my $tail = $1; # Can contain a glob item, which will affect meaning of filename.
+ my $file = $2;
+ if ($file =~ /^http:|^https:|^ftp:|^ftps:/ ) { $remote{$file} = ''; }
+ elsif ($tail =~ /glob=\"true\"/ ) { $glob_names{$file} = ''; }
+ else { $$PHbib_files{$file} = ''; }
+ }
}
close $bcf_fh;
- find_files( \%bib_files, 'bib', 'bib', $Pbib_files, \@not_found_bib );
- if ( $#{$Pbib_files} == -1 ) {
- #
- print "$My_name: No .bib files listed in .bcf file '$bcf_file'\n";
- return 2;
+ foreach my $spec ( keys %glob_names ) {
+ my @result = glob $spec;
+ if ( ($#result == 0) && ($spec eq $result[0]) ) {
+ # There was no wild card, and glob just returned the given
+ # name, which applies whether or not the file exists.
+ # We'll treat is the same as a non-globbed name.
+ $$PHbib_files{$spec} = '';
+ delete $glob_names{$spec};
+ }
+ else {
+ foreach (@result) { $$PHbib_files{$_} = $_; }
+ }
}
+ foreach (keys %$PHbib_files) { if (-e) { $$PHbib_files{$_} = $_; } }
+ foreach my $spec (keys %$PHbib_files ) {
+ next if $$PHbib_files{$spec};
+ my @lines = kpsewhich( $spec );
+ if (@lines) { $$PHbib_files{$spec} = $lines[0]; }
+ }
+ while (my ($spec, $file) = each %$PHbib_files ) {
+ if ($file) { push @found, $file; }
+ else { push @not_found, $spec; }
+ }
- show_array( "$My_name: Bibliography file(s) from .bcf file:", @$Pbib_files )
+ @found = uniqs(@found);
+ @not_found = uniqs(@not_found);
+ push @$PAfound, @found;
+ push @$PAnot_found, @not_found;
+ push @$PAremote, sort keys %remote;
+
+ show_array( "$My_name: Bibliography file(s) from .bcf file:", sort( @found, @not_found ) )
unless $silent;
- if (@not_found_bib) {
- show_array(
- "Bib file(s) not found in search path:",
- @not_found_bib );
- }
- if (@not_found_bib) {
- if ($force_mode) {
+ if (@not_found) {
+ show_array( "Bib file(s) not found in search path:", @not_found );
+ if ($force_mode && ! $incomplete) {
warn "$My_name: Failed to find one or more bibliography files in search path.\n";
warn "====BUT force_mode is on, so I will continue. There may be problems ===\n";
}
- return 3;
+ $$Pstatus = 3;
}
- return 1;
+ $$Pstatus += 100 * $incomplete;
} #END parse_bcf
+#************************************************************
+sub incomplete_bcf {
+ # Do simple check of bcf file for completeness.
+ # Usage: incomplete_bcf( $bcf_file )
+ # Reason for this subroutine: If a run of *latex exits prematurely
+ # because of an error, any bcf file generated would normally be
+ # incomplete. It is useful to test for this before running biber,
+ # especially as part of the end-of-run analysis for *latex, to do
+ # appropriate clean up in an error situation.
+ # Perhaps it would be ideal to check for other kinds of malformed bcf
+ # file, but the incomplete run from error termination of *latex is
+ # likely to be the most common case.
+ # Return 1 if bcf file exists but does NOT have the expected final line.
+ # Otherwise return 0.
+
+ my $bcf_file = $_[0];
+ my $last_line = '';
+
+ open(my $bcf_fh, $bcf_file)
+ || do {
+ warn "$My_name: Couldn't find bcf file '$bcf_file'\n";
+ return 0;
+ };
+ while ( <$bcf_fh> ) {
+ if (eof($bcf_fh)) { $last_line = $_; }
+ }
+ close $bcf_fh;
+ if ( $last_line =~ /^\s*<\/bcf:controlfile>/ ) { return 0; }
+ warn "$My_name: Incomplete (and hence corrupt) bcf file '$bcf_file'\n";
+ return 1;
+} #END incomplete_bcf
+
+
#************************************************************
#************************************************************
#************************************************************
@@ -7416,7 +7839,11 @@
# Set its dependents etc, using information from log, aux, and fls files.
# Use fls file only if $recorder is set, and the fls file was generated
# on this run.
- # Return:
+ # Return: An array: ( Whether there are missing directories,
+ # reference to array of missing directories,
+ # whether there are bad warnings
+ # )
+ # (Missing directories are those for aux files in aux_dir.)
# N.B. A complication which we try and handle in determining
# dependent files is that there may be aliasing of file names,
@@ -7756,7 +8183,7 @@
$failure = 0;
}
$created_rules{$ind_file} = $from_rule;
- }
+ } # end IDX_FILE
local %processed_aux_files = ();
BBL_FILE:
@@ -7763,9 +8190,6 @@
foreach my $bbl_file ( uniqs( @bbl_files ) ) {
my ($bbl_base, $bbl_path, $bbl_ext) = fileparseA( $bbl_file );
$bbl_base = $bbl_path.$bbl_base;
- my @new_bib_files = ();
- my @new_aux_files = ();
- my @new_bst_files = ();
my $bcf_file = "$bbl_base.bcf";
my $bib_program = 'bibtex';
if ( test_gen_file( $bcf_file ) ) {
@@ -7772,66 +8196,104 @@
$bib_program = 'biber';
}
my $from_rule = "$bib_program $bbl_base";
- print "======= Dealing with '$from_rule'\n" if ($diagnostics);
+ $created_rules{$bbl_file} = $from_rule;
+ print " ===Source file '$bbl_file' for '$rule'\n"
+ if ($diagnostics);
+ rdb_ensure_file( $rule, $bbl_file, $from_rule );
+ if ( ! -e $bbl_file ) {
+ # Failure was non-existence of makable file
+ # Leave failure issue to other rules.
+ $failure = 0;
+ }
+
# Don't change to use activation and deactivation here, rather than
# creation and removal of rules. This is because rules are to be
# created on the fly here with details corresponding to current state
# of .tex source file(s). So activating a previously inactive rule,
- # which is out-of-date, may cause trouble.
+ # which is out-of-date, may cause trouble. ????????????? I just use previous rule, if it exists???
if ($bib_program eq 'biber') {
# Remove OPPOSITE kind of bbl generation:
rdb_remove_rule( "bibtex $bbl_base" );
-
- parse_bcf( $bcf_file, \@new_bib_files );
- }
+ # Get information from .bcf file:
+ my $bcf_status = 0;
+ my %bib_files = ();
+ my @found = ();
+ my @not_found = ();
+ my @remote = ();
+ parse_bcf( $bcf_file, \$bcf_status, \%bib_files,
+ \@found, \@not_found, \@remote );
+ my @new_sources = (@found, @not_found);
+ push @new_sources, $bcf_file;
+ if ( ! rdb_rule_exists( $from_rule ) ){
+ print " ===Creating rule '$from_rule'\n" if ($diagnostics);
+ rdb_create_rule( $from_rule, 'external', $biber, '', 1,
+ $bcf_file, $bbl_file, $bbl_base,
+ 1, 0, 0, 1, [ "$bbl_base.blg" ] );
+ # Since the rule is new, populate it with the best information
+ # that we have;
+ rdb_ensure_file_multi( $from_rule, @new_sources );
+ }
+ # Cache the information about source files from .bcf file, for use
+ # when biber terminates earlier:
+ rdb_set_extra( $from_rule, 'bcf_datasources', [@new_sources] );
+ if ($bcf_status >= 100 ) {
+ my $save_bcf = "$bcf_file$save_error_suffix";
+ my $save_bbl = "$bbl_file$save_error_suffix";
+ warn "$My_name: ========== Incomplete bcf_file '$bcf_file'.\n",
+ " I'll rename the file to '$save_bcf'.\n";
+ rename $bcf_file, $save_bcf;
+ if ($bibtex_use) {
+ warn " I'll rename the bbl file to '$save_bbl',\n",
+ " in case the incomplete bcf file was a result of error in\n",
+ " '$rule' caused by an error in the bbl file.\n";
+ rename $bbl_file, $save_bbl;
+ }
+ }
+ if ( ($bibtex_use == 1) || ($bibtex_use == 1.5) ) {
+ # Conditional use of biber => we'll make decisions on
+ # whether to run biber according to whether all bib files
+ # exist. That's on the basis of the source list of the
+ # biber rule. So if the latest information from .bcf file
+ # is that a previously listed but non-existent bib file is
+ # not in the list from the .bcf file, then we remove it
+ # from the source list of biber.
+ # AND I must add any files listed in .bcf that are
+ # non-existent.
+ my @bib_to_remove = ();
+ foreach (rdb_get_source( $from_rule ) ) {
+ if ( ( /\.bib$/ ) && ( ! -e $_ ) && ( ! exists $bib_files{$_} ) ) {
+ push @bib_to_remove, $_;
+ }
+ }
+ show_array( "Bib files to remove from source list of '$from_rule'",
+ @bib_to_remove
+ ) if $diagnostics;
+ rdb_remove_files( $from_rule, @bib_to_remove );
+ show_array( "Bib files to add to source list of '$from_rule'",
+ @not_found
+ ) if $diagnostics;
+ rdb_ensure_file_multi( $from_rule, @not_found );
+ }
+ } # end biber setup
else {
+ # Using bibtex
# Remove OPPOSITE kind of bbl generation:
rdb_remove_rule( "biber $bbl_base" );
-
- parse_aux( "$bbl_base.aux", \@new_bib_files, \@new_aux_files, \@new_bst_files );
- }
- if ( ! rdb_rule_exists( $from_rule ) ){
- print " ===Creating rule '$from_rule'\n" if ($diagnostics);
- if ( $bib_program eq 'biber' ) {
- rdb_create_rule( $from_rule, 'external', $biber, '', 1,
- $bcf_file, $bbl_file, $bbl_base, 1, 0, 0, 1, [ "$bbl_base.blg" ] );
- }
- else {
+ if ( ! rdb_rule_exists( $from_rule ) ){
rdb_create_rule( $from_rule, 'external', $bibtex, 'run_bibtex', 1,
- "$bbl_base.aux", $bbl_file, $bbl_base, 1, 0, 0, 1, [ "$bbl_base.blg" ] );
+ "$bbl_base.aux", $bbl_file, $bbl_base,
+ 1, 0, 0, 1, [ "$bbl_base.blg" ] );
}
- }
- $created_rules{$bbl_file} = $from_rule;
- local %old_sources = ();
- rdb_one_rule( $from_rule, sub { %old_sources = %$PHsource; } );
- my @new_sources = ( @new_bib_files, @new_aux_files, @new_bst_files );
- if ( $bib_program eq 'biber' ) {
- push @new_sources, $bcf_file;
- }
- foreach my $source ( @new_sources ) {
- print " ===Source file '$source' for '$from_rule'\n"
- if ($diagnostics);
- rdb_ensure_file( $from_rule, $source );
- delete $old_sources{$source};
- }
- foreach my $source ( @new_aux_files ) {
- $processed_aux_files{$source} = 1;
- }
- if ($diagnostics) {
- foreach ( keys %old_sources ) {
- print "Removing no-longer-needed dependent '$_' from rule '$from_rule'\n";
- }
- }
- rdb_remove_files( $from_rule, keys %old_sources );
- print " ===Source file '$bbl_file' for '$rule'\n"
- if ($diagnostics);
- rdb_ensure_file( $rule, $bbl_file, $from_rule );
- if ( ! -e $bbl_file ) {
- # Failure was non-existence of makable file
- # Leave failure issue to other rules.
- $failure = 0;
- }
- }
+ my @new_bib_files = ();
+ my @new_aux_files = ();
+ my @new_bst_files = ();
+ parse_aux( "$bbl_base.aux",
+ \@new_bib_files, \@new_aux_files, \@new_bst_files );
+ foreach ( @new_aux_files ) { $processed_aux_files{$_} = 1; }
+ rdb_set_source( $from_rule,
+ @new_bib_files, @new_aux_files, @new_bst_files );
+ } # end bibtex set upt
+ } # end BBL_FILE
if ( ($#aux_hooks > -1) && ! exists $processed_aux_files{$aux_main} ) {
my @new_bib_files = ();
@@ -7951,7 +8413,8 @@
rdb_remove_files( $rule, @files_not_needed );
return ($missing_dirs, [@missing_subdirs],
- ( $log_info{bad_warning} ? 1 : 0 ) );
+ ( $log_info{bad_warning} ? 1 : 0 ),
+ );
} # END rdb_set_latex_deps
@@ -8372,6 +8835,7 @@
my @dest_exts = ();
if ($pdf_mode) {push @dest_exts, '.pdf';}
if ($dvi_mode) {push @dest_exts, '.dvi';}
+ if ($hnt_mode) {push @dest_exts, '.hnt';}
if ($postscript_mode) {push @dest_exts, '.ps';}
my $deps_space = ' ';
@@ -8760,6 +9224,7 @@
print "=========SWITCH OF OUTPUT WAS DONE.\n";
next PASS;
}
+
if ( ($runs > 0) && ! $too_many_passes ) {
$retry_msg = 0;
if ( $force_mode || (! $failure) ) {
@@ -8894,6 +9359,33 @@
else { print "$My_name: Nothing to do for '$texfile_name'.\n"; }
# Diagnostics
+ my @missing_bib = ();
+ my @bibx_vetoed = ();
+ rdb_for_some( [rdb_accessible()],
+ sub{ if ( $rule =~ /^(biber|bibtex)/ ) {
+ my $veto = $$PHextra{bibx_vetoed};
+ if ( $veto ) {
+ push @bibx_vetoed, $rule;
+ if ( (ref($veto) eq 'ARRAY') && (@$veto) ) { push @missing_bib, @$veto; }
+ }
+ }
+ }
+ );
+ if (@bibx_vetoed && ! $silent) {
+ show_array(
+ "\n$My_name: The following rules were vetoed from being run, because of the\n".
+ "setting for the non-use/condititional use of bibtex/biber:",
+ sort( @bibx_vetoed )
+ );
+ if ($bibtex_use == 0) { print "Reason: I am configured not to use bibtex/biber\n"; }
+ elsif (@missing_bib) {
+ show_array(
+ "Reason: I am configured only to use bibtex/biber if all .bib files exist,\n".
+ "but the following didn't:",
+ uniqs( @missing_bib )
+ );
+ }
+ }
if ($#primary_warning_summary > -1) {
# N.B. $mult_defined, $bad_reference, $bad_character, $bad_citation also available here.
show_array( "$My_name: Summary of warnings from last run of *latex:",
@@ -8900,10 +9392,10 @@
@primary_warning_summary );
}
if ( ($#warning_list >= 0) && !$silence_logfile_warnings ) {
- warn "$My_name: ====List of undefined refs and citations:\n";
+ warn "$My_name: ====Undefined refs and citations with line #s in .tex file:\n";
for (my $i = 0; $i <= $#warning_list; $i++) {
if ($i >= $max_logfile_warnings ) {
- warn " And ", $#warning_list + 1 - $i, " more --- see log file.\n";
+ warn " And ", $#warning_list + 1 - $i, " more --- see log file '$log_name'\n";
last;
}
warn " $warning_list[$i]\n";
@@ -9006,33 +9498,19 @@
# define $pass{$rule} elsewhere, do it here:
if ( ! defined $pass{$rule} ) {$pass{$rule} = 0; }
- # Special fix up for bibtex:
- my $bibtex_not_run = -1; # Flags status as to whether this is a
- # bibtex rule and if it is, whether out-of-date condition is to
- # be ignored.
- # -1 => not a bibtex rule
- # 0 => no special treatment
- # 1 => don't run bibtex because of non-existent bibfiles
- # (and setting to do this test)
- # 2 => don't run bibtex because of setting
- my @missing_bib_files = ();
- if ( $rule =~ /^(bibtex|biber)/ ) {
- $bibtex_not_run = 0;
- if ($bibtex_use == 0) {
- $bibtex_not_run = 2;
+ my %changes = ();
+ if ( ! rdb_rerun_needed(\%changes, 0) ) {
+ my $veto = $$PHextra{bibx_vetoed};
+ if ($veto && ! $silent ) {
+ warn "$My_name: Veto of running of '$rule' (\$bibtex_use=$bibtex_use)\n";
}
- elsif ( ($bibtex_use == 1) || ($bibtex_use == 1.5) ) {
- # Conditional run of bibtex (or biber) depending on existence of .bib file.
- foreach ( keys %$PHsource ) {
- if ( ( /\.bib$/ ) && (! -e $_) ) {
- push @missing_bib_files, $_;
- $bibtex_not_run = 1;
- }
- }
- }
+ return;
}
- if ( ! rdb_rerun_needed(\%changes, 0) ) { return; }
+ if (!$silent) {
+ print "$My_name: applying rule '$rule'...\n";
+ &rdb_diagnose_changes2( \%changes, "Rule '$rule': ", 0 );
+ }
# Set this in case of early exit:
# ???!!! Check I am setting $missing_dvi_pdf correctly.
@@ -9039,15 +9517,10 @@
if ( $$Pdest && (! -e $$Pdest) && ( $$Pcmd_type eq 'primary' ) ) {
$missing_dvi_pdf = $$Pdest;
}
-
- if (!$silent) {
- print "$My_name: applying rule '$rule'...\n";
- &rdb_diagnose_changes2( \%changes, "Rule '$rule': ", 0 );
- }
-
# We are applying the rule, so its source file state for when it was
- # last made is as of now. This is do in the subroutines that do the
- # actual run, to allow for possible calls to them from other places.
+ # last made should be as of now. This is done in the subroutines that
+ # do the actual run, to allow for possible calls to them from other
+ # places. (Actually only rdb_run1, now.)
# The actual run
my $return = 0; # Return code from called routine
@@ -9069,21 +9542,10 @@
$runs_total++;
$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:",
- @missing_bib_files);
- }
- elsif ($bibtex_not_run == 2 ) {
- warn "$My_name: I AM CONFIGURED/INVOKED NOT TO RUN '$rule'\n";
- }
- $return = &rdb_dummy_run0;
- }
- else {
- warn_running( "Run number $pass{$rule} of rule '$rule'" );
- $return = &rdb_run1;
- }
+ warn_running( "Run number $pass{$rule} of rule '$rule'" );
+ $return = &rdb_run1;
+
if ($$Pchanged) {
$newrule_nofile = 1;
$return = 0;
@@ -9090,10 +9552,10 @@
}
elsif ( $$Pdest && ( !-e $$Pdest ) && (! $failure) ){
# If there is a destination to make, but for some reason
- # it did not get made, and no other error was reported,
- # then a priori there appears to be an error condition:
- # the run failed. But there are some important cases in
- # which this is a wrong diagnosis.
+ # it did not get made, and an error condition wasn't set already
+ # in $failure, then a priori there appears to be an error
+ # condition, i.e., the run failed. But there are some important
+ # cases in which this is a wrong diagnosis.
if ( ( $$Pcmd_type eq 'cusdep') && $$Psource && (! -e $$Psource) ) {
# However, if the rule is a custom dependency, this is not by
# itself an error, if also the source file does not exist. In
@@ -9117,19 +9579,12 @@
# Missing output file was reported to be NOT an error
$$Pout_of_date = 0;
}
- elsif ( ($bibtex_use <= 1.5) && ($bibtex_not_run > 0) ) {
- # Lack of destination file is not to be treated as an error
- # for a bibtex rule when latexmk is configured not to treat
- # this as an error, and the lack of a destination file is the
- # only error.
- $$Pout_of_date = 0;
- }
else {
$failure = 1;
}
}
if ( ($return != 0) && ($return != -2) ) {
- $failure = 1;
+ $failure = 1;
$$Plast_result = 2;
if ( !$$Plast_message ) {
$$Plast_message = "Run of rule '$rule' gave a non-zero error code";
@@ -9149,6 +9604,11 @@
# Otherwise: 0 on other kind of success,
# -1 on error,
# -2 when missing dest_file is to be ignored
+ # -3 for situation like biber with malformed bcf file:
+ # missing dest_file that can't be made without
+ # change of source file
+ # error is to be reported
+ # corrupt source file has been deleted/renamed.
# Defaults for summary of results of run.
$$Prun_time = time();
@@ -9233,105 +9693,10 @@
run_hooks( 'after_xlatex_analysis' );
}
elsif ( $rule =~ /^biber/ ) {
- my @biber_datasource = ( );
- my $retcode = check_biber_log( $$Pbase, \@biber_datasource );
- foreach my $source ( @biber_datasource ) {
-# if ( $source =~ /\"/ ) {next; }
- print " ===Source file '$source' for '$rule'\n"
- if ($diagnostics);
- rdb_ensure_file( $rule, $source );
- }
- if ($retcode == 5) {
- # Special treatment if sole missing file is bib file
- # I don't want to treat that as an error
- $return = 0;
- $$Plast_result = 200;
- $$Plast_message = "Could not find bib file for '$$Pbase'";
- push @warnings, "Bib file not found for '$$Pbase'";
- }
- elsif ($retcode == 6) {
- # Missing control file. Need to remake it (if possible)
- # Don't treat missing bbl file as error.
- print "$My_name: bibtex control file missing. Since that can\n",
- " be recreated, I'll try to do so.\n";
- $return = -2;
- rdb_for_some( [keys %current_primaries], sub{ $$Pout_of_date = 1; } );
- }
- elsif ($retcode == 4) {
- $$Plast_result = 2;
- $$Plast_message = "Could not find all biber source files for '$$Pbase'";
- push @warnings, "Not all biber source files found for '$$Pbase'";
- }
- elsif ($retcode == 3) {
- $$Plast_result = 2;
- $$Plast_message = "Could not open biber log file for '$$Pbase'";
- push @warnings, $$Plast_message;
- }
- elsif ($retcode == 2) {
- $$Plast_message = "Biber errors: See file '$$Pbase.blg'";
- push @warnings, $$Plast_message;
- }
- elsif ($retcode == 1) {
- push @warnings, "Biber warnings for '$$Pbase'";
- }
- elsif ($retcode == 10) {
- push @warnings, "Biber found no citations for '$$Pbase'";
- # Biber doesn't generate a bbl file in this situation.
- $return = -2;
- }
- elsif ($retcode == 11) {
- push @warnings, "Biber: malformed bcf file for '$$Pbase'. IGNORE";
- if (!$silent) {
- print "$My_name: biber found malformed bcf file for '$$Pbase'.\n",
- " I'll ignore error, and delete any bbl file.\n";
- }
- # Malformed bcf file is a downstream consequence, normally,
- # of an error in *latex run. So this is not an error
- # condition in biber itself.
- # Current version of biber deletes bbl file.
- # Older versions (pre-2016) made an incorrect bbl file, which
- # tended to cause latex errors, and give a self-perpetuating error.
- # To be safe, ensure the bbl file doesn't exist.
- unlink $$Pdest;
- # The missing bbl file is now not an error:
- $return = -2;
- }
+ after_biber( \$return );
}
elsif ( $rule =~ /^bibtex/ ) {
- my $retcode = check_bibtex_log($$Pbase);
- if ( ! -e $$Psource ) {
- $retcode = 10;
- if (!$silent) {
- print "Source '$$Psource' for '$rule' doesn't exist,\n",
- "so I'll force *latex to run to try and make it.\n";
- }
- rdb_for_some( [keys %current_primaries], sub{ $$Pout_of_date = 1; } );
- }
- if ($retcode == 3) {
- $$Plast_result = 2;
- $$Plast_message = "Could not open bibtex log file for '$$Pbase'";
- push @warnings, $$Plast_message;
- }
- elsif ($retcode == 2) {
- $$Plast_message = "Bibtex errors: See file '$$Pbase.blg'";
- $failure = 1;
- push @warnings, $$Plast_message;
- }
- elsif ($retcode == 1) {
- push @warnings, "Bibtex warnings for '$$Pbase'";
- }
- elsif ($retcode == 10) {
- push @warnings, "Bibtex found no citations for '$$Pbase',\n",
- " or bibtex found a missing aux file\n";
- if (! -e $$Pdest ) {
- print "$My_name: Bibtex did not produce '$$Pdest'. But that\n",
- " was because of missing files, so I will continue.\n";
- $return = -2;
- }
- else {
- $return = 0;
- }
- }
+ after_bibtex( \$return );
}
else {
# No special analysis for other rules
@@ -9366,28 +9731,6 @@
#-----------------
-sub rdb_dummy_run0 {
- # Assumes contexts for: rule.
- # Update rule state as if the rule ran successfully,
- # but don't run the rule.
- # Returns 0 (success code)
-
- # Source file data, by definition, correspond to the file state just before
- # the latest run, and the run_time to the time just before the run:
- &rdb_update_files;
- $$Prun_time = time();
- $$Pchanged = 0; # No special changes in files
- $$Plast_result = 0;
- $$Plast_result_info = 'CURR';
- $$Plast_message = '';
-
- $$Pout_of_date = $$Pout_of_date_user = 0;
-
- return 0;
-} # END rdb_dummy_run0
-
-#-----------------
-
sub Run_subst {
# Call: Run_subst( cmd, msg, options, source, dest, base )
# Runs command with substitutions.
@@ -9465,6 +9808,9 @@
return $return;
} #END Run_subst
+
+#************************************************************
+
sub analyze_latex_run {
# Call: analyze_latex_run(old_ret_code)
# Analyze results of run of *latex (or whatever was run instead) from
@@ -9493,7 +9839,7 @@
my ($missing_dirs, $PA_missing_subdirs, $bad_warnings) = &rdb_set_latex_deps;
if ($bad_warning_is_error && $bad_warnings) {
warn "$My_name: Serious warnings in .log configured to be errors\n";
- $return ||= $bad_warnings;1
+ $return ||= $bad_warnings;
}
# For each file of the kind made by epstopdf.sty during a run,
@@ -9623,7 +9969,7 @@
);
return $user_changes;
-}
+} #END rdb_user_changes
#************************************************************
@@ -9648,6 +9994,9 @@
local our $PHchanges = shift;
local our $outside_make_loop = shift;
+ my $bibx_rule = ( $rule =~ /^(biber|bibtex)/ );
+
+
# File level routine reports its results in %$PHchanges: maps kind of
# change to ref to array of files with that kind of change.
%$PHchanges = ();
@@ -9766,6 +10115,11 @@
elsif ( $$Pcmd_type eq 'delegated' ) {
# Delegate to destination rule
}
+ elsif ( $$PHextra{bibx_vetoed} ) {
+ # Previous attempt at a run of biber/bibtex was vetoed
+ # So it's pointless to rerun it unless there was some
+ # other change, which will have been detected.
+ }
else {
$rerun_needed = 1;
push @{$$PHchanges{no_dest}}, $rule;
@@ -9779,6 +10133,43 @@
}
}
$$Pno_history = 0; # See comments in definition of %rule_db.
+ if ( $$Psource && (! -e $$Psource) ) {
+# print "================In '$rule', no source '$$Psource'\n";
+ }
+
+ if ( $bibx_rule ) {
+ # Check whether run of biber/bibtex rule is to be vetoed.
+ # Default to no veto:
+ $$PHextra{bibx_vetoed} = 0;
+ if ($rerun_needed) {
+ if ($bibtex_use == 0) {
+ # Do not use biber/bibtex at all
+ $rerun_needed = 0;
+ $$PHextra{bibx_vetoed} = 1;
+ }
+ elsif ($bibtex_use < 1.9) {
+ # Conditional bibtex/biber use, if all .bib files exist
+ my @missing_bib_files = ();
+ foreach ( keys %$PHsource ) {
+ if ( ( /\.bib$/ ) && (! -e $_) ) {
+ push @missing_bib_files, $_;
+ }
+ }
+ if ( @missing_bib_files ) {
+ $rerun_needed = 0;
+ $$PHextra{bibx_vetoed} = [ sort @missing_bib_files ];
+ }
+ }
+ if ($$PHextra{bibx_vetoed}) {
+ # Avoid propagating error state from previous invocations,
+ # since things might have changed if I did a run instead of
+ # vetoing it. A saved non-zero error state tends to stop
+ # certain things from being run.
+ $$Plast_result = 0;
+ }
+
+ }
+ }
if ($rerun_needed) {
push @{$$PHchanges{rules_to_apply}}, $rule;
}
@@ -10122,9 +10513,13 @@
#===== Accesses rule part of database structure =======
local ( $rule, $rule_act1, $file_act, $rule_act2 ) = @_;
- if ( (! $rule) || ! rdb_rule_exists($rule) ) { return; }
+ if ( (! $rule) || ! rdb_rule_exists($rule) ) {
+ die_trace( "$My_name: BUG in call to rdb_one_rule: non-existent rule '$rule'" );
+ }
- local ( $PArule_data, $PHsource, $PHdest, $PHrewritten_before_read, $PHsource_rules ) = @{$rule_db{$rule}};
+ local ( $PArule_data, $PHsource, $PHdest, $PHrewritten_before_read,
+ $PHsource_rules, $PHextra )
+ = @{$rule_db{$rule}};
local ($Pcmd_type, $Pext_cmd, $PAint_cmd, $Pno_history,
$Psource, $Pdest, $Pbase,
$Pout_of_date, $Pout_of_date_user, $Prun_time, $Pcheck_time,
@@ -10286,6 +10681,7 @@
{},
{},
{},
+ {},
{}
];
foreach my $file ($source, @$PAextra_source ) {
@@ -10368,36 +10764,80 @@
if ( ! defined $new_file ) {
die_trace( "$My_name: BUG in call to rdb_ensure_file: undefined file for '$rule'" );
}
- if ( $new_file =~ /\"/ ) {
- warn "$My_name: in rdb_ensure_file for rule '$rule', there is a double quote in\n",
- " the filename: '$new_file'.\n",
- " I cannot handle this, will ignore this file.\n";
- return;
- }
if ( ! defined $set_not_exists ) { $set_not_exists = 0; }
- rdb_one_rule( $rule,
- sub{
- if (! exists ${$PHsource}{$new_file} ) {
- if ( $set_not_exists ) {
- ${$PHsource}{$new_file} = [@nofile, '', 0];
- }
- else {
- ${$PHsource}{$new_file}
- = [fdb_get($new_file, $$Prun_time), '', 0];
- }
- }
+ rdb_one_rule(
+ $rule, sub{ if ($set_not_exists) { rdb_ensure_new_files_here($new_file); }
+ else { rdb_ensure_files_here($new_file); }
}
);
- if (defined $new_from_rule ) {
- $from_rules{$new_file} = $new_from_rule;
- }
+ if (defined $new_from_rule ) { $from_rules{$new_file} = $new_from_rule; }
} #END rdb_ensure_file
#************************************************************
+sub rdb_ensure_file_multi {
+ # rdb_ensure_file( rule, file ... )
+ # Ensures the source files exist in the given rule.
+ # Like rdb_ensure_file, but without the possible setting of a from rule
+ # or of the initialization to non-existent file
+ #============ NOTE: rule and file data set here ===============================
+ use strict;
+ my $rule = shift;
+ my @files = @_;
+ rdb_one_rule( $rule, sub { rdb_ensure_files_here( @files ); } );
+} #END rdb_ensure_file_multi
+
+#************************************************************
+
+sub rdb_ensure_files_here {
+ # rdb_ensure_files_here( file, ...)
+ # Assumes rule context
+ # Ensures the given files are in the source file list.
+ # For added files, initialize state to current of file,
+ # as is appropriate if the file was read in latest run of rule
+ use strict;
+ our ($rule, $My_name, $PHsource, $Prun_time);
+ foreach (@_) {
+ if ( /\"/ ) {
+ warn "$My_name: in rdb_ensure_files_here for rule '$rule', there\n",
+ " is a double quote in the filename: '$_'.\n",
+ " I cannot handle this, will ignore this file.\n";
+ next;
+ }
+ if (! exists ${$PHsource}{$_} ) {
+ ${$PHsource}{$_} = [fdb_get($_, $$Prun_time), '', 0];
+ }
+ }
+} #DN rdb_ensure_files_here
+
+#************************************************************
+
+sub rdb_ensure_new_files_here {
+ # rdb_ensure_new_files_here( file, ...)
+ # Assumes rule context
+ # Ensures the given files are in the source file list.
+ # For added files, initialize state to non-existent,
+ # as is appropriate if the file is new to the rule
+ use strict;
+ our ($rule, $My_name, $PHsource, @nofile);
+ foreach (@_) {
+ if ( /\"/ ) {
+ warn "$My_name: in rdb_ensure_new_files_here for rule '$rule', there\n",
+ " is a double quote in the filename: '$_'.\n",
+ " I cannot handle this, will ignore this file.\n";
+ next;
+ }
+ if (! exists ${$PHsource}{$_} ) {
+ ${$PHsource}{$_} = [@nofile, '', 0];
+ }
+ }
+}
+
+#************************************************************
+
sub rdb_remove_files {
# rdb_remove_file( rule, file, ... )
- # Removes file(s) for the rule.
+ # Removes file(s) for the rule.
my $rule = shift;
if (!$rule) { return; }
local @files = @_;
@@ -10408,37 +10848,86 @@
#************************************************************
-sub rdb_list_source {
- # rdb_list_source( rule )
+sub rdb_get_extra {
+ # rdb_get_extra( rule, key )
+ # Returns value pointed to by key in the rule's extra hash.
+ # Mostly for use when not in context of the given rule
+ # or from user code.
+ use strict;
+ our $PHextra;
+ my ($rule, $key) = @_;
+ my $info = undef;
+ rdb_one_rule( $rule, sub{ $info = $$PHextra{$key}; } );
+ return $info;
+} #END rdb_get_extra
+
+#************************************************************
+
+sub rdb_set_extra {
+ # rdb_set_extra( rule, key, value )
+ # Set value pointed to by key in the rule's extra hash.
+ # Mostly for use when not in context of the given rule,
+ # or from user code.
+ use strict;
+ our $PHextra;
+ my ($rule, $key, $value) = @_;
+ rdb_one_rule( $rule, sub{ $$PHextra{$key} = $value; } );
+} #END rdb_set_extra
+
+#************************************************************
+
+sub rdb_get_source {
+ # rdb_get_source( rule )
# Return array of source files for rule.
- my $rule = shift;
+ use strict;
+ our $PHsource;
+ my $rule = $_[0];
my @files = ();
- rdb_one_rule( $rule,
- sub{ @files = keys %$PHsource; }
- );
+ rdb_one_rule( $rule, sub{ @files = keys %$PHsource; } );
return @files;
-} #END rdb_list_source
+} #END rdb_get_source
#************************************************************
+sub rdb_show_source {
+ # rdb_show_source( rule[, msg] )
+ # Display sorted source files for rule, preceeded by optional message
+ use strict;
+ my ($rule, $msg) = @_;
+ print( $msg ) if $msg;
+ show_array( "Source files for '$rule'", sort( rdb_get_source($rule) ));
+} #END rdb_show_source
+
+#************************************************************
+
sub rdb_set_source {
# rdb_set_source( rule, file, ... )
+ # Set the source file list for rule to given files
+ use strict;
my $rule = shift;
- if (!$rule) { return; }
- my %files = ();
- foreach (@_) {
-# if ( /\"/ ) {next; }
- rdb_ensure_file( $rule, $_ );
- $files{$_} = 1;
- }
- foreach ( rdb_list_source($rule) ) {
- if ( ! exists $files{$_} ) { rdb_remove_files( $rule, $_ ); }
- }
- return;
-} #END rdb_list_source
+ my @files = @_;
+ rdb_one_rule( $rule, sub { rdb_set_source_here( @files ); } );
+} #END rdb_set_source
#************************************************************
+sub rdb_set_source_here {
+ # rdb_set_source_here( file, ... )
+ # Set the source file list for current rule to given files
+ # Rule context assumed.
+ use strict;
+ our ( $rule, $PHsource, $Psource );
+ my @files = @_;
+ push( @files, $$Psource)
+ if ($$Psource);
+ my %deletions = %$PHsource;
+ foreach (@files) { delete $deletions{$_}; }
+ rdb_remove_files( $rule, keys %deletions );
+ rdb_ensure_files_here( @files );
+} #END rdb_set_source
+
+#************************************************************
+
sub rdb_rule_exists {
# Call rdb_rule_exists($rule): Returns whether rule exists.
my $rule = shift;
@@ -10464,7 +10953,12 @@
sub rdb_update_gen_files {
# Assumes rule context. Update source files of rule to current state,
# but only for source files that are generated by this or another rule.
- rdb_do_files(
+ if ($$PHextra{bibx_vetoed} ) {
+ # I will NOT update generated source files for vetoed rule, so that
+ # source file state for the rule corresponds to last actual run of rule
+ return;
+ }
+ rdb_do_files(
sub{ if ( exists $from_rules{$file} ) { &rdb_update1; } }
);
} #END rdb_update_gen_files
@@ -10749,7 +11243,7 @@
my $return_mtime = 0;
foreach my $include (@_)
{
- my $include_mtime = &get_mtime($include);
+ my $include_mtime = get_mtime($include);
# The file $include may not exist. If so ignore it, otherwise
# we'll get an undefined variable warning.
if ( ($include_mtime) && ($include_mtime > $return_mtime) )
@@ -10787,12 +11281,12 @@
sub processing_time {
# Return time used.
# Either total processing time of process and child processes as reported
- # in pieces by times(), or HiRes time since Epoch depending on setting of
+ # in pieces by times(), or time since Epoch depending on setting of
# $times_are_clock.
# That variable is to be set on OSs (MSWin32) where times() does not
# include time for subprocesses.
if ($times_are_clock) {
- return Time::HiRes::time();
+ return time();
}
my ($user, $system, $cuser, $csystem) = times();
return $user + $system + $cuser + $csystem;
@@ -10880,7 +11374,7 @@
# files), which are few in number. Only likely conceivable case for
# having many files is with a big document, for which *latex running
# time is large, so almost certainly that dwarfs run time for several
- # runs of kpsewhich.
+ # runs of kpsewhich.
my ($PHfiles, $format, $ext, $PAfiles, $PAnot_found) = @_;
@$PAfiles = @$PAnot_found = ();
@@ -10900,7 +11394,7 @@
if ( ! /\..*$/ ) { $_ .= ".$ext"; }
push @$PAfiles, $_;
}
-
+
return 1 + $#{$PAnot_found};
} #END find_files
@@ -11001,7 +11495,7 @@
}
}
$cmd =~ s/%[RBTDO]//g;
- $cmd =~ s/%S/@_/g;
+ $cmd =~ s/%S/@args/g;
my @found = ();
local $fh;
if ( $kpsewhich_show || $diagnostics ) {
More information about the tex-live-commits
mailing list.