Discussion:
[AUCTeX] Output parsing problems with LaTeX2e <2017-04-15>
Uwe Siart
2017-04-18 15:03:32 UTC
Permalink
When I type "C-c C-a" even on a very simple document like

\documentclass{article}
\begin{document}
Test
\end{document}

I get

,----
| LaTeX: problems after {1} page
| Type ‘C-c C-l’ to display results of compilation.
| LaTeX: problems after {1} page
| Type ‘C-c C-l’ to display results of compilation.
| LaTeX: problems after {1} page
| Type ‘C-c C-l’ to display results of compilation.
| LaTeX: problems after {1} page
| Type ‘C-c C-l’ to display results of compilation.
| Stopping after running "LaTeX" 4 times in a row.
| LaTeX: problems after {1} page
`----

This happens with AUCTeX 11.90.1 and the recent LaTeX format of
<2017-04-15> (TL17 pretest).

Don't know if this is a problem with AUCTeX or with the latest LaTeX
format.

--
Uwe
Mosè Giordano
2017-04-18 15:18:50 UTC
Permalink
Hi Uwe,

2017-04-18 17:03 GMT+02:00 Uwe Siart <***@tum.de>:
> When I type "C-c C-a" even on a very simple document like
>
> \documentclass{article}
> \begin{document}
> Test
> \end{document}
>
> I get
>
> ,----
> | LaTeX: problems after {1} page
> | Type ‘C-c C-l’ to display results of compilation.
> | LaTeX: problems after {1} page
> | Type ‘C-c C-l’ to display results of compilation.
> | LaTeX: problems after {1} page
> | Type ‘C-c C-l’ to display results of compilation.
> | LaTeX: problems after {1} page
> | Type ‘C-c C-l’ to display results of compilation.
> | Stopping after running "LaTeX" 4 times in a row.
> | LaTeX: problems after {1} page
> `----
>
> This happens with AUCTeX 11.90.1 and the recent LaTeX format of
> <2017-04-15> (TL17 pretest).
>
> Don't know if this is a problem with AUCTeX or with the latest LaTeX
> format.

I don't have problems with TeX Live 2016, so I'd bet on changes in TeX
Live 2017. It would be great if you could provide an example of
output buffer.

Bye,
Mosè
Uwe Siart
2017-04-18 18:02:08 UTC
Permalink
On 18 Apr 2017 at 17:18, Mosè Giordano wrote:

> I don't have problems with TeX Live 2016, so I'd bet on changes in TeX
> Live 2017. It would be great if you could provide an example of
> output buffer.

I can confirm that everything is fine with TL16 final. It only happens
with TL17 pretest. Here's the output buffer:


Running `LaTeX' on `t' with ``pdflatex -file-line-error -interaction=nonstopmode "\input" "t.tex"''
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/W32TeX) (preloaded format=pdflatex)
restricted \write18 enabled.
entering extended mode
LaTeX2e <2017-04-15>
Babel <3.9r> and hyphenation patterns for 83 language(s) loaded.
(./t.tex (c:/Programme/texlive/2017/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(c:/Programme/texlive/2017/texmf-dist/tex/latex/base/size10.clo)) (./t.aux)
[1{c:/Programme/texlive/2017/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]
(./t.aux) )<c:/Programme/texlive/2017/texmf-dist/fonts/type1/public/amsfonts/cm/cmr10.pfb>
Output written on t.pdf (1 page, 10798 bytes).
Transcript written on t.log.

TeX Output finished at Tue Apr 18 19:59:23
Mosè Giordano
2017-04-18 22:06:24 UTC
Permalink
Hi Uwe,

2017-04-18 20:02 GMT+02:00 Uwe Siart <***@tum.de>:
> On 18 Apr 2017 at 17:18, Mosè Giordano wrote:
>
>> I don't have problems with TeX Live 2016, so I'd bet on changes in TeX
>> Live 2017. It would be great if you could provide an example of
>> output buffer.
>
> I can confirm that everything is fine with TL16 final. It only happens
> with TL17 pretest. Here's the output buffer:
>
>
> Running `LaTeX' on `t' with ``pdflatex -file-line-error -interaction=nonstopmode "\input" "t.tex"''
> This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/W32TeX) (preloaded format=pdflatex)
> restricted \write18 enabled.
> entering extended mode
> LaTeX2e <2017-04-15>
> Babel <3.9r> and hyphenation patterns for 83 language(s) loaded.
> (./t.tex (c:/Programme/texlive/2017/texmf-dist/tex/latex/base/article.cls
> Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
> (c:/Programme/texlive/2017/texmf-dist/tex/latex/base/size10.clo)) (./t.aux)
> [1{c:/Programme/texlive/2017/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]
> (./t.aux) )<c:/Programme/texlive/2017/texmf-dist/fonts/type1/public/amsfonts/cm/cmr10.pfb>
> Output written on t.pdf (1 page, 10798 bytes).
> Transcript written on t.log.
>
> TeX Output finished at Tue Apr 18 19:59:23

Thank you so much, I think I can reproduce the error. The problem
should related to the change of date format, now LaTeX2e uses ISO date
yyyy-mm-dd, in addition to yyyy/mm/dd (see the changes on 2017/04/15:
https://www.latex-project.org/news/latex2e-news/). You should be able
to fix this locally by replacing the line

\\(Version\\|ver\\.\\|<[0-9/]*\\(?:u[^>]*\\)?>\\)" nil t)

with

\\(Version\\|ver\\.\\|<[0-9/-]*\\(?:u[^>]*\\)?>\\)" nil t)

in `TeX-LaTeX-sentinel', file tex-buf.el. Can you please confirm this
solves the problem for you?

Thanks,
Mosè
Uwe Siart
2017-04-19 04:54:17 UTC
Permalink
On 19 Apr 2017 at 0:06, Mosè Giordano wrote:

> Hi Uwe,
>
> Thank you so much, I think I can reproduce the error. The problem
> should related to the change of date format, now LaTeX2e uses ISO date
> yyyy-mm-dd, in addition to yyyy/mm/dd (see the changes on 2017/04/15:
> https://www.latex-project.org/news/latex2e-news/). You should be able
> to fix this locally by replacing the line
>
> \\(Version\\|ver\\.\\|<[0-9/]*\\(?:u[^>]*\\)?>\\)" nil t)
>
> with
>
> \\(Version\\|ver\\.\\|<[0-9/-]*\\(?:u[^>]*\\)?>\\)" nil t)
>
> in `TeX-LaTeX-sentinel', file tex-buf.el. Can you please confirm this
> solves the problem for you?

Hello Mosè,

Yes, your fix works perfect. The problem vanishes with this.

Thanks!

Uwe
Mosè Giordano
2017-04-19 22:00:58 UTC
Permalink
Hi Uwe,

2017-04-19 6:54 GMT+02:00 Uwe Siart <***@tum.de>:
> Hello Mosè,
>
> Yes, your fix works perfect. The problem vanishes with this.

Very good. I installed the fix into the repository. Thanks again for
reporting the issue!

Bye,
Mosè
Uwe Siart
2017-04-20 05:05:39 UTC
Permalink
On 20 Apr 2017 at 0:00, Mosè Giordano wrote:

> Very good. I installed the fix into the repository.

Great! Would this fix justify another ELPA release (shortly after the
last one)? Propably, the new LaTeX format will be out in the wild very
soon. TL17 is sheduled for public release beginning of June, but don't
know when MiKTeX users will get it.

--
Uwe
Mosè Giordano
2017-04-21 13:50:34 UTC
Permalink
Tassilo,

there is work for you below ;-)

Bye,
Mosè

2017-04-20 7:05 GMT+02:00 Uwe Siart <***@tum.de>:
> On 20 Apr 2017 at 0:00, Mosè Giordano wrote:
>
>> Very good. I installed the fix into the repository.
>
> Great! Would this fix justify another ELPA release (shortly after the
> last one)? Propably, the new LaTeX format will be out in the wild very
> soon. TL17 is sheduled for public release beginning of June, but don't
> know when MiKTeX users will get it.
>
> --
> Uwe
>
>
Tassilo Horn
2017-04-21 15:09:11 UTC
Permalink
Mosè Giordano <***@gnu.org> writes:

Hi Mosè,

> there is work for you below ;-)

GNU AUCTeX 11.90.2 is on its way!

Bye,
Tassilo
Arash Esbati
2017-04-22 17:38:56 UTC
Permalink
Tassilo Horn <***@gnu.org> writes:

> Mosè Giordano <***@gnu.org> writes:
>
>> there is work for you below ;-)
>
> GNU AUCTeX 11.90.2 is on its way!

Hi all,

besides this, are you aware of any AUCTeX style which should be updated
for TL2017 release? Currently, I see only fontspec.el which should be
touched. And a fontification bug in comment.el where only the first
line in comment environment is fontified in `font-lock-comment-face'.

Best, Arash
Tassilo Horn
2017-04-23 06:58:17 UTC
Permalink
Arash Esbati <***@gnu.org> writes:

Hi Arash,

> besides this, are you aware of any AUCTeX style which should be updated
> for TL2017 release?

Not that I know of but I don't follow the TeXLive development closely.

> Currently, I see only fontspec.el which should be touched.

Feel free to do that. I have no clue if and what changed ther. ;-)

> And a fontification bug in comment.el where only the first line in
> comment environment is fontified in `font-lock-comment-face'.

I've just fixed that. :-)

Bye,
Tassilo
Arash Esbati
2017-04-23 10:14:56 UTC
Permalink
Tassilo Horn <***@gnu.org> writes:

> Arash Esbati <***@gnu.org> writes:
>
>> besides this, are you aware of any AUCTeX style which should be updated
>> for TL2017 release?
>
> Not that I know of but I don't follow the TeXLive development closely.

Hi Tassilo,

yes, same here.

>> Currently, I see only fontspec.el which should be touched.
>
> Feel free to do that. I have no clue if and what changed ther. ;-)

Will do. Most notably, I like the new syntax in macros like \fontspec
et al. where the optional argument comes after the mandatory font name.

>> And a fontification bug in comment.el where only the first line in
>> comment environment is fontified in `font-lock-comment-face'.
>
> I've just fixed that. :-)

Thanks. While you're on top of font-latex.el game again, can you also
have a look at my proposal here?

http://lists.gnu.org/archive/html/auctex-devel/2017-04/msg00011.html

On my wish list is also correct fontification for optional and/or
mandatory arguments of math environments, e.g.:

\documentclass{article}
\usepackage{amsmath}
\usepackage[overload]{empheq}
\begin{document}

\begin{align}
a_1 &= b_1 + c_1
\end{align}

\begin{empheq}{align}
a_1 &= b_1 + c_1
\end{empheq}

\begin{empheq}[left=\empheqlbrace]{align}
\label{eq:2}
a_1 &= b_1 + c_1
\end{empheq}
\end{document}

I think the functions `font-latex-match-math-envII' and
`font-latex-extend-region-backwards-math-envII' should be changed for
this. Right?

Best, Arash
Tassilo Horn
2017-04-24 15:59:37 UTC
Permalink
Arash Esbati <***@gnu.org> writes:

> Thanks. While you're on top of font-latex.el game again, can you also
> have a look at my proposal here?
>
> http://lists.gnu.org/archive/html/auctex-devel/2017-04/msg00011.html

Yes, I have no objections. :-)

> On my wish list is also correct fontification for optional and/or
> mandatory arguments of math environments, e.g.:
>
> \documentclass{article}
> \usepackage{amsmath}
> \usepackage[overload]{empheq}
> \begin{document}
>
> \begin{align}
> a_1 &= b_1 + c_1
> \end{align}
>
> \begin{empheq}{align}
> a_1 &= b_1 + c_1
> \end{empheq}
>
> \begin{empheq}[left=\empheqlbrace]{align}
> \label{eq:2}
> a_1 &= b_1 + c_1
> \end{empheq}
> \end{document}
>
> I think the functions `font-latex-match-math-envII' and
> `font-latex-extend-region-backwards-math-envII' should be changed for
> this. Right?

Absolutly correct. :-)

Bye,
Tassilo
Tassilo Horn
2017-04-18 15:29:36 UTC
Permalink
Uwe Siart <***@tum.de> writes:

Hi Uwe,

> When I type "C-c C-a" even on a very simple document like
>
> \documentclass{article}
> \begin{document}
> Test
> \end{document}
>
> I get
>
> ,----
> | LaTeX: problems after {1} page
> | Type ‘C-c C-l’ to display results of compilation.
> | LaTeX: problems after {1} page
> | Type ‘C-c C-l’ to display results of compilation.
> | LaTeX: problems after {1} page
> | Type ‘C-c C-l’ to display results of compilation.
> | LaTeX: problems after {1} page
> | Type ‘C-c C-l’ to display results of compilation.
> | Stopping after running "LaTeX" 4 times in a row.
> | LaTeX: problems after {1} page
> `----
>
> This happens with AUCTeX 11.90.1 and the recent LaTeX format of
> <2017-04-15> (TL17 pretest).
>
> Don't know if this is a problem with AUCTeX or with the latest LaTeX
> format.

Hm, I still have TeXLive 2015, and there I don't get that error. I'll
try updating to the current version 2016 (not 2017 pretest) and report
back.

Bye,
Tassilo
Tassilo Horn
2017-04-18 17:09:01 UTC
Permalink
Tassilo Horn <***@gnu.org> writes:

>> Don't know if this is a problem with AUCTeX or with the latest LaTeX
>> format.
>
> Hm, I still have TeXLive 2015, and there I don't get that error. I'll
> try updating to the current version 2016 (not 2017 pretest) and report
> back.

Like Mosè, I can't reproduce the issue with TeXLive 2016. How would I
install the 2017 pre-release? (My google foo did not suffice...)

Bye,
Tassilo
Mosè Giordano
2017-04-18 17:11:23 UTC
Permalink
Hi Tassilo,

2017-04-18 19:09 GMT+02:00 Tassilo Horn <***@gnu.org>:
> Like Mosè, I can't reproduce the issue with TeXLive 2016. How would I
> install the 2017 pre-release? (My google foo did not suffice...)

https://www.tug.org/texlive/pretest.html

Bye,
Mosè
Tassilo Horn
2017-04-19 15:10:06 UTC
Permalink
Mosè Giordano <***@gnu.org> writes:

> 2017-04-18 19:09 GMT+02:00 Tassilo Horn <***@gnu.org>:
>> Like Mosè, I can't reproduce the issue with TeXLive 2016. How would I
>> install the 2017 pre-release? (My google foo did not suffice...)
>
> https://www.tug.org/texlive/pretest.html

Thx, installing now.

Bye,
Tassilo
Loading...