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.
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
bug: acro can't be used together with \include and \includeonly #229
Comments
This is something I obviously didn't think of… |
great, thanks. It it really a pain to run 1700 pages in one go only to get the acros right :-) looking forward to see the updated file |
Clemens, are you sure your solution works? From a glance at the patch I doubt it. I don't see anything that writes into the include aux files, but that would be needed to know that in a chapter |
@cgnieder my guess was unfortunately correct. The problem is not solved by the new code ashown in the following test:
This means that formatting changes whenever you only run some includes even though everything else is correctly resolved and thenot included files are up-to-date |
You're right. I realized that later, too. |
but I don't think it is that difficult either. What about this approach:
Thus if acro-test-1.tex is skipped your datastructure will still know that |
Yes, but the mechanism for any of |
maybe, haven't looked at the details of the mechanism. Revising it might also help with the code getting slower and slower if you have many acronyms. However, I don't think you must revise: A call to
you say the second part is done by storing in a macro, okay. That doesn't prevent you when reading the include aux files that each record there does exactly this second step (but not doing the typesetting step). So if you put, say
into the aux then at begin document
|
One can argue that this feature but in my opinion it should be considered a bug. If you use acronyms across a large project (in case of TLC 1600+ pages) using
\include
and\includeonly
the results depend on which files are included or excluded and as a result pagination and wording changes. The reason is the use of a separate file for storing the acro information instead of relying on the aux file mechanism. As a side effect that also blocks a precious file handle of which TeX is known to not have enough.While on the outset it might seems nice to keep things separate I would strongly suggest to drop that approach and stick with the aux file mechanism so that data remains available even if only some chapters are processed.
The text was updated successfully, but these errors were encountered: