rstudio / rstudio/tinytex

Increase latexmk memory limit?

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

Nobody has claimed this yet.

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

Description

Dear TinyTex people,

I've recently been using to vizualize a protein structure from TEX to a .DVI file. The command I use is as simple as:

dviFile <- tinytex::latexmk(proteinTexFile, clean = T, engine = "latex", engine_args = "-shell-escape")

In rare cases (i.e. large proteins) the engine runs out of memory. As I need it to be DVI file I understand I need to use latex engine. I've been trying to increase memory by changing the engine_args value to

dviFile <- tinytex::latexmk(proteinTexFile, clean = T, engine = "latex", engine_args = "-shell-escape -extra_mem_top=10000000 -extra_mem_bot=10000000")

Running the help command on latexmk in linux environment also did not make it any clearer to me.

Any chance I can increase this memory settings within the command itself? As I do not (always) have access as sudo/root.

Kind regards,
Patrick


By filing an issue to this repo, I promise that

  • [X ] I have fully read the issue guide at https://yihui.org/issue/.
  • [ X] 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('rstudio/tinytex').
    • If I have posted the same issue elsewhere, I have also mentioned it in this issue.
  • [X ] 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 invocation in the issue and inspect how its engine and engine_args values are passed to the LaTeX engine. Determine whether memory settings can be supplied without root access; done means documenting or supporting a reliable command-level approach for producing the requested DVI output.

Written by the indexing model from the issue text.

Assessment

Tech stack
latex, r
Domain
build-system, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.