Skip to content

Fix no errors printed if filename contains apostrophe - #1716

Merged
deathaxe merged 1 commit into
masterfrom
fix/no-error-output
Oct 3, 2026
Merged

deathaxe merged 1 commit into
masterfrom
fix/no-error-output

Conversation

@deathaxe

@deathaxe deathaxe commented Oct 3, 2026

Copy link
Copy Markdown
Member

Fixes #1715

This commit adds apostrophe to the set of sane file name characters, to enable syntax definition parsing unquoted file names containing it.

The bug is triggered by generating PDFs with MikTeX, which does not prepend ./ to relative file names in log files such as TeXLive.

MikTeX

...
(test-1715's file.tex
LaTeX2e <2025-06-01> patch level 1
L3 programming layer <2025-08-13>
...

TeXLive

...
(./test-1715's file.tex
LaTeX2e <2025-06-01> patch level 1
L3 programming layer <2025-08-13>
...

This commit adds apostrophe to the set of sane file name characters,
to enable syntax definition parsing unquoted file names containing it.
@deathaxe
deathaxe merged commit 57e6d92 into master Oct 3, 2026
3 checks passed
@deathaxe
deathaxe deleted the fix/no-error-output branch October 3, 2026 10:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

No warning when file name contains apostrophe

1 participant