Infer bib engine from file contents - #19
Merged
Merged
Conversation
yihui
force-pushed
the
master
branch
9 times, most recently
from
May 17, 2020 05:41
7c7780d to
c50d034
Compare
|
|
yihui
force-pushed
the
main
branch
3 times, most recently
from
August 26, 2022 16:01
450bcac to
afb10f3
Compare
yihui
force-pushed
the
main
branch
3 times, most recently
from
April 30, 2026 17:21
8519e1c to
200b062
Compare
Single test file means `CI=true Rscript tests/*.R` works directly without a for loop. Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
The `bib_engine` argument of `latexmk()` defaulted to `bibtex`, so the bibliography of a biblatex + biber document was silently not built (bibtex requires \bibdata/\bibstyle in the .aux file, which biblatex + biber does not produce). Users had to manually set `bib_engine = 'biber'`. Default `bib_engine` to NULL and infer the engine from the auxiliary files generated during compilation: if a .bcf file exists (produced by biblatex with the biber backend), use biber; otherwise use bibtex. The explicit argument and the global option `tinytex.bib_engine` still take precedence. This reworks rstudio#19 to infer from the generated aux files rather than parsing the .tex source with regexes, which is more robust (handles multi-line \usepackage, \RequirePackage, etc.). Co-authored-by: HughParsonage <hugh.parsonage@gmail.com> Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Collaborator
|
Thanks for this, @HughParsonage — the core idea (stop defaulting to I've rebased the PR onto current
Let me know if you'd rather keep the source-parsing approach for any case I've missed. |
Contributor
Author
|
No I think your approach is better. Happy to help! |
[ci skip]
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since biber typically uses biblatex, we can infer bibtex/biber by examining the contents of
file.The pull requests adds some tests, notably running
install_tinytex. I wasn't sure whether this was appropriate or not.