VS Code LaTeX Workshop issue

Stream: FLT

[Kevin Buzzard]

The LaTeX Workshop issue sadly remains :-( I'm very new to LaTeX in VS Code, I've been writing LaTeX in emacs since 1994 and have only decided to switch because of FLT.

...
Chapter 9.
[43] [44] [45]) (./chapter/chtopbestiary.tex [46]
Chapter 10.
[47] [48] [49] [50] [51] [52] [53]) (./chapter/biblio.tex (../print/print.bbl [54] [55]))) [56] (../print/print.aux) )
(see the transcript file for additional information)
Output written on ../print/print.pdf (57 pages).
SyncTeX written on ../print//print.synctex.gz.
Transcript written on ../print//print.log.
Latexmk: No log file was found, neither the expected one, 'print.log', nor one in '.'.
Latexmk: fls file doesn't appear to have been made.
Latexmk: Couldn't read log file 'print.log':
  No such file or directory
----------------------
This message may duplicate earlier message.
Latexmk: Failure in processing file '/media/buzzard/ExternalSSD1TB/lean-projects/FLT/blueprint/src/print':
   *LaTeX didn't generate the expected log file 'print.log'
----------------------
Latexmk: Sometimes, the -f option can be used to get latexmk
  to try to force complete processing.
  But normally, you will need to correct the file(s) that caused the
  error, and then rerun latexmk.
  In some cases, it is best to clean out generated files before rerunning
  latexmk after you've corrected the files.
Latexmk: Getting log file 'print.log'
Latexmk: Errors, so I did not complete making targets
Collected error summary (may duplicate other messages):
  pdflatex: gave an error

[Kevin Buzzard]

buzzard@brutus:~/lean-projects/FLT/blueprint/print$ ls
FLT.bib    print.blg          print.log  print.synctex.gz  web.log
print.aux  print.fdb_latexmk  print.out  web.aux           web.out
print.bbl  print.fls          print.pdf  web.fls           web.pdf
buzzard@brutus:~/lean-projects/FLT/blueprint/print$

[Julian Berman]

(It doesn't matter that you have duplicates really, though if you're on zsh, yeah you should use $path instead of $PATH which automatically deduplicates, and which isn't a string, it's an array so it's half sane)

[Julian Berman]

That error seems like it says "something put print.log in ../print/print.log, and then something else is now looking for print.log, i.e. in the current directory"

[Julian Berman]

so whatever thing generates print.log is not agreeing with latexmk on where print.log belongs

[Kevin Buzzard]

This is no longer about leanblueprint so I'm going to move the conversation into #FLT . On my laptop everything works fine:

...
Chapter 9.
[43] [44] [45]) (/home/buzzard/lean-projects/FLT/blueprint/src/chapter/chtopbestiary.tex [46]
Chapter 10.
[47] [48] [49] [50] [51] [52] [53]) (/home/buzzard/lean-projects/FLT/blueprint/src/chapter/biblio.tex (/home/buzzard/lean-projects/FLT/blueprint/src/print.bbl [54] [55]))) [56] (/home/buzzard/lean-projects/FLT/blueprint/src/print.aux) )
(see the transcript file for additional information)
Output written on /home/buzzard/lean-projects/FLT/blueprint/src/print.pdf (57 pages).
SyncTeX written on /home/buzzard/lean-projects/FLT/blueprint/src/print.synctex.gz.
Transcript written on /home/buzzard/lean-projects/FLT/blueprint/src/print.log.
Latexmk: Found input bbl file 'print.bbl'
Latexmk: Found input bbl file 'print.bbl'
Latexmk: Log file says output to 'print.pdf
...

[Julian Berman]

(I don't know, but what command(s) generate this output?)

[Kevin Buzzard]

"Build LaTeX project (Ctrl+Alt+B)" followed by "Open compiler log" in the subsequent error box

[Kevin Buzzard]

VS Code

Version: 1.95.1
Commit: 65edc4939843c90c34d61f4ce11704f09d3e5cb6
Date: 2024-10-31T05:14:54.222Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Linux x64 6.8.0-49-generic

[Kevin Buzzard]

The latexmkrc files in /blueprint/src/ are identical on the laptop (works fine) and the desktop (doesn't work)

[Eric Wieser]

I switched to using latex workshop half way through my thesis, I'll see if I can work out the config I changed tomorrow

[Kevin Buzzard]

Oh! This error looks far more pertinent:

...
exmf-dist/tex/latex/base/atveryend-ltx.sty) (/usr/share/texlive/texmf-dist/tex/generic/uniquecounter/uniquecounter.sty))) (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty) (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg) (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/xetex.def))) (/usr/share/texlive/texmf-dist/tex/latex/cleveref/cleveref.sty)

! LaTeX Error: File `blueprint.sty' not found.

Type X to quit or <RETURN> to proceed,
or enter new name. (Default extension: sty)

Enter file name:
/media/buzzard/ExternalSSD1TB/lean-projects/FLT/blueprint/src/web.tex:12: Emergency stop.
<read *>

l.12 ^^M

No pages of output.
Transcript written on ../print//web.log.
Latexmk: No log file was found, neither the expected one, 'web.log', nor one in '.'.
Latexmk: fls file doesn't appear to have been made.
Latexmk: Couldn't read log file 'web.log':
  No such file or directory

[Kevin Buzzard]

Maybe this is a blueprint issue after all?

I copied ~/.local/pipx/venvs/leanblueprint/lib/python3.12/site-packages/leanblueprint/templates/blueprint.sty into FLT/blueprint/src/ (it's a 2 line file saying

\DeclareOption*{}
\ProcessOptions

) and now I get a new error:

...
Run number 1 of rule 'pdflatex'
------------
------------
Running 'xelatex -synctex=1 -output-directory=../print/  -synctex=1 -interaction=nonstopmode -file-line-error -recorder  "/media/buzzard/ExternalSSD1TB/lean-projects/FLT/blueprint/src/web.tex"'
------------
This is XeTeX, Version 3.141592653-2.6-0.999995 (TeX Live 2023/Debian) (preloaded format=xelatex)
 restricted \write18 enabled.
entering extended mode
(/media/buzzard/ExternalSSD1TB/lean-projects/FLT/blueprint/src/web.tex
LaTeX2e <2023-11-01> patch level 1
...
tex))) (./macro/common.tex) (./macro/web.tex)
/media/buzzard/ExternalSSD1TB/lean-projects/FLT/blueprint/src/web.tex:19: Undefined control sequence.
l.19 \github
            {https://github.com/ImperialCollegeLondon/FLT/}

/media/buzzard/ExternalSSD1TB/lean-projects/FLT/blueprint/src/web.tex:19: LaTeX Error: Missing \begin{document}.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H <return>  for immediate help.
 ...

[Shreyas Srinivas]

Quick fix: paste the blueprint.sty file into your latex source folder

[Kevin Buzzard]

I just tried this but it doesn't fix my problems. I'm now back to

...
(see the transcript file for additional information)
Output written on ../print/print.pdf (57 pages).
SyncTeX written on ../print//print.synctex.gz.
Transcript written on ../print//print.log.
Latexmk: No log file was found, neither the expected one, 'print.log', nor one in '.'.
Latexmk: fls file doesn't appear to have been made.
Latexmk: Couldn't read log file 'print.log':
  No such file or directory

[Shreyas Srinivas]

And then go to the TeX icon on the left

[Shreyas Srinivas]

In the latex build options, first run "clean the project" or whatever else it is called

[Shreyas Srinivas]

And then explicitly pick the option to build with xelatex

[Kevin Buzzard]

It's compiling! Thanks so much!

[Kevin Buzzard]

So now I'm in the situation where the default build (i.e. the thing that happens whenever I save the LaTeX file I'm working on) fails, but if I explicitly open the latex build options and select Recipe: latexmk (xelatex) then it works. Is there a way of making things work by default?

[Shreyas Srinivas]

Attempt 1 : try this https://stackoverflow.com/a/59719932

[Shreyas Srinivas]

It might not work with recent versions

[Shreyas Srinivas]

Attempt 2: Tinker with this setting: https://github.com/James-Yu/LaTeX-Workshop/wiki/Compile#latex-workshoplatexrecipedefault

[Shreyas Srinivas]

For attempt 2:

1. ctrl+shift+ p. Search for preferences and open settings.
2. In the input box above the preferences, search for

latex-workshop.latex.recipes

[Shreyas Srinivas]

3. Set it to lastUsed

[Shreyas Srinivas]

4. Compile once with xelatex manually as you have been doing

[Shreyas Srinivas]

5. Next time you save, latex workshop should use xelatex by default

[Eric Wieser]

Eric Wieser said:

I switched to using latex workshop half way through my thesis, I'll see if I can work out the config I changed tomorrow

Long delayed, but my config was

.vscode/settings.json

    "latex-workshop.latex.autoBuild.run": "never",
    "latex-workshop.latex.rootFile.doNotPrompt": true,
    "latex-workshop.latex.recipe.default": "latexmk (lualatex)",
    // "latex-workshop.view.pdf.invert": 0.9,
    "latex-workshop.texcount.args": ["-merge", "-inc", "-total"],
    "latex-workshop.latex.tools": [
        {
            "name": "lualatexmk",
            "command": "latexmk",
            "args": [
                "-synctex=1",
                "-shell-escape",
                "-interaction=nonstopmode",
                "-file-line-error",
                "-lualatex",
                "-bibtex",
                "-outdir=%OUTDIR%",
                "%DOC%"
            ],
            "env": {
                "max_print_line": "10000",
                "max_strings": "800000",
                "save_size": "400000",
            }
        }
    ],

[Eric Wieser]

I would guess "latex-workshop.latex.recipe.default": "latexmk (lualatex)", is the one you care about, though with xelatex isntead of lualatex

[Filippo A. E. Nuccio]

You might also want to look at the LaTeX extension setting "Latex-workshop > Latex > Recipe:Default": if you set it to "last", once you build with your preferred recipe then the next call (through a "save") will use the seme recipe.

[Eric Wieser]

That sounds like the same setting as the one I mentioned :)

[Filippo A. E. Nuccio]

Oh it could be. I thought that what you mentioned basically replaces the default recipe.

[Kevin Buzzard]

Shreyas Srinivas said:

For attempt 2:

1. ctrl+shift+ p. Search for preferences and open settings.
2. In the input box above the preferences, search for

latex-workshop.latex.recipes

It's latex-workshop.latex.recipe.default. Thanks!