Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Line breaks are not parsed correctly when using #58

Open
jmpzero opened this issue Oct 10, 2018 · 1 comment · May be fixed by #66
Open

Line breaks are not parsed correctly when using #58

jmpzero opened this issue Oct 10, 2018 · 1 comment · May be fixed by #66

Comments

@jmpzero
Copy link

jmpzero commented Oct 10, 2018

The two regular expressions don't seem to work, when the whole path is multiline

r'^Transcript written on "?(.* )\.log"?\.$'
and
r'^Output written on "?(.*\. [^ ."]+)"? \([0-9]+ page'

Files were located in a path, where the the output for transcript and output would not fit into a single line. The script immediately broke, even though the regular expression should support multilines.
@jmpzero
Copy link
Author

jmpzero commented Oct 10, 2018

This happens especially when

Transcript written on /home/jmpzero/tex/test
.log.

or

Output written on /home/jmpzero/tex/test.pdf
(2 pages, , 89632 bytes).

@jmpzero jmpzero mentioned this issue Oct 10, 2018
Open
@lazdmx lazdmx linked a pull request May 29, 2019 that will close this issue
Open
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Log pathnames support lazdmx/latexrun
1 participant
@jmpzero