Attached is a patch file containing the changes between the CVS version of the Latex bundle and my version. They are as follows:
1a. Improve the parsing of %!TEX lines, so that it conforms to the behaviour of TeXShop. Previously it was too strict about the format; in particular it demanded a single space following the = sign, rather than arbitrary whitespace. (Oddly, a single space before the = sign *is* required.)
1b. Do not ignore "file not found" errors in options.rb. (Why was this done?)
2a. The second group of changes concerns the error handling in the 'Typeset & View' command. Previously, detection of errors depended on parsing the output of the TeX command. However, it is difficult or impossible to do this reliably, because of the variety of forms that error messages can take. The new code also looks at the exit value of the tex process.
2b. While working on the latexErrWarn.py script, I noticed that the code detecting the -v (verbose) option was broken. I have fixed it; but, to conform to existing behaviour, this option is no longer passed to the script.
3. Allow per-file setting (in a %!TEX line) to override the global $TM_LATEX_PROGRAM setting. For backwards compatibility reasons, an exception is made for latexmk. There is a new option $TM_LATEX_COMPILER which does over-ride everything; this should be the recommended way of using frameworks like latexmk in the future. Eventually the latexmk exception should be removed.
Robin
Hi Robin,
very nice work with these changes thanks for doing this!
I just made the changes locally, and tried to compile one of my files through latexmk, and though everything went well, the output window contained the following text as plain text, without any formatting:
Latexmk: This is latexmk, John Collins, 26 February 2007, version: 3.08n. **** Report bugs etc to John Collins . **** Latexmk: Missing input file: 'fancyvrb.cfg' from 'No file ...' line Latexmk: Input bbl file "./TextMateForLaTeX.bbl", so turn on bibtex_mode Latexmk: Found bibliography files [./TextmateAndLaTeX.bib ./pracjourn.bib] ------------ Run number 1 of 'pdflatex -interaction=nonstopmode -file- line-error-style TextMateForLaTeX.tex' ------------ Latexmk: Saving old .aux file "./TextMateForLaTeX.aux" Latexmk: Missing input file: 'fancyvrb.cfg' from 'No file ...' line Latexmk: Input bbl file "./ TextMateForLaTeX.bbl", so turn on bibtex_mode Latexmk: Found bibliography files [./TextmateAndLaTeX.bib ./pracjourn.bib] Latexmk: File "./TextMateForLaTeX.aux" has not changed, so it is valid
This is I am guessing the output from latexmk. Was it supposed to do it like this, or is that a bug?
Haris Skiadas Department of Mathematics and Computer Science Hanover College
On Jul 15, 2007, at 10:45 AM, Robin Houston wrote:
Attached is a patch file containing the changes between the CVS version of the Latex bundle and my version. They are as follows:
1a. Improve the parsing of %!TEX lines, so that it conforms to the behaviour of TeXShop. Previously it was too strict about the format; in particular it demanded a single space following the = sign, rather than arbitrary whitespace. (Oddly, a single space before the = sign *is* required.)
1b. Do not ignore "file not found" errors in options.rb. (Why was this done?)
2a. The second group of changes concerns the error handling in the 'Typeset & View' command. Previously, detection of errors depended on parsing the output of the TeX command. However, it is difficult or impossible to do this reliably, because of the variety of forms that error messages can take. The new code also looks at the exit value of the tex process.
2b. While working on the latexErrWarn.py script, I noticed that the code detecting the -v (verbose) option was broken. I have fixed it; but, to conform to existing behaviour, this option is no longer passed to the script.
- Allow per-file setting (in a %!TEX line) to override the global
$TM_LATEX_PROGRAM setting. For backwards compatibility reasons, an exception is made for latexmk. There is a new option $TM_LATEX_COMPILER which does over-ride everything; this should be the recommended way of using frameworks like latexmk in the future. Eventually the latexmk exception should be removed.
Robin <latex-bundle.patch> <mime-attachment.txt>
On 7/15/07, Charilaos Skiadas skiadas@hanover.edu wrote:
This is I am guessing the output from latexmk. Was it supposed to do it like this, or is that a bug?
Hmm, I suppose it's probably a bug. I don't have time to investigate why it's happening right now; I'll take a look later or tomorrow.
Thanks.
Robin
On Jul 15, 2007, at 11:24 AM, Robin Houston wrote:
On 7/15/07, Charilaos Skiadas skiadas@hanover.edu wrote:
This is I am guessing the output from latexmk. Was it supposed to do it like this, or is that a bug?
Hmm, I suppose it's probably a bug. I don't have time to investigate why it's happening right now; I'll take a look later or tomorrow.
I've committed Robin's patch. Please updated your bundles and let us know of any problems. Thanks!
Thanks.
Robin
Haris Skiadas Department of Mathematics and Computer Science Hanover College
On 7/15/07, Robin Houston robin.houston@gmail.com wrote:
Hmm, I suppose it's probably a bug. I don't have time to investigate why it's happening right now; I'll take a look later or tomorrow.
Well, I found time sooner than I expected! See attached.
The problem was that stderr was not being piped through the log parser. I have restored the previous behaviour of merging stderr with stdout, and parsing both as a single stream. (This is probably not ideal, but it's the same as was happening before.)
I also fixed a problem whereby the last character of the TeX status messages was omitted.
Finally, I forgot to mention: the previous patch makes it so that, if you want to use latex+dvips rather than pdflatex, you need only set TM_LATEX_PROGRAM=latex. There is no need to define TEX_PSTRICKS.
Robin
-
Charilaos Skiadas -
Robin Houston