When using the "physics" package in pdfLaTeX (a standard package included in distribution) I get the following error upon compilation:
"Unbalanced parentheses in the log file could not be resolved. Please report this, annexing the log file to the report."
It happens on each run of pdfLaTeX and on all computers that I have been able to test this on.
Thank you for reporting this. Could you provide a minimal tex file to reproduce the problem ?
Sure thing. Here you are
Related
Tickets:
#211Sure thing.
Thanks for reporting this and thanks for the log file.
There is indeed an unbalanced parenthesis in line 565 of the log file,
issued by the package as part of some message from the package.
A minimal patch would consist in taking exception for this kind of message.
But potentially other packages could issue messages with unbalanced
parentheses and there is no point in trying to detect them in packages,
since presumably packages have no errors (the parens matching is
only for the sake of error browsing), so a more thorough fix would consist
in only starting the parens matching business once tex actually begins
reading the main input file. I will look into this.
Cheers, Joachim.
My last sentence does not make sense, because all packages are of course input from the main file.
But it is true that I will look into a better fix.
Hi Matt,
In my experience, once this happens the unbalanced parameters sit in the log file and kills all subsequent runs of LaTeX. It may not solve the problem but, if you haven’t done so, delete the existing log file (I usually throw out everything except the source files) and start the process as though it is the first time it has been run. That often helps, although is a workaround rather than a real fix for the problem.
I hope this helps.
Cheers, Chris.
From: Joachim Kock via AlphaCocoa-devel alphacocoa-devel@lists.sourceforge.net
Reply-To: "[alphacocoa:tickets]" 211@tickets.alphacocoa.p.re.sourceforge.net
Date: Saturday, 22 December 2018 at 8:15 am
To: "alphacocoa-devel@lists.sourceforge.net" alphacocoa-devel@lists.sourceforge.net
Cc: Joachim Kock jkock@users.sourceforge.net
Subject: [Alphacocoa-devel] [alphacocoa:tickets] #211 TeX Mode error using standard package
My last sentence does not make sense, because all packages are of course input from the main file.
But it is true that I will look into a better fix.
[tickets:#211]https://sourceforge.net/p/alphacocoa/tickets/211/ TeX Mode error using standard package
Status: open
Created: Fri Dec 21, 2018 05:54 PM UTC by Matt Haddad
Last Updated: Fri Dec 21, 2018 09:12 PM UTC
Owner: nobody
Attachments:
When using the "physics" package in pdfLaTeX (a standard package included in distribution) I get the following error upon compilation:
"Unbalanced parentheses in the log file could not be resolved. Please report this, annexing the log file to the report."
It happens on each run of pdfLaTeX and on all computers that I have been able to test this on.
Sent from sourceforge.net because alphacocoa-devel@lists.sourceforge.net is subscribed to https://sourceforge.net/p/alphacocoa/tickets/https://sourceforge.net/p/alphacocoa/tickets/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/alphacocoa/admin/tickets/options.https://sourceforge.net/p/alphacocoa/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
Related
Tickets:
#211Hi again,
a miminal fix is to add these three lines to tetexComm.tcl, in line 2080 (after the other entries of the patList):
I have tested it. Would you apply the patch, Bernard? I have some trouble with svn :-(
In the long run, I want to revise the whole logfile scanning mechanism. It is not fair that this error message should bother innocent users who might not even use error browsing. It should be decoupled from the general tex run and only be performed on the fly when error browsing is invoked. And the error handling should be more graceful. I will implement this structural change and test it thoroughly over the coming weeks.
Cheers, Joachim.
Thank you Joachim for looking into this. I have just committed your patch to the repository (rev. 1607).