rstudio / rstudio/tinytex

What is `tinytex.verbose = TRUE` supposed to do?

Open
#196 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
R
Stars
1.2k
Forks
127
PR merge metrics
No merged PRs in 30d

Description

I'm moving from MacTeX to TinyTeX, and for a legacy project I've found that I need to use LuaLaTeX and Biber for typesetting and references. Consequently I'm typesetting using tinytex::latexmk('talk.tex', engine = 'lualatex', bib_engine = 'biber'). I'm trying to track down a missing reference warning, and can't find where (if anywhere) the biber messages are being logged. Based on some other responses to issues in this repo, I thought options(tinytex.verbose = TRUE) might be helpful. Basically I expected it to show me the lua and biber messages as they're generated, similar to the "typesetting" windows in TeX Shop and similar software. But it doesn't seem to change the output of the latexmk() call in any way — all I see is the same minimal output:

[1] "talk.pdf"
Warning message:
LaTeX Warning: There were undefined references.
Package biblatex Warning: Please rerun LaTeX.
(biblatex)                Page breaks have changed.

So, what is tinytex.verbose = TRUE supposed to do?


By filing an issue to this repo, I promise that

  • I have fully read the issue guide at https://yihui.org/issue/.
  • I have provided the necessary information about my issue.
    • If I'm asking a question, I have already asked it on Stack Overflow or RStudio Community, waited for at least 24 hours, and included a link to my question there.
    • If I'm filing a bug report, I have included a minimal, self-contained, and reproducible example, and have also included xfun::session_info('tinytex'). I have upgraded all my packages to their latest versions (e.g., R, RStudio, and R packages), and also tried the development version: remotes::install_github('yihui/tinytex').
    • If I have posted the same issue elsewhere, I have also mentioned it in this issue.
  • I have learned the Github Markdown syntax, and formatted my issue correctly.

I understand that my issue may be closed if I don't fulfill my promises.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the tinytex::latexmk() call described in the issue and investigate what options(tinytex.verbose = TRUE) is intended to expose when using LuaLaTeX and Biber. Compare the command's output with the expected LuaLaTeX and Biber messages; done means the option's behavior is clarified or the missing output is addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
latex, r
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.