texlive[68110] trunk: texfot (30aug23)
commits+karl at tug.org
commits+karl at tug.org
Wed Aug 30 01:21:55 CEST 2023
Revision: 68110
http://tug.org/svn/texlive?view=revision&revision=68110
Author: karl
Date: 2023-08-30 01:21:55 +0200 (Wed, 30 Aug 2023)
Log Message:
-----------
texfot (30aug23)
Modified Paths:
--------------
trunk/Build/source/texk/texlive/linked_scripts/texfot/texfot.pl
trunk/Master/texmf-dist/doc/man/man1/texfot.1
trunk/Master/texmf-dist/doc/man/man1/texfot.man1.pdf
trunk/Master/texmf-dist/scripts/texfot/texfot.pl
Modified: trunk/Build/source/texk/texlive/linked_scripts/texfot/texfot.pl
===================================================================
--- trunk/Build/source/texk/texlive/linked_scripts/texfot/texfot.pl 2023-08-29 23:21:43 UTC (rev 68109)
+++ trunk/Build/source/texk/texlive/linked_scripts/texfot/texfot.pl 2023-08-29 23:21:55 UTC (rev 68110)
@@ -1,5 +1,5 @@
#!/usr/bin/env perl
-# $Id: texfot,v 1.48 2022/12/16 02:15:30 karl Exp $
+# $Id: texfot,v 1.50 2023/08/29 15:20:57 karl Exp $
# Invoke a TeX command, filtering all but interesting terminal output;
# do not look at the log or check any output files.
# Exit status is that of the subprogram.
@@ -8,7 +8,7 @@
#
# Public domain. Originally written 2014 by Karl Berry.
-my $ident = '$Id: texfot,v 1.48 2022/12/16 02:15:30 karl Exp $';
+my $ident = '$Id: texfot,v 1.50 2023/08/29 15:20:57 karl Exp $';
(my $prg = $0) =~ s,^.*/,,;
select STDERR; $| = 1; # no buffering
select STDOUT; $| = 1;
@@ -266,9 +266,8 @@
C<texfot> does not look at the log file or any other possible output
file(s); it only looks at the standard output and standard error from
-the command. stdout is processed first, then stderr. Lines from stderr
-have an identifying prefix. C<texfot> writes all accepted lines to its
-stdout.
+the command. stdout is processed first, then stderr. C<texfot> writes
+all accepted lines to its stdout.
The messages shown are intended to be those which likely need action by
the author: error messages, overfull and underfull boxes, undefined
@@ -310,9 +309,10 @@
=item 6.
Otherwise, the default: if the line came from stdout, ignore it; if the
-line came from stderr, print it (to stdout). This distinction is made
-because TeX engines write relatively few messages to stderr, and it's
-likely that any such should be considered.
+line came from stderr, print it (to stdout), with the prefix
+S<C<[stderr] >>. This distinction is made because TeX engines write
+relatively few messages to stderr, and it's likely that any such should
+be considered.
=back
@@ -319,6 +319,19 @@
Once a particular check matches, the program moves on to process the
next line.
+C<texfot> matches exclusively line-by-line; however, TeX itself folds
+output lines, typically at column 79. This means matches might fail
+because the text being matched was split over two lines. To work around
+this, you can effectively turn off TeX's folding by setting the
+C<max_print_line> parameter to a large number, either in the environment
+or on the command:
+
+ # When errors are missed due to TeX's folding of lines:
+ texfot pdftex --cnf-line max_print_line=999 file.tex
+
+ # Equivalently:
+ env max_print_line=999 texfot pdftex file.tex
+
Don't hesitate to peruse the source to the script, which is essentially
a straightforward loop matching against the different lists as above.
You can see the exact regexps being matched in the different categories
@@ -333,14 +346,15 @@
=head1 OPTIONS
The following are the options to C<texfot> itself (not the TeX engine
-being invoked; consult the TeX documentation or the engine's C<--help>
-output for that).
+being invoked; consult the engine documentation or C<--help> output for
+that).
The first non-option terminates C<texfot>'s option parsing, and the
remainder of the command line is invoked as the TeX command, without
further parsing. For example, C<texfot --debug tex
--debug> will output debugging information from both C<texfot> and
-C<tex>.
+C<tex>. TeX engines, unlike many standard programs, require that options
+be specified before the input filename or text.
Options may start with either - or --, and may be unambiguously
abbreviated. It is best to use the full option name in scripts, though,
@@ -381,11 +395,11 @@
=item C<--no-quiet>
By default, the TeX command being invoked is reported on standard
-output. C<--quiet> omits that reporting. To get a completely silent run,
+output; C<--quiet> omits that reporting. To get a completely silent run,
redirect standard output: S<C<texfot ... E<gt>/dev/null>>. (The only
messages to standard error should be errors from C<texfot> itself, so it
-shouldn't be necessary to redirect that, but of course that can be done
-as well.)
+shouldn't be necessary to redirect that, but of course that could be
+done as well.)
=item C<--stderr>
@@ -422,7 +436,7 @@
=head1 RATIONALE
I wrote this because, in my work as a TUGboat editor
-(L<https://tug.org/TUGboat>, journal submissions always welcome!), I run
+(L<https://tug.org/TUGboat>, article submissions always welcome!), I run
and rerun many documents, many times each. It was easy to lose warnings
I needed to see in the mass of unvarying and uninteresting output from
TeX, such as style files being read and fonts being used. I wanted to
@@ -431,7 +445,7 @@
I found some other programs of a similar nature, the LaTeX package
C<silence>, and plenty of other (La)TeX wrappers, but it seemed none of
them did what I wanted. Either they read the log file (I wanted to look
-at only the online output), or they output more or less than I wanted,
+at only the online output), or they output more, or less, than I wanted,
or they required invoking TeX differently (I wanted to keep my build
process exactly the same, most critically the TeX invocation, which can
get complicated). Hence I wrote this little script.
@@ -457,6 +471,6 @@
bug reports. It has no home page beyond the package page on CTAN:
L<https://ctan.org/pkg/texfot>.
- $Id: texfot,v 1.48 2022/12/16 02:15:30 karl Exp $
+ $Id: texfot,v 1.50 2023/08/29 15:20:57 karl Exp $
=cut
Modified: trunk/Master/texmf-dist/doc/man/man1/texfot.1
===================================================================
--- trunk/Master/texmf-dist/doc/man/man1/texfot.1 2023-08-29 23:21:43 UTC (rev 68109)
+++ trunk/Master/texmf-dist/doc/man/man1/texfot.1 2023-08-29 23:21:55 UTC (rev 68110)
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 4.14 (Pod::Simple 3.42)
+.\" Automatically generated by Pod::Man 4.14 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
@@ -133,7 +133,7 @@
.\" ========================================================================
.\"
.IX Title "TEXFOT 1"
-.TH TEXFOT 1 "2022-12-16" "texfot" "Karl Berry"
+.TH TEXFOT 1 "2023-08-29" "texfot" "Karl Berry"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@@ -177,9 +177,8 @@
.PP
\&\f(CW\*(C`texfot\*(C'\fR does not look at the log file or any other possible output
file(s); it only looks at the standard output and standard error from
-the command. stdout is processed first, then stderr. Lines from stderr
-have an identifying prefix. \f(CW\*(C`texfot\*(C'\fR writes all accepted lines to its
-stdout.
+the command. stdout is processed first, then stderr. \f(CW\*(C`texfot\*(C'\fR writes
+all accepted lines to its stdout.
.PP
The messages shown are intended to be those which likely need action by
the author: error messages, overfull and underfull boxes, undefined
@@ -206,13 +205,29 @@
Otherwise, if the line matches the list of regexps to show, show it.
.IP "6." 4
Otherwise, the default: if the line came from stdout, ignore it; if the
-line came from stderr, print it (to stdout). This distinction is made
-because TeX engines write relatively few messages to stderr, and it's
-likely that any such should be considered.
+line came from stderr, print it (to stdout), with the prefix
+\&\f(CW\*(C`[stderr]\ \*(C'\fR. This distinction is made because TeX engines write
+relatively few messages to stderr, and it's likely that any such should
+be considered.
.PP
Once a particular check matches, the program moves on to process the
next line.
.PP
+\&\f(CW\*(C`texfot\*(C'\fR matches exclusively line-by-line; however, TeX itself folds
+output lines, typically at column 79. This means matches might fail
+because the text being matched was split over two lines. To work around
+this, you can effectively turn off TeX's folding by setting the
+\&\f(CW\*(C`max_print_line\*(C'\fR parameter to a large number, either in the environment
+or on the command:
+.PP
+.Vb 2
+\& # When errors are missed due to TeX\*(Aqs folding of lines:
+\& texfot pdftex \-\-cnf\-line max_print_line=999 file.tex
+\&
+\& # Equivalently:
+\& env max_print_line=999 texfot pdftex file.tex
+.Ve
+.PP
Don't hesitate to peruse the source to the script, which is essentially
a straightforward loop matching against the different lists as above.
You can see the exact regexps being matched in the different categories
@@ -226,14 +241,15 @@
.SH "OPTIONS"
.IX Header "OPTIONS"
The following are the options to \f(CW\*(C`texfot\*(C'\fR itself (not the TeX engine
-being invoked; consult the TeX documentation or the engine's \f(CW\*(C`\-\-help\*(C'\fR
-output for that).
+being invoked; consult the engine documentation or \f(CW\*(C`\-\-help\*(C'\fR output for
+that).
.PP
The first non-option terminates \f(CW\*(C`texfot\*(C'\fR's option parsing, and the
remainder of the command line is invoked as the TeX command, without
further parsing. For example, \f(CW\*(C`texfot \-\-debug tex
\&\-\-debug\*(C'\fR will output debugging information from both \f(CW\*(C`texfot\*(C'\fR and
-\&\f(CW\*(C`tex\*(C'\fR.
+\&\f(CW\*(C`tex\*(C'\fR. TeX engines, unlike many standard programs, require that options
+be specified before the input filename or text.
.PP
Options may start with either \- or \-\-, and may be unambiguously
abbreviated. It is best to use the full option name in scripts, though,
@@ -281,11 +297,11 @@
.IX Item "--no-quiet"
.PD
By default, the TeX command being invoked is reported on standard
-output. \f(CW\*(C`\-\-quiet\*(C'\fR omits that reporting. To get a completely silent run,
+output; \f(CW\*(C`\-\-quiet\*(C'\fR omits that reporting. To get a completely silent run,
redirect standard output: \f(CW\*(C`texfot\ ...\ >/dev/null\*(C'\fR. (The only
messages to standard error should be errors from \f(CW\*(C`texfot\*(C'\fR itself, so it
-shouldn't be necessary to redirect that, but of course that can be done
-as well.)
+shouldn't be necessary to redirect that, but of course that could be
+done as well.)
.ie n .IP """\-\-stderr""" 4
.el .IP "\f(CW\-\-stderr\fR" 4
.IX Item "--stderr"
@@ -321,7 +337,7 @@
.SH "RATIONALE"
.IX Header "RATIONALE"
I wrote this because, in my work as a TUGboat editor
-(<https://tug.org/TUGboat>, journal submissions always welcome!), I run
+(<https://tug.org/TUGboat>, article submissions always welcome!), I run
and rerun many documents, many times each. It was easy to lose warnings
I needed to see in the mass of unvarying and uninteresting output from
TeX, such as style files being read and fonts being used. I wanted to
@@ -330,7 +346,7 @@
I found some other programs of a similar nature, the LaTeX package
\&\f(CW\*(C`silence\*(C'\fR, and plenty of other (La)TeX wrappers, but it seemed none of
them did what I wanted. Either they read the log file (I wanted to look
-at only the online output), or they output more or less than I wanted,
+at only the online output), or they output more, or less, than I wanted,
or they required invoking TeX differently (I wanted to keep my build
process exactly the same, most critically the TeX invocation, which can
get complicated). Hence I wrote this little script.
@@ -356,5 +372,5 @@
<https://ctan.org/pkg/texfot>.
.PP
.Vb 1
-\& $Id: texfot,v 1.48 2022/12/16 02:15:30 karl Exp $
+\& $Id: texfot,v 1.50 2023/08/29 15:20:57 karl Exp $
.Ve
Modified: trunk/Master/texmf-dist/doc/man/man1/texfot.man1.pdf
===================================================================
(Binary files differ)
Modified: trunk/Master/texmf-dist/scripts/texfot/texfot.pl
===================================================================
--- trunk/Master/texmf-dist/scripts/texfot/texfot.pl 2023-08-29 23:21:43 UTC (rev 68109)
+++ trunk/Master/texmf-dist/scripts/texfot/texfot.pl 2023-08-29 23:21:55 UTC (rev 68110)
@@ -1,5 +1,5 @@
#!/usr/bin/env perl
-# $Id: texfot,v 1.48 2022/12/16 02:15:30 karl Exp $
+# $Id: texfot,v 1.50 2023/08/29 15:20:57 karl Exp $
# Invoke a TeX command, filtering all but interesting terminal output;
# do not look at the log or check any output files.
# Exit status is that of the subprogram.
@@ -8,7 +8,7 @@
#
# Public domain. Originally written 2014 by Karl Berry.
-my $ident = '$Id: texfot,v 1.48 2022/12/16 02:15:30 karl Exp $';
+my $ident = '$Id: texfot,v 1.50 2023/08/29 15:20:57 karl Exp $';
(my $prg = $0) =~ s,^.*/,,;
select STDERR; $| = 1; # no buffering
select STDOUT; $| = 1;
@@ -266,9 +266,8 @@
C<texfot> does not look at the log file or any other possible output
file(s); it only looks at the standard output and standard error from
-the command. stdout is processed first, then stderr. Lines from stderr
-have an identifying prefix. C<texfot> writes all accepted lines to its
-stdout.
+the command. stdout is processed first, then stderr. C<texfot> writes
+all accepted lines to its stdout.
The messages shown are intended to be those which likely need action by
the author: error messages, overfull and underfull boxes, undefined
@@ -310,9 +309,10 @@
=item 6.
Otherwise, the default: if the line came from stdout, ignore it; if the
-line came from stderr, print it (to stdout). This distinction is made
-because TeX engines write relatively few messages to stderr, and it's
-likely that any such should be considered.
+line came from stderr, print it (to stdout), with the prefix
+S<C<[stderr] >>. This distinction is made because TeX engines write
+relatively few messages to stderr, and it's likely that any such should
+be considered.
=back
@@ -319,6 +319,19 @@
Once a particular check matches, the program moves on to process the
next line.
+C<texfot> matches exclusively line-by-line; however, TeX itself folds
+output lines, typically at column 79. This means matches might fail
+because the text being matched was split over two lines. To work around
+this, you can effectively turn off TeX's folding by setting the
+C<max_print_line> parameter to a large number, either in the environment
+or on the command:
+
+ # When errors are missed due to TeX's folding of lines:
+ texfot pdftex --cnf-line max_print_line=999 file.tex
+
+ # Equivalently:
+ env max_print_line=999 texfot pdftex file.tex
+
Don't hesitate to peruse the source to the script, which is essentially
a straightforward loop matching against the different lists as above.
You can see the exact regexps being matched in the different categories
@@ -333,14 +346,15 @@
=head1 OPTIONS
The following are the options to C<texfot> itself (not the TeX engine
-being invoked; consult the TeX documentation or the engine's C<--help>
-output for that).
+being invoked; consult the engine documentation or C<--help> output for
+that).
The first non-option terminates C<texfot>'s option parsing, and the
remainder of the command line is invoked as the TeX command, without
further parsing. For example, C<texfot --debug tex
--debug> will output debugging information from both C<texfot> and
-C<tex>.
+C<tex>. TeX engines, unlike many standard programs, require that options
+be specified before the input filename or text.
Options may start with either - or --, and may be unambiguously
abbreviated. It is best to use the full option name in scripts, though,
@@ -381,11 +395,11 @@
=item C<--no-quiet>
By default, the TeX command being invoked is reported on standard
-output. C<--quiet> omits that reporting. To get a completely silent run,
+output; C<--quiet> omits that reporting. To get a completely silent run,
redirect standard output: S<C<texfot ... E<gt>/dev/null>>. (The only
messages to standard error should be errors from C<texfot> itself, so it
-shouldn't be necessary to redirect that, but of course that can be done
-as well.)
+shouldn't be necessary to redirect that, but of course that could be
+done as well.)
=item C<--stderr>
@@ -422,7 +436,7 @@
=head1 RATIONALE
I wrote this because, in my work as a TUGboat editor
-(L<https://tug.org/TUGboat>, journal submissions always welcome!), I run
+(L<https://tug.org/TUGboat>, article submissions always welcome!), I run
and rerun many documents, many times each. It was easy to lose warnings
I needed to see in the mass of unvarying and uninteresting output from
TeX, such as style files being read and fonts being used. I wanted to
@@ -431,7 +445,7 @@
I found some other programs of a similar nature, the LaTeX package
C<silence>, and plenty of other (La)TeX wrappers, but it seemed none of
them did what I wanted. Either they read the log file (I wanted to look
-at only the online output), or they output more or less than I wanted,
+at only the online output), or they output more, or less, than I wanted,
or they required invoking TeX differently (I wanted to keep my build
process exactly the same, most critically the TeX invocation, which can
get complicated). Hence I wrote this little script.
@@ -457,6 +471,6 @@
bug reports. It has no home page beyond the package page on CTAN:
L<https://ctan.org/pkg/texfot>.
- $Id: texfot,v 1.48 2022/12/16 02:15:30 karl Exp $
+ $Id: texfot,v 1.50 2023/08/29 15:20:57 karl Exp $
=cut
More information about the tex-live-commits
mailing list.