diff options
Diffstat (limited to 'Master/texmf-dist/doc/man')
| -rw-r--r-- | Master/texmf-dist/doc/man/man1/latexmk.1 | 193 | ||||
| -rw-r--r-- | Master/texmf-dist/doc/man/man1/latexmk.man1.pdf | bin | 215231 -> 213929 bytes |
2 files changed, 94 insertions, 99 deletions
diff --git a/Master/texmf-dist/doc/man/man1/latexmk.1 b/Master/texmf-dist/doc/man/man1/latexmk.1 index 2266b4df6e7..98264b7aa9f 100644 --- a/Master/texmf-dist/doc/man/man1/latexmk.1 +++ b/Master/texmf-dist/doc/man/man1/latexmk.1 @@ -1,4 +1,4 @@ -.TH LATEXMK 1 "17 April 2020" "" +.TH LATEXMK 1 "13 September 2020" "" .SH NAME latexmk \- generate LaTeX document .SH SYNOPSIS @@ -15,7 +15,8 @@ commands to generate a .dvi, .ps, .pdf and/or hardcopy version of the document. .PP By default \fIlatexmk\fR will run the commands necessary to generate -a .dvi file. +a .dvi file, which copies the behavior of earlier versions when only +\fIlatex\fR was available. .PP \fILatexmk\fR can also be set to run continuously with a suitable previewer. In that case the \fIlatex\fR program (or one of its @@ -26,7 +27,7 @@ updates the on-screen view of the compiled document. \fILatexmk\fR determines which are the source files by examining the log file. (Optionally, it also examines the list of input and output files generated by the \fB-recorder\fR option of modern versions of -\fIlatex\fR (and \fIpdflatex\fR, \fIxelatex\fR, \fIlualatex\fR, etc). +\fIlatex\fR (and \fIpdflatex\fR, \fIxelatex\fR, \fIlualatex\fR). See the documentation for the \fB-recorder\fR option of \fIlatexmk\fR below.) When \fIlatexmk\fR is run, it examines properties of the source files, and if any have been changed since the last document @@ -73,7 +74,7 @@ leftover from older versions of \fIlatexmk\fR, but \fBare currently non-functional\fR. More flexibility can be obtained in current versions, since the command strings for running -\fIlatex\fR, \fIpdflatex\fR, etc can now be configured to run multiple +\fI*latex\fR can now be configured to run multiple commands. This also extends the possibility of postprocessing generated files. .PP @@ -111,34 +112,39 @@ In general the command line to invoke \fIlatexmk\fR has the form All options can be introduced by single or double "-" characters, e.g., "latexmk -help" or "latexmk --help". -\fBNote 1\fR: \fBIn addition to the options in the list below, +\fBNote 1\fR: In the documentation, '\fI*latex\fR' means any of the +supported engines, i.e., currently \fIlatex\fR, \fIlualatex\fR, +\fIpdflatex\fR, \fIxelatex\fR. Mention of a specific one of these normally +refers that specific engines. Earlier versions of this documentation +weren't so consistent. + +\fBNote 2\fR: \fBIn addition to the options in the list below, \fIlatexmk\fR recognizes almost all the options recognized by the -\fIlatex\fR, \fIpdflatex\fR programs (and their relatives) in their +\fI*latex\fR in their current TeXLive and MiKTeX implementations. Some of the options for these programs also trigger special action or behavior by \fIlatexmk\fR, in which case they have specific explanations in this document. Otherwise, they -are just passed through to a called \fIlatex\fR or \fIpdflatex\fR +are just passed through to a called \fI*latex\fR program. Run \fIlatexmk\fR with the \fB-showextraoptions\fR to get a list of the options that \fIlatexmk\fR accepts and that are simply -passed through to \fIlatex\fR or \fIpdflatex\fR (etc). See also the +passed through to \fI*latex\fR. See also the explanation of the \fB-showextraoptions\fR option for more information. -\fBNote 2\fR: In this documentation, the program \fIpdflatex\fR is often -referred to. Users of programs like \fIlualatex\fR and \fIxelatex\fR -should know that from \fIlatexmk\fR's point of view, these other -programs behave very like \fIpdflatex\fR, i.e., they make a pdf file from a -tex file, etc. So whenever \fIpdflatex\fR is mentioned without -mention of the other programs, the statements apply equally to -\fIlualatex\fR, \fIxelatex\fR, and any other similar programs. -\fILatexmk\fR can be easily configured to use whichever of these -programs is needed. See the documentation for the following options: -\fB-pdflua\fR, \fB-pdfxe\fR, \fB-lualatex\fR, and \fB-xelatex\fR, -and also see the documentation for the -\fI$pdflatex\fR, \fI$lualatex\fR, and \fI$xelatex\fR configuration variables. -At present \fIlatexmk\fR does not do automatic detection of which -program is to be used. +\fBNote 3\fR: In this documentation, the term \fI*latex\fR is often +referred to, which refers to all the supported \fIlatex\fR-like programs, +whether the original \fIlatex\fR, or the later \fIpdflatex\fR, +\fIxelatex\fR, and \fIlualatex\fR. Users should know that from +\fIlatexmk\fR's point of view, all of these programs behave very much +alike, with the sole exception that by default \fIlatex\fR produces a dvi +file and all the others produce a pdf file. \fILatexmk\fR can be easily +configured to use whichever of these programs is needed. See the +documentation for the following options: \fB-pdflua\fR, \fB-pdfxe\fR, +\fB-lualatex\fR, and \fB-xelatex\fR, and also see the documentation for the +\fI$latex\fR, \fI$pdflatex\fR, \fI$lualatex\fR, and \fI$xelatex\fR +configuration variables. At present \fIlatexmk\fR does not do automatic +detection of which program is to be used. \fBDefinitions of options and arguments\fR @@ -179,11 +185,11 @@ Windows, and is accepted by \fIlatex\fR etc. .TP .B -auxdir=FOO or -aux-directory=FOO -Sets the directory for auxiliary output files of (pdf)latex +Sets the directory for auxiliary output files of *latex (.aux, .log etc). This -achieves its effect by the \fB-aux-directory\fR option of (pdf)latex, +achieves its effect by the \fB-aux-directory\fR option of *latex, which currently is only implemented on the MiKTeX version of -(pdf)latex. +*latex. See also the \fB-outdir\fR/\fB-output-directory\fR options, and the \fI$aux_dir\fR, \fI$out_dir\fR, and \fI$search_path_separator\fR @@ -373,7 +379,7 @@ it. Then all the generated files (.aux, .log, .dvi, .pdf, etc) will be relative to the current directory rather than the source file. This is the default behavior and corresponds to the behavior of the -\fIlatex\fR and \fIpdflatex\fR programs. However, it is not desirable +\fI*latex\fR programs. However, it is not desirable behavior when \fIlatexmk\fR is invoked by a GUI configured to invoke \fIlatexmk\fR with a full pathname for the source file. See the \fB-cd\fR option. @@ -569,7 +575,7 @@ 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 -\fIlatex\fR, \fIpdflatex\fR, etc, and the passing of this option to +\fI*latex\fR, and the passing of this option to these programs is part of \fIlatexmk\fR's implementation of \fB-jobname\fR. @@ -579,7 +585,7 @@ file. The primary purpose is when multiple files are specified on the command line to \fIlatexmk\fR, and you wish to use a jobname with a different file-dependent value for each file. For example, suppose you had .tex files test1.tex and test2.tex, and you wished to compare -the results of compilation by \fIpdflatex\fR and those with +the results of compilation by \fI*latex\fR and those with \fIxelatex\fR. Then under a unix-type operating system you could use the command line @@ -640,7 +646,7 @@ To set the command for running \fIpdflatex\fR (rather than the command for .TP .B -logfilewarninglist .B -logfilewarnings -After a run of \fI(pdf)latex\fR, give a list of warnings about +After a run of \fI*latex\fR, give a list of warnings about undefined citations and references (unless silent mode is on). See also the \fI$silence_logfile_warnings\fR configuration variable. @@ -648,7 +654,7 @@ See also the \fI$silence_logfile_warnings\fR configuration variable. .TP .B -logfilewarninglist- .B -logfilewarnings- -After a run of \fI(pdf)latex\fR, do not give a list of warnings about +After a run of \fI*latex\fR, do not give a list of warnings about undefined citations and references. (Default) See also the \fI$silence_logfile_warnings\fR configuration variable. @@ -751,10 +757,10 @@ no matter where it occurs on the command line. .TP .B -outdir=FOO or -output-directory=FOO -Sets the directory for the output files of (pdf)latex. This achieves -its effect by the \fB-output-directory\fR option of (pdf)latex, which +Sets the directory for the output files of *latex. This achieves +its effect by the \fB-output-directory\fR option of *latex, which currently (Dec. 2011 and later) is implemented on the common versions of -(pdf)latex, i.e., MiKTeX and TeXLive. It may not be present in other +*latex, i.e., MiKTeX and TeXLive. It may not be present in other versions. See also the \fB-auxdir\fR/\fB-aux-directory\fR options, and the @@ -1049,12 +1055,12 @@ the order they appear on the command line. .TP .B -recorder -Give the -recorder option with \fIlatex\fR and \fIpdflatex\fR. In +Give the -recorder option with \fI*latex\fR. In (most) modern versions of these programs, this results in a file of extension \fI.fls\fR containing a list of the files that these programs have read and written. \fILatexmk\fR will then use this file to improve its detection of source files and generated files after a -run of \fIlatex\fR or \fIpdflatex\fR. This is the default setting of +run of \fI*latex\fR. This is the default setting of \fIlatexmk\fR, unless overridden in an initialization file. For further information, see the documentation for the \fI$recorder\fR @@ -1062,7 +1068,7 @@ configuration variable. .TP .B -recorder- -Do not supply the -recorder option with \fIlatex\fR and \fIpdflatex\fR. +Do not supply the -recorder option with \fI*latex\fR. .TP .B -rules @@ -1075,14 +1081,14 @@ processing. (This is the default.) .TP .B -showextraoptions -Show the list of extra \fIlatex\fR and \fIpdflatex\fR options that +Show the list of extra \fI*latex\fR options that \fIlatexmk\fR recognizes, but that it simply passes -through to the programs \fIlatex\fR, \fIpdflatex\fR, etc when they +through to the programs \fI*latex\fR when they are run. These options are (currently) a combination of those allowed by the TeXLive and MiKTeX implementations. (If a particular option is given to \fIlatexmk\fR -but is not handled by the particular implementation of \fIlatex\fR or -\fIpdflatex\fR that is being used, that program will probably give an +but is not handled by the particular implementation of \fI*latex\fR +that is being used, that program will probably give an error message.) These options are very numerous, but are not listed in this documentation because they have no effect on \fIlatexmk\fR's actions. @@ -1097,10 +1103,10 @@ There are also options that are accepted by \fIlatex\fR etc, but instead trigger actions by \fIlatexmk\fR: \fB-help\fR, \fB-version\fR. -Finally, there are certain options for \fIlatex\fR and \fIpdflatex\fR +Finally, there are certain options for \fI*latex\fR (e.g., \fB-recorder\fR) that trigger special actions or behavior by \fIlatexmk\fR itself as well as being passed in some form to the -called \fIlatex\fR and \fIpdflatex\fR program, or that affect other +called \fI*latex\fR program, or that affect other programs as well. These options do have entries in this documentation. These options are: \fB-jobname=STRING\fR, \fB-aux-directory=dir\fR, @@ -1150,7 +1156,7 @@ See also the configuration variable \fI$show_time\fR. .TP .B -use-make -When after a run of \fIlatex\fR or \fIpdflatex\fR, there are warnings +When after a run of \fI*latex\fR, there are warnings about missing files (e.g., as requested by the LaTeX \\input, \\include, and \\includgraphics commands), \fIlatexmk\fR tries to make them by a custom dependency. If no relevant custom dependency with an appropriate @@ -1162,7 +1168,7 @@ Note that the filename may be specified without an extension, e.g., by \\includegraphics{drawing} in a LaTeX file. In that case, \fIlatexmk\fR will try making drawing.ext with ext set in turn to the possible extensions that are relevant for \fIlatex\fR (or as -appropriate \fIpdflatex\fR). +appropriate \fIpdflatex\fR, \fIlualatex\fR, \fIxelatex\fR). See also the documentation for the \fI$use_make_for_missing_files\fR configuration variable. @@ -1217,7 +1223,7 @@ references (i.e., undefined citations or references or about multiply defined references). This is \fBafter\fR \fIlatexmk\fR has completed all the runs it needs to try and resolve references and citations. Thus \fB-Werror\fR causes \fIlatexmk\fR to treat such warnings as -errors, but only when they occur on the last run of (pdf)latex and +errors, but only when they occur on the last run of *latex and only after processing is complete. Also can be set by the configuration variable \fI$warnings_as_errors\fR. @@ -1528,7 +1534,7 @@ files". (See the earlier section "Configuration/Initialization (rc) Files" for the files where the configurations are done.) Syntax for setting these variables is of the following forms: .PP - $bibtex = 'bibtex %O %B'; + $bibtex = 'bibtex %O %S'; .PP for the setting of a string variable, .PP @@ -1659,19 +1665,6 @@ filenames containing spaces.) In case \fIlatexmk\fR's quoting does not work correctly on your system, you can turn it off -- see the documentation for the variable \fI$quote_filenames\fR. .PP -The distinction between %B and %R needs a bit of care, since they are -often the same, but not always. For example on a simple document, the -basename of a bibtex run is the same as for the texfile. But in a -document with several bibliographies, the bibliography files will have -a variety of names. Since bibtex is invoked with the basename of the -bibliography file, the setting for the bibtex command should therefore -be -.PP - $bibtex = 'bibtex %O %B'; -.PP -Generally, you should use %B rather than %R. Similarly for most -purposes, the name %T of the primary texfile is not a useful -placeholder. See the default values in the section "List of configuration variables usable in initialization files" for what is normally the most @@ -1898,15 +1891,15 @@ command line by the \fB-r\fR option. .TP .B $aux_dir [""] The directory in which auxiliary files (aux, log, etc) are to be -written by a run of (pdf)latex. If this variable is not set, but +written by a run of *latex. If this variable is not set, but \fI$out_dir\fR is set, then \fI$aux_dir\fR is set to \fI$out_dir\fR, which is the directory to which general output files are to be written. \fBImportant note\fR: The effect of \fI$aux_dir\fR, if different from -\fI$out_dir\fR, is achieved by giving \fI(pdf)latex\fR the +\fI$out_dir\fR, is achieved by giving \fI*latex\fR the \fB-aux-directory\fR. Currently (Dec. 2011 and later) this only works on the -MiKTeX version of \fI(pdf)latex\fR. +MiKTeX version of \fI*latex\fR. See also the documentation of \fI$out_dir\fR for some complications on what directory names are suitable. @@ -1980,11 +1973,12 @@ Switch(es) for the biber processing program when silent mode is on. .B $bibtex ["bibtex %O %S"] The BibTeX processing program. .TP -.B $bibtex_fudge [1] -When using bibtex, whether to take special action to allow bibtex to -work when $out_dir or $aux_dir is specified. In May 2018, there was -planned an update to bibtex to correct a bug, after that update, the -special action will no longer be required. +.B $bibtex_fudge [0] +When using bibtex, whether to take special action to allow older +versions of bibtex to +work when $out_dir or $aux_dir is specified. With bibtex from about 2019, +this special action is longer be required; hence the default is not to do +it. .TP .B $bibtex_silent_switch ["-terse"] Switch(es) for the BibTeX processing program when silent mode is on. @@ -2037,7 +2031,7 @@ generation generated files. This operation is somewhat dangerous, and can have unintended consequences, since the files to be deleted are determined from a file -created by (pdf)latex, which can contain erroneous +created by *latex, which can contain erroneous information. Therefore this variable is turned off by default, and then files to be deleted are restricted to those explictly specified by patterns configured in the variables \fIclean_ext\fR, @@ -2238,8 +2232,8 @@ then the dependency list is set to stdout (i.e., normally the screen). .B $do_cd [0] Whether to change working directory to the directory specified for the main source file before processing it. The default behavior is not to -do this, which is the same as the behavior of \fIlatex\fR and -\fIpdflatex\fR programs. This variable is set by the \fB-cd\fR and +do this, which is the same as the behavior of \fI*latex\fR +programs. This variable is set by the \fB-cd\fR and \fB-cd-\fR options on \fIlatexmk\fR's command line. .TP .B $dvi_filter [empty] @@ -2364,7 +2358,7 @@ worry about these settings, and can ignore the following explanation. In almost all situations, \fIlatexmk\fR does not need to use the time stamps of the files it works with. However, there are a couple of situations when it needs to know whether a certain file was created in -the current run of a program (e.g., \fI(pdf)latex\fR) or is a leftover +the current run of a program (e.g., \fI*latex\fR) or is a leftover file from a previous run. It does this by comparing the modification time of the file with the system time just before the program was started. If the modification time is earlier than when the program was @@ -2416,11 +2410,11 @@ This contains a list of extensions for files that are generated during a LaTeX run and that are read in by LaTeX in later runs, either directly or indirectly. -This list specifies files known to be generated by latex (and -pdflatex, etc). It is used in two ways: +This list specifies files known to be generated by \fI*latex\fR. +It is used in two ways: (a) The specified files are deleted in a cleanup operation (with the \fB-c\fR, \fB-C\fR, \fB-CA\fR, \fB-g\fR and \fB-gg\fR options), and -(b) It affects the determination of whether a rerun of (pdf)LaTeX is +(b) It affects the determination of whether a rerun of *latex is needed after a run that gives an error. (Concerning item (b): Normally, a change of a source file during a run @@ -2693,13 +2687,13 @@ The index processing program. \fBSwitch(es)\fR for the index processing program when silent mode is on. .TP .B $max_repeat [5] -The maximum number of times \fIlatexmk\fR will run latex/pdflatex +The maximum number of times \fIlatexmk\fR will run \fI*latex\fR before deciding that there may be an infinite loop and that it needs -to bail out, rather than rerunning latex/pdflatex again to resolve +to bail out, rather than rerunning \fI*latex\fR again to resolve cross-references, etc. The default value covers all normal cases. (Note that the "etc" covers a lot of cases where one run of -latex/pdflatex generates files to be read in on a later run.) +\fI*latex\fR generates files to be read in on a later run.) .TP .B $MSWin_back_slash [1] This configuration variable only has an effect when \fIlatexmk\fR is @@ -2735,10 +2729,10 @@ same file, and if one is running will not start a new one. If .B $out_dir [""] If non-blank, this variable specifies the directory in which output files are to be written by a run of -(pdf)latex. See also the variable \fI$aux_dir\fR. +*latex. See also the variable \fI$aux_dir\fR. The effect of this variable (when non-blank) is achieved by using the -\fB-output-directory\fR option of (pdf)latex. This exists in the +\fB-output-directory\fR option of *latex. This exists in the usual current (Dec. 2011 and later) implementations of TeX, i.e., MiKTeX and TeXLive. But it may not be present in other versions. @@ -3046,26 +3040,26 @@ true), then quoting is done. Otherwise quoting is omitted. The quoting method used by \fIlatexmk\fR 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 \fIlatex\fR and \fIpdflatex\fR cannot +spaces. (But note that many versions of \fI*latex\fR cannot correctly deal with TeX files whose names contain spaces. \fILatexmk\fR's quoting only ensures that such filenames are correctly treated by the operating system in passing arguments to programs.) .TP .B $recorder [1] -Whether to use the \fB-recorder\fR option to \fIlatex\fR and -\fIpdflatex\fR. Use of this option results in a file of extension +Whether to use the \fB-recorder\fR option to \fI(latex\fR +Use of this option results in a file of extension \fI.fls\fR containing a list of the files that these programs have read and written. \fILatexmk\fR will then use this file to improve its detection of source files and generated files after a run of -\fIlatex\fR or \fIpdflatex\fR. +\fI*latex\fR. It is generally recommended to use this option (or to configure the \fI$recorder\fR variable to be on.) But it only works if -\fI(pdf)latex\fR supports the -recorder option, which is true for most +\fI*latex\fR supports the -recorder option, which is true for most current implementations \fINote about the name of the .fls file:\fR Most implementations of -\fI(pdf)latex\fR produce an .fls file with the same basename as the +\fI*latex\fR produce an .fls file with the same basename as the main document's LaTeX, e.g., for Document.tex, the .fls file is Document.fls. However, some implementations instead produce files named for the program, i.e., latex.fls or pdflatex.fls. In this @@ -3079,9 +3073,9 @@ BIBINPUTS, and BSTINPUTS. This variable is mainly used by \fB-auxdir\fR, and/or \fB-aux-directory\fR options are used. In that case \fIlatexmk\fR needs to communicate appropriately modified search paths to \fIbibtex\fR, \fIdvipdf\fR, \fIdvips\fR, and -\fI(pdf)latex\fR. +\fI*latex\fR. -[Comment to technically savvy readers: \fI(pdf)latex\fR doesn't +[Comment to technically savvy readers: \fI*latex\fR doesn't actually need the modified search path. But, surprisingly, \fIdvipdf\fR and \fIdvips\fR do, because sometimes graphics files get generated in the output or aux @@ -3101,12 +3095,12 @@ Unix collection.) Whether to show CPU time used. .TP .B $silence_logfile_warnings [0] -Whether after a run of (pdf)latex to summarize warnings in the log +Whether after a run of *latex to summarize warnings in the log file about undefined citations and references. Setting $silence_logfile_warnings=0 gives the summary of warnings (provided silent mode isn't also set), and this is useful to locate undefined citations and references without searching through the much more -verbose log file or the screen output of (pdf)latex. But the summary +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 \fB-silence_logfile_warning_list\fR and @@ -3152,7 +3146,7 @@ variable TMPDIR if it exists, otherwise "/tmp". .TP .B $use_make_for_missing_files [0] Whether to use \fImake\fR to try and make files that are missing after -a run of \fIlatex\fR or \fIpdflatex\fR, and for which a custom +a run of \fI*latex\fR, and for which a custom dependency has not been found. This is generally useful only when \fIlatexmk\fR is used as part of a bigger project which is built by using the \fImake\fR program. @@ -3185,7 +3179,7 @@ defined references). This is \fBafter\fR \fIlatexmk\fR has completed all the runs it needs to try and resolve references and citations. Thus \fI$warnings_as_errors\fR being nonzero causes \fIlatexmk\fR to treat such warnings as errors, but only when they occur on the last -run of (pdf)latex and only after processing is complete. A non-zero +run of *latex and only after processing is complete. A non-zero value \fI$warnings_as_errors\fR can be set by the command-line option \fB-Werror\fR. @@ -3195,7 +3189,7 @@ 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 warnings as errors that require the overall build process to be aborted. Of -course, since multiple runs of (pdf)latex are generally needed to +course, since multiple runs of *latex are generally needed to resolve references and citations, what matters is \fInot\fR the warnings on the first run, but the warnings on the \fIlast\fR run; \fIlatexmk\fR takes this into account appropriately. @@ -3325,7 +3319,7 @@ output. .SS How custom dependencies are used: An instance of a custom dependency rule is created whenever -\fIlatexmk\fR detects that a run of latex/pdflatex needs to read a +\fIlatexmk\fR detects that a run of \fI*latex\fR needs to read a file, like a graphics file, whose extension is the to-extension of a custom dependency. Then \fIlatexmk\fR examines whether a file exists with the same name, but with the corresponding from-extension, as @@ -3399,7 +3393,8 @@ 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 \fIpdflatex\fR instead of latex, then you will probably prefer to +If you use \fIpdflatex\fR, \fIlualatex\fR or \fIxelatex\fR instead of +\fIlatex\fR, 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 @@ -3475,7 +3470,7 @@ Examples of their use is given in the following examples, concerning multiple index files and glossaries. The only index-file conversion built-in to \fIlatexmk\fR is from an -".idx" file written on one run of latex/pdflatex to an ".ind" file to +".idx" file written on one run of \fI*latex\fR to an ".ind" file to be read in on a subsequent run. But with the index.sty package, for example, you can create extra indexes with extensions that you configure. \fILatexmk\fR does not know how to deduce the extensions @@ -3527,7 +3522,7 @@ Similar techniques can be applied for glossaries. Those of you with experience with Makefiles, may get concerned that the \fI.ndx\fR file is written during a run of -latex/pdflatex and is always later than the \fI.nnd\fR last read in. +\fI*latex\fR and is always later than the \fI.nnd\fR last read in. Thus the \fI.nnd\fR appears to be perpetually out-of-date. This situation, of circular dependencies, is endemic to latex, and is one of the issues that \fIlatexmk\fR is programmed to overcome. It @@ -3536,7 +3531,7 @@ does a remake when the file contents have actually changed. Of course if you choose to write random data to the \fI.nnd\fR (or the \fI.aux\fR file, etc) that changes on each new run, then you will have -a problem. For real experts: See the \fI%hash_cal_ignore_pattern\fR +a problem. For real experts: See the \fI%hash_calc_ignore_pattern\fR if you have to deal with such problems. .SS Old Method of Defining Custom Dependencies: @@ -3595,7 +3590,7 @@ Example: ensure_path( 'TEXINPUTS', './custom_cls_sty_files//' ); (In this example, the trailing '//' is documented by TeX systems to -mean that latex, pdflatex, etc search for files in the specified +mean that \fI*latex\fR search for files in the specified directory and in all subdirectories.) Technically \fIensure_path\fR works by setting Perl's variable @@ -3874,7 +3869,7 @@ e-mail addresses are not written in their standard form to avoid being harvested too easily.) .SH AUTHOR Current version, by John Collins (username jcc8 at node psu.edu). -(Version 4.69a). +(Version 4.70a). Released version can be obtained from CTAN: <http://www.ctan.org/pkg/latexmk/>, and from the diff --git a/Master/texmf-dist/doc/man/man1/latexmk.man1.pdf b/Master/texmf-dist/doc/man/man1/latexmk.man1.pdf Binary files differindex 64953b74f1d..15ba2e728ae 100644 --- a/Master/texmf-dist/doc/man/man1/latexmk.man1.pdf +++ b/Master/texmf-dist/doc/man/man1/latexmk.man1.pdf |