summaryrefslogtreecommitdiff
path: root/Master
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2013-12-04 00:02:29 +0000
committerKarl Berry <karl@freefriends.org>2013-12-04 00:02:29 +0000
commit2667ac5383dea9c9fe17ac47780210373d753580 (patch)
tree780b51a11ae134bfafa6c8f110e3fb12fdfa4ca2 /Master
parentf077be0a1cb84cd0031d4d47104a836f7cf255be (diff)
latexmk (3dec13)
git-svn-id: svn://tug.org/texlive/trunk@32312 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master')
-rw-r--r--Master/texmf-dist/doc/man/man1/latexmk.14
-rw-r--r--Master/texmf-dist/doc/man/man1/latexmk.man1.pdfbin143562 -> 143481 bytes
-rw-r--r--Master/texmf-dist/doc/support/latexmk/CHANGES3
-rw-r--r--Master/texmf-dist/doc/support/latexmk/COPYING3
-rw-r--r--Master/texmf-dist/doc/support/latexmk/latexmk.pdfbin131776 -> 131801 bytes
-rw-r--r--Master/texmf-dist/doc/support/latexmk/latexmk.txt298
6 files changed, 156 insertions, 152 deletions
diff --git a/Master/texmf-dist/doc/man/man1/latexmk.1 b/Master/texmf-dist/doc/man/man1/latexmk.1
index eba70f11923..f9778ed60ca 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 1L "10 November 2013" ""
+.TH LATEXMK 1L "2 December 2013" ""
.SH NAME
latexmk \- generate LaTeX document
.SH SYNOPSIS
@@ -2403,7 +2403,7 @@ the cases I have tested.
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
-'\\'. Forward slashes are generated by latexmk, to maintain its
+\'\\'. Forward 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
diff --git a/Master/texmf-dist/doc/man/man1/latexmk.man1.pdf b/Master/texmf-dist/doc/man/man1/latexmk.man1.pdf
index 8a5de50a71e..88a913a54fb 100644
--- a/Master/texmf-dist/doc/man/man1/latexmk.man1.pdf
+++ b/Master/texmf-dist/doc/man/man1/latexmk.man1.pdf
Binary files differ
diff --git a/Master/texmf-dist/doc/support/latexmk/CHANGES b/Master/texmf-dist/doc/support/latexmk/CHANGES
index 7bcb1fa67d9..61c1db82295 100644
--- a/Master/texmf-dist/doc/support/latexmk/CHANGES
+++ b/Master/texmf-dist/doc/support/latexmk/CHANGES
@@ -435,3 +435,6 @@ From v. 4.37 to 4.39
In -pvc mode, writing of deps file (caused by the -M and related
options) is per make not per overall run.
+From v. 4.39 to 4.39 documentation update of 2 Dec 2013
+ Correct two errors in documentation and in the file COPYING.
+
diff --git a/Master/texmf-dist/doc/support/latexmk/COPYING b/Master/texmf-dist/doc/support/latexmk/COPYING
index 5b6e7c66c27..b411c8b4fe0 100644
--- a/Master/texmf-dist/doc/support/latexmk/COPYING
+++ b/Master/texmf-dist/doc/support/latexmk/COPYING
@@ -2,7 +2,8 @@
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
- 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
+
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
diff --git a/Master/texmf-dist/doc/support/latexmk/latexmk.pdf b/Master/texmf-dist/doc/support/latexmk/latexmk.pdf
index cc30baf150b..8b8f227c55d 100644
--- a/Master/texmf-dist/doc/support/latexmk/latexmk.pdf
+++ b/Master/texmf-dist/doc/support/latexmk/latexmk.pdf
Binary files differ
diff --git a/Master/texmf-dist/doc/support/latexmk/latexmk.txt b/Master/texmf-dist/doc/support/latexmk/latexmk.txt
index b7c096496a2..bda111a4768 100644
--- a/Master/texmf-dist/doc/support/latexmk/latexmk.txt
+++ b/Master/texmf-dist/doc/support/latexmk/latexmk.txt
@@ -127,7 +127,7 @@ LATEXMK OPTIONS AND ARGUMENTS ON COMMAND LINE
- 10 November 2013 2
+ 2 December 2013 2
@@ -195,7 +195,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 3
+ 2 December 2013 3
@@ -263,7 +263,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 4
+ 2 December 2013 4
@@ -332,7 +332,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 5
+ 2 December 2013 5
@@ -403,7 +403,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 6
+ 2 December 2013 6
@@ -474,7 +474,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 7
+ 2 December 2013 7
@@ -545,7 +545,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 8
+ 2 December 2013 8
@@ -616,7 +616,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 9
+ 2 December 2013 9
@@ -687,7 +687,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 10
+ 2 December 2013 10
@@ -758,7 +758,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 11
+ 2 December 2013 11
@@ -829,7 +829,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 12
+ 2 December 2013 12
@@ -900,7 +900,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 13
+ 2 December 2013 13
@@ -971,7 +971,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 14
+ 2 December 2013 14
@@ -1042,7 +1042,7 @@ HOW TO CHANGE THE WAY LATEXMK BEHAVES, DEALING WITH PROBLEMS, ETC
- 10 November 2013 15
+ 2 December 2013 15
@@ -1113,7 +1113,7 @@ CONFIGURATION/INITIALIZATION (RC) FILES
- 10 November 2013 16
+ 2 December 2013 16
@@ -1184,7 +1184,7 @@ FORMAT OF COMMAND SPECIFICATIONS
- 10 November 2013 17
+ 2 December 2013 17
@@ -1255,7 +1255,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 18
+ 2 December 2013 18
@@ -1326,7 +1326,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 19
+ 2 December 2013 19
@@ -1397,7 +1397,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 20
+ 2 December 2013 20
@@ -1468,7 +1468,7 @@ LIST OF CONFIGURATION VARIABLES USABLE IN INITIALIZATION FILES
- 10 November 2013 21
+ 2 December 2013 21
@@ -1539,7 +1539,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 22
+ 2 December 2013 22
@@ -1610,7 +1610,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 23
+ 2 December 2013 23
@@ -1681,7 +1681,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 24
+ 2 December 2013 24
@@ -1754,7 +1754,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 25
+ 2 December 2013 25
@@ -1827,7 +1827,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 26
+ 2 December 2013 26
@@ -1901,7 +1901,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 27
+ 2 December 2013 27
@@ -1975,7 +1975,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 28
+ 2 December 2013 28
@@ -2049,7 +2049,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 29
+ 2 December 2013 29
@@ -2123,7 +2123,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 30
+ 2 December 2013 30
@@ -2197,7 +2197,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 31
+ 2 December 2013 31
@@ -2273,7 +2273,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 32
+ 2 December 2013 32
@@ -2349,7 +2349,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 33
+ 2 December 2013 33
@@ -2425,7 +2425,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 34
+ 2 December 2013 34
@@ -2501,7 +2501,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 35
+ 2 December 2013 35
@@ -2577,7 +2577,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 36
+ 2 December 2013 36
@@ -2654,7 +2654,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 37
+ 2 December 2013 37
@@ -2731,7 +2731,7 @@ CUSTOM DEPENDENCIES
- 10 November 2013 38
+ 2 December 2013 38
@@ -2808,7 +2808,7 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 39
+ 2 December 2013 39
@@ -2828,37 +2828,38 @@ LATEXMK(1L) LATEXMK(1L)
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 sanity from
- software like MiKTeX that mixes both directory separators; but their
+ 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
+ run of MiKTeX (at least in v. 2.9) for an example of the use of both
directory separators.)
- 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.
+ If you have some general custom dependencies defined in the system or
+ user initialization file, you may find that for a particular project
+ they are undesirable. So you might want to delete the unneeded ones.
For example, you remove any "fig" to "eps" rule by the line
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();
in an initialization file.
- Another example of a custom dependency overcomes a limitation of
- latexmk concerning index files. The only index-file conversion built-
+ Another example of a custom dependency overcomes a limitation of
+ latexmk concerning index files. The only index-file conversion built-
in to latexmk is from an ".idx" file written on one run of latex/pdfla-
- tex to an ".ind" file to be read in on a subsequent run. But with the
+ tex to an ".ind" file to be read in on a subsequent run. But with the
index.sty package you can create extra indexes with extensions that you
configure. Latexmk does not know how to deduce the extensions from the
information it has. But you can easily write a custom dependency. For
- example if your latex file uses the command "\newindex{spe-
+ example if your latex file uses the command "\newindex{spe-
cial}{ndx}{nnd}{Special index}" you will need to convert files with the
- extension .ndx to .nnd. The following lines in an initialization RC
+ extension .ndx to .nnd. The following lines in an initialization RC
file will cause this to happen:
add_cus_dep('ndx', 'nnd', 0, 'makendx2nnd');
@@ -2866,26 +2867,25 @@ LATEXMK(1L) LATEXMK(1L)
system( "makeindex -o \"$_[0].nnd\" \"$_[0].ndx\"" );
}
- (You will need to modify this code if you use filenames with spaces in
+ (You will need to modify this code if you use filenames with spaces in
them, to provide correct quoting of the filenames.)
- Those of you with experience with Makefiles, will undoubtedly be con-
+ Those of you with experience with Makefiles, will undoubtedly be con-
cerned that the .ndx file is written during a run of latex/pdflatex and
- is always later than the .nnd last read in. Thus the .nnd appears to
- be perpetually out-of-date. This situation, of circular dependencies,
+ is always later than the .nnd last read in. Thus the .nnd appears to
+ be perpetually out-of-date. This situation, of circular dependencies,
is endemic to latex, and latexmk in its current version works correctly
- with circular dependencies. It examines the contents of the files (by
- use of an md5 checksum), and only does a remake when the file contents
+ with circular dependencies. It examines the contents of the files (by
+ use of an md5 checksum), and only does a remake when the file contents
have actually changed.
- Of course if you choose to write random data to the .nnd (or and .aux
- file, etc) that changes on each new run, then you will have a problem.
- For real experts: See the %hash_cal_ignore_pattern if you have to deal
- with such problems.
+ Of course if you choose to write random data to the .nnd (or and .aux
+ file, etc) that changes on each new run, then you will have a problem.
+ For real experts: See the %hash_cal_ignore_pattern if you have to deal
- 10 November 2013 40
+ 2 December 2013 40
@@ -2894,20 +2894,22 @@ LATEXMK(1L) LATEXMK(1L)
LATEXMK(1L) LATEXMK(1L)
+ with such problems.
+
Glossaries can be dealt with similarly.
OLD METHOD OF DEFINING CUSTOM DEPENDENCIES
- In previous versions of latexmk, the only method of defining custom
- dependencies was to directly manipulate the table of custom dependen-
+ In previous 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.
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";
@@ -2915,54 +2917,52 @@ OLD METHOD OF DEFINING CUSTOM DEPENDENCIES
system( "fig2dev -Lps \"$_[0].fig\" \"$_[0].eps\"" );
}
- This method still works, and is equivalent to the earlier code using
- the add_cus_dep subroutine, except that it doesn't delete any previous
- custom-dependency for the same conversion. So the new method is
+ This method still works, and is equivalent to the earlier code using
+ the add_cus_dep subroutine, except that it doesn't delete any previous
+ custom-dependency for the same conversion. So the new method is
preferable.
USING latexmk WITH make
- This section is targeted only at advanced users who use the make pro-
+ This section is targeted only at advanced users who use the make pro-
gram for complex projects, as for software development, with the depen-
dencies specified by a Makefile.
- Now the basic task of latexmk is to run the appropriate programs to
- make a viewable version of a LaTeX document. However, the usual make
- program is not suited to this purpose for at least two reasons. First
+ Now the basic task of latexmk is to run the appropriate programs to
+ make a viewable version of a LaTeX document. However, the usual make
+ program is not suited to this purpose for at least two reasons. First
is that the use of LaTeX involves circular dependencies (e.g., via .aux
files), and these cannot be handled by the standard make program. Sec-
- ond is that in a large document the set of source files can change
- quite frequently, particularly with included graphics files; in this
- situation keeping a Makefile manually updated is inappropriate and
- error-prone, especially when the dependencies can be determined auto-
+ ond is that in a large document the set of source files can change
+ quite frequently, particularly with included graphics files; in this
+ situation keeping a Makefile manually updated is inappropriate and
+ error-prone, especially when the dependencies can be determined auto-
matically. Latexmk solves both of these problems robustly.
- Thus for many standard LaTeX documents latexmk can be used by itself
- without the make program. In a complex project it simply needs to be
- suitably configured. A standard configuration would be to define cus-
- tom dependencies to make graphics files from their source files (e.g.,
- as created by the xfig program). Custom dependencies are latexmk's
+ Thus for many standard LaTeX documents latexmk can be used by itself
+ without the make program. In a complex project it simply needs to be
+ suitably configured. A standard configuration would be to define cus-
+ tom dependencies to make graphics files from their source files (e.g.,
+ as created by the xfig program). Custom dependencies are latexmk's
equivalent of pattern rules in Makefiles.
- Nevertheless there are projects for which a Makefile is appropriate,
+ Nevertheless there are projects for which a Makefile is appropriate,
and it is useful to know how to use latexmk from a Makefile. A typical
- example would be to generate documentation for a software project.
- Potentially the interaction with the rest of the rules in the Makefile
+ example would be to generate documentation for a software project.
+ Potentially the interaction with the rest of the rules in the Makefile
could be quite complicated, for example if some of the source files for
a LaTeX document are generated by the project's software.
In this section, I give a couple of examples of how latexmk can be use-
- fully invoked from a Makefile. The examples use specific features of
- current versions of GNU make, which is the default on both linux and
- OS-X systems. They may need modifications for other versions of make.
+ 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
-
- 10 November 2013 41
+ 2 December 2013 41
@@ -2971,6 +2971,7 @@ USING latexmk WITH make
LATEXMK(1L) LATEXMK(1L)
+ The simplest method is simply to delegate all the relevant tasks to
latexmk, as is suitable for a straightforward LaTeX document. For this
a suitable Makefile is like
@@ -2979,33 +2980,33 @@ LATEXMK(1L) LATEXMK(1L)
%.pdf : %.tex FORCE_MAKE
latexmk -pdf -dvi- -ps- $<
- (Note: the last line must be introduced by a tab for the Makefile to
- function correctly!) Naturally, if making try.pdf from its associated
- LaTeX file try.tex were the only task to be performed, a direct use of
- latexmk without a Makefile would normally be better. The benefit of
- using a Makefile for a LaTeX document would be in a larger project,
+ (Note: the last line must be introduced by a tab for the Makefile to
+ function correctly!) Naturally, if making try.pdf from its associated
+ LaTeX file try.tex were the only task to be performed, a direct use of
+ latexmk without a Makefile would normally be better. The benefit of
+ using a Makefile for a LaTeX document would be in a larger project,
where lines such as the above would be only be a small part of a larger
Makefile.
The above example has a pattern rule for making a .pdf file from a .tex
- file, and it is defined to use latexmk in the obvious way. There is a
+ file, and it is defined to use latexmk in the obvious way. There is a
conventional default target named "all", with a prerequisite of
- try.pdf. So when make is invoked, by default it makes try.pdf. The
- only complication is that there may be many source files beyond
+ try.pdf. So when make is invoked, by default it makes try.pdf. The
+ only complication is that there may be many source files beyond
try.tex, but these aren't specified in the Makefile, so changes in them
- will not by themselves cause latexmk to be invoked. Instead, the pat-
- tern rule is equipped with a "phony" prerequisite FORCE_MAKE; this has
- the effect of causing the rule to be always out-of-date, so that
- latexmk is always run. It is latexmk that decides whether any action
- is needed, e.g., a rerun of pdflatex. Effectively the Makefile dele-
+ will not by themselves cause latexmk to be invoked. Instead, the pat-
+ tern rule is equipped with a "phony" prerequisite FORCE_MAKE; this has
+ the effect of causing the rule to be always out-of-date, so that
+ latexmk is always run. It is latexmk that decides whether any action
+ is needed, e.g., a rerun of pdflatex. Effectively the Makefile dele-
gates all decisions to latexmk, while make has no knowledge of the list
- of source files except for primary LaTeX file for the document. If
- there are, for example, graphics files to be made, these must be made
+ of source files except for primary LaTeX file for the document. If
+ there are, for example, graphics files to be made, these must be made
by custom dependencies configured in latexmk.
- But something better is needed in more complicated situations, for
- example, when the making of graphics files needs to be specified by
- rules in the Makefile. To do this, one can use a Makefile like the
+ But something better is needed in more complicated situations, for
+ example, when the making of graphics files needs to be specified by
+ rules in the Makefile. To do this, one can use a Makefile like the
following:
TARGETS = document1.pdf document2.pdf
@@ -3024,22 +3025,21 @@ LATEXMK(1L) LATEXMK(1L)
%.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
- 10 November 2013 42
+ 2 December 2013 42
@@ -3048,25 +3048,26 @@ LATEXMK(1L) LATEXMK(1L)
LATEXMK(1L) LATEXMK(1L)
+ There is now no need for the phony prerequisite for the rule to make
.pdf files from .tex files. But I have added a rule to make .pdf files
- from .fig files produced by the xfig program; these are commonly used
- for graphics insertions in LaTeX documents. Latexmk is arranged to
- output a dependency file after each run. It is given the -recorder
+ from .fig files produced by the xfig program; these are commonly used
+ for graphics insertions in LaTeX documents. Latexmk is arranged to
+ output a dependency file after each run. It is given the -recorder
option, which improves its detection of files generated during a run of
- pdflatex; such files should not be in the dependency list. The -e
- options are used to turn off all custom dependencies, and to document
- this. Instead the -use-make is used to delegate the making of missing
+ pdflatex; such files should not be in the dependency list. The -e
+ options are used to turn off all custom dependencies, and to document
+ this. Instead the -use-make is used to delegate the making of missing
files to make itself.
- Suppose in the LaTeX file there is a command \includegraphics{graph},
- and an xfig file "graph.fig" exists. On a first run, pdflatex reports
- a missing file, named "graph". Latexmk succeeds in making "graph.pdf"
+ Suppose in the LaTeX file there is a command \includegraphics{graph},
+ and an xfig file "graph.fig" exists. On a first run, pdflatex reports
+ a missing file, named "graph". Latexmk succeeds in making "graph.pdf"
by calling "make graph.pdf", and after completion of its work, it lists
"fig.pdf" among the dependents of the file latexmk is making. Then let
- "fig.fig" be updated, and then let make be run. Make first remakes
+ "fig.fig" be updated, and then let make be run. Make first remakes
"fig.pdf", and only then reruns latexmk.
- Thus we now have a method by which all the subsidiary processing is
+ Thus we now have a method by which all the subsidiary processing is
delegated to make.
@@ -3075,34 +3076,34 @@ SEE ALSO
BUGS
Sometimes a viewer (gv) tries to read an updated .ps or .pdf file after
- its creation is started but before the file is complete. Work around:
+ its creation is started but before the file is complete. Work around:
manually refresh (or reopen) display. Or use one of the other preview-
ers and update methods.
- (The following isn't really a bug, but concerns features of preview-
- ers.) Preview continuous mode only works perfectly with certain pre-
- viewers: Xdvi on UNIX/LINUX works for dvi files. Gv on UNIX/LINUX
- works for both postscript and pdf. Ghostview on UNIX/LINUX needs a
- manual update (reopen); it views postscript and pdf. Gsview under MS-
- Windows works for both postscript and pdf, but only reads the updated
- file when its screen is refreshed. Acroread under UNIX/LINUX views
- pdf, but the file needs to be closed and reopened to view an updated
- version. Under MS-Windows, acroread locks its input file and so the
- pdf file cannot be updated. (Remedy: configure latexmk to use suma-
+ (The following isn't really a bug, but concerns features of preview-
+ ers.) Preview continuous mode only works perfectly with certain pre-
+ viewers: Xdvi on UNIX/LINUX works for dvi files. Gv on UNIX/LINUX
+ works for both postscript and pdf. Ghostview on UNIX/LINUX needs a
+ manual update (reopen); it views postscript and pdf. Gsview under MS-
+ Windows works for both postscript and pdf, but only reads the updated
+ file when its screen is refreshed. Acroread under UNIX/LINUX views
+ pdf, but the file needs to be closed and reopened to view an updated
+ version. Under MS-Windows, acroread locks its input file and so the
+ pdf file cannot be updated. (Remedy: configure latexmk to use suma-
trapdf instead.)
THANKS TO
- Authors of previous versions. Many users with their feedback, and
- especially David Coppit (username david at node coppit.org) who made
- many useful suggestions that contributed to version 3, and Herbert
- Schulz. (Please note that the e-mail addresses are not written in
+ Authors of previous versions. Many users with their feedback, and
+ especially David Coppit (username david at node coppit.org) who made
+ many useful suggestions that contributed to version 3, and Herbert
+ Schulz. (Please note that the e-mail addresses are not written in
their standard form to avoid being harvested by worms and viruses.)
AUTHOR
- Current version, by John Collins (username collins at node
+ Current version, by John Collins (username collins at node
phys.psu.edu). (Version 4.39).
- Released version can be obtained from CTAN: <http://www.ctan.org/tex-
+ Released version can be obtained from CTAN: <http://www.ctan.org/tex-
archive/support/latexmk/>, and from the author's website
<http://www.phys.psu.edu/~collins/software/latexmk/>.
Modifications and enhancements by Evan McLean (Version 2.0)
@@ -3115,8 +3116,7 @@ AUTHOR
-
- 10 November 2013 43
+ 2 December 2013 43
@@ -3193,6 +3193,6 @@ LATEXMK(1L) LATEXMK(1L)
- 10 November 2013 44
+ 2 December 2013 44