Yes, this does look quite awkward to fix. But maybe mention the problem and
workaround for MiKTeX users in the documentation somewhere?
Thanks again for your help.
___
bug-auctex mailing list
bug-auctex@gnu.org
Hi John,
> John Holman writes:
> Many thanks - your suggestion to use the customize option to add
> --max-print-line=1000 to the pdflatex command line works at least for the
> current test case.
> Adding -max-print-line=1000 - one hyphen rather than two - also works.
Thanks for the
Hi Ikumi
Many thanks - your suggestion to use the customize option to add
--max-print-line=1000 to the pdflatex command line works at least for the
current test case.
Adding -max-print-line=1000 - one hyphen rather than two - also works.
Perhaps auctex should be changed to add this as standard,
Hi John,
> John Holman writes:
> Document preview works when the filename has no more than 22 characters,
> e.g. test.tex, but fails with message "Ghostscript filter: No bounding box"
> when the filename has more, e.g. 01234567890123456789012.tex. However
> buffer preview always works.
I
Have to say this explanation seems unlikely to me at first sight. File path
limit MAX_PATH is 260 but here we have
C:\Users\johng\temp\textest\01234567890123456789012.tex which is only
about 50. Routinely deal with much longer paths than this using windows
without a problem. Similarly max command
John Holman writes:
> Hi. I'm not sure that the problem was captured in the log below created
> by preview-report-bug so a few more details first:
>
> Running auctex on windows 11 with MiKTeX
>
> Test file contents (but most files containing maths seem to trigger the
> problem)
>
>
Hi. I'm not sure that the problem was captured in the log below created
by preview-report-bug so a few more details first:
Running auctex on windows 11 with MiKTeX
Test file contents (but most files containing maths seem to trigger the
problem)
\documentclass{article}
\begin{document}
\(x=y\)
