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!

[Kevin Buzzard]

I have new LaTeX workshop woes on my laptop. I'm on main, CI is green (actually CI is running but I just merged a PR with green CI), leanblueprint all works fine locally so the LaTeX is surely fine, but LaTeX workshop is giving me 1000 errors. I don't know if I'm supposed to be running lualatex or xelatex but neither of them work through latex workshop and both give very odd errors. here is a gist of the beginning of the output up until the first couple of errors with lualatex in latex workshop, which clearly indicate something is wrong because it's literally trying to compile the wrong file. A summary of the error is

Rc files read:
  latexmkrc
Latexmk: This is Latexmk, John Collins, 27 Dec. 2024. Version 4.86a.
Latexmk: applying rule 'lualatex'...
Rule 'lualatex':  Reasons for rerun
Category 'disappeared_gen_this':
  web.aux
  web.out

------------
Run number 1 of rule 'lualatex'
------------
------------
Running 'lualatex  -synctex=1 -interaction=nonstopmode -file-line-error -recorder  "/Users/buzzard/Lean/Projects/FLT/blueprint/src/web.tex"'
------------
This is LuaHBTeX, Version 1.21.0 (TeX Live 2025/Homebrew)
 restricted system commands enabled.
(/Users/buzzard/Lean/Projects/FLT/blueprint/src/web.tex
LaTeX2e <2024-11-01> patch level 2
L3 programming layer <2025-01-18>
 (/opt/homebrew/Cellar/texlive/20250308_1/share/texmf-dist/tex/latex/base/report.cls
Document Class: report 2024/06/29 v1.4n Standard LaTeX document class
(/opt/homebrew/Cellar/texlive/20250308_1/share/texmf-dist/tex/latex/base/size10.clo)) (/opt/homebrew/Cellar/texlive/20250308_1/share/texmf-dist/tex/latex/amsmath/amsmath.sty
For additional information on amsmath, use the `?' option.
...
  [gazillion imports etc deleted]
...
(/opt/homebrew/Cellar/texlive/20250308_1/share/texmf-dist/tex/generic/pgf/libraries/pgflibraryarrows.meta.code.tex))) (./macro/common.tex) (./macro/web.tex)
/Users/buzzard/Lean/Projects/FLT/blueprint/src/web.tex:19: Undefined control sequence.
l.19 \github
            {https://github.com/ImperialCollegeLondon/FLT/}

/Users/buzzard/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.
 ...

l.19 \github{h
              ttps://github.com/ImperialCollegeLondon/FLT/}
/Users/buzzard/Lean/Projects/FLT/blueprint/src/web.tex:20: Undefined control sequence.
l.20 \dochome
             {https://ImperialCollegeLondon.github.io/FLT/docs}

I'm interpreting this as "I am starting to compile the project by running LaTeX on blueprint/src/web.tex directly despite the fact that this isn't the root file". I cannot for the life of me figure out why. I have no idea how latex works nowadays. The only file I can find called latexmkrc is in blueprint/src and it says

$pdf_mode = 1;
$pdflatex = 'xelatex -synctex=1 -output-directory=../print/';
@default_files = ('print.tex');

If I run latexmk -lualatex or latexmk -xelatex in /blueprint/srcit works fine. How have I borked LaTeX workshop on my laptop?

[Shreyas Srinivas]

Follow the same process as before

[Kevin Buzzard]

That's not very specific but otoh I thought I'd tried all reasonable interpretations of that comment before posting. What exactly did I miss?

[Shreyas Srinivas]

Starting here until your :heart: emoji reaction.
Shreyas Srinivas said:

And then go to the TeX icon on the left

[Shreyas Srinivas]

As a rule of thumb this cleans up your folder. I won’t claim this will solve all issues, but it is usually a good starting point.

[Kevin Buzzard]

Tried that before I posted, doesn't fix it. I also tried latexmk -c in /blueprint/src. But can you explain the actual problem instead of just telling me how to solve it? Why is LaTeX trying to tex web.tex? If I try to run lualatex (for example) on that file directly then it fails because it runs into these commands \github and \dochome which don't exist. What is going on?

[Kevin Buzzard]

Note that on my desktop things are fine, and on my laptop other LaTeX projects are working fine with LaTeX Workshop so I am specifically interested in exactly how I have borked my laptop setup.

[Kevin Buzzard]

It's so confusing. I just do things randomly (for example running another LaTeX project on the laptop) and now the error has changed. It's very frustrating not having any understanding of what is going on. Now we are back to the equally obscure error which I had at the top of this thread:

...
[70] (../print/print.aux)

LaTeX Warning: There were undefined references.

 )
(see the transcript file for additional information)
Output written on ../print/print.pdf (71 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: Getting log file 'print.log'
Latexmk: Couldn't read log file 'print.log':
  No such file or directory
Latexmk: Errors, so I did not complete making targets
Collected error summary (may duplicate other messages):
  pdflatex: gave an error

i.e. "I just wrote to print.log and now I can't find print.log".

[Kevin Buzzard]

and now I (a) switch to xelatex (b) copy blueprint.sty from /blueprint/src to /blueprint (c) switch back to lualatex (d) delete blueprint.sty in /blueprint and now it's working again (with both lualatex and xelatex). And now we wait until it breaks again and stops me from working on FLT (having spent 30 minutes failing to fix this earlier today, I gave up and went home so I could continue on my desktop). Not understanding anything is very frustrating, I am debugging blind.

[Kevin Buzzard]

If I could understand the underlying causes of either of these errors (the "there is no command called \github" error and the "I just made print.log but now i can't find it" error) then I would be able to fix them properly instead of just executing arbitrary things until stuff magically gets fixed.

[Shreyas Srinivas]

So if I remember my meddling with the blueprint from two weeks ago correctly, there are actually two main files, web.tex and print.tex for the web and pdf version of the blueprint respectively. Latex workshop tries to find the root latex file of your project and compiles it. It is possible (although I can’t really confirm from here), that latex workshop is confused about which file is the root.

[Shreyas Srinivas]

In addition there are common macros in a common.tex file

[Shreyas Srinivas]

Latex workshop searches your directory to find this root file

[Shreyas Srinivas]

How it does this is explained here : https://github.com/james-yu/latex-workshop/wiki/compile#the-root-file

[Shreyas Srinivas]

One way to force it to pick the correct file is to insert the magic comment.

[Shreyas Srinivas]

For Latex workshop purposes I would suggest putting it in the top level Tex file for PDFs

[Shreyas Srinivas]

Another possible issue is that latex workshop by default expects to work at the top level of the folder hierarchy you have opened in vscode. It used to struggle with this, and I don’t know if that has changed. To work around this, you might want to consider opening the blueprint subfolder in a separate vscode window

[Shreyas Srinivas]

I have avoided dealing with blueprint compilation issues in the public projects I have worked on so far by letting the CI do its thing

[Shreyas Srinivas]

The reason I asked you to clean the latex auxiliary files is that they can often throw a spanner in the compilation process after you fix some errors. Cleaning those auxiliary files means latex essentially starts from a blank slate. Again this depends on what error you fixed and what you changed. I just find it easier to suggest starting from a blank state than getting into latex debugging nightmares. Latex is an aging tool that continues to chug along for want of equally powerful alternatives (Typst for example is a promising candidate) which can be proselytised by prominent academics and pushed onto new students.

[Kevin Buzzard]

Thanks for these hints. The next time I'm in this hell I will see if they help. I agree about LaTeX being an aging tool!

[Shreyas Srinivas]

so what I am seeing here is that latex is confused about where your project begins

[Shreyas Srinivas]

It doesn't have a notion of "the document really starts here" other than "look for files with \documentclass.. and other headers"

[Shreyas Srinivas]

and there are two toplevel files in the blueprint. latex is just picking the first one (web.tex) and running with that

[Shreyas Srinivas]

I think basically most decent latex editors don't understand how to handle this scenario, with two root files compiling to two separate documents, out of the box. (Emacs doesn't count as a decent editor in 2025)

[Shreyas Srinivas]

Even overleaf would struggle

[Shreyas Srinivas]

A good tradeoff here is if the blueprint's default folder structure had two project folders, one for the web and one for the print version. Then if it only let you edit the content files of the print version, copying them to generate the web version, then you wouldn't have this annoying issue.

[Shreyas Srinivas]

Ideally blueprint should be letting you edit a normal latex project generating a pdf and then copying the files into a separate build folders for building its own version of these documents .This is how website tools like jekyll and mdbook have functioned for almost a decade now. You should not have to worry about "web.tex" or "print.tex"

[Shreyas Srinivas]

So the source of your frustration is that everything is held together by duct tape

[Kevin Buzzard]

my blueprint does have two separate folders called print and web, although I have no idea if they're used.

[Shreyas Srinivas]

that's where the final output and some auxiliary files of the blueprint's compilation go

[Shreyas Srinivas]

What I am saying is, that this separation is insufficient. The leanblueprint tool should ideally be creating two entire source folders under a build folder and compiling them. It shouldn't be exposing you to the final files that are compiled directly.

[Shreyas Srinivas]

If it did that, then latex workshop would only see one top level project

[Shreyas Srinivas]

Fwiw, I have been onboarding an Isabelle expert into lean with a small graph theory project. They have had these exact same issues. The current leanblueprint way of setting things up can confuse latex workshop

[Shreyas Srinivas]

what probably triggered this issue now, rather than before, was that you actually ran leanblueprint web. That's when we had trouble.

[Kevin Buzzard]

I'm running that all the time. I usually work on command line

[Shreyas Srinivas]

Are you able to insert the magic comment in print.tex and then run the xelatex build from the latex workshop menu on the left hand side? The CLI will work because there you will usually tell latex “here is the top file”. Lean blueprint CLI will do the same. The only trouble is pointing latex workshop to the correct top file.

[Kevin Buzzard]

The problem has gone away right now so I'm reluctant to do further experimentation. I'll try the magic file thing if I run into this again. Your explanation seems to explain the "I'm insisting on running latex on web.tex" error but not the "I just made print.log but now I can't find it" error. Note that I've never had any problems with leanblueprint since we got the project set up correctly.

[Patrick Massot]

Wow, that was a very long and convoluted way by Shreyas to write “I don’t know”.

[Patrick Massot]

Kevin, I opened a PR fixing you latex-workshop settings for this project.

[Patrick Massot]

Of course the real fix would be to use a decent editor (either emacs or neovim or one of their many variants).

[Shreyas Srinivas]

Patrick Massot said:

Wow, that was a very long and convoluted way by Shreyas to write “I don’t know”.

Tweaking latex workshop settings is another duct tape until something breaks upstream.

[Shreyas Srinivas]

And the magic comment is just the easiest fix to tell latex workshop where to look. Easier than the config fixes. It works until another latex editing tool does something slightly differently

[Kevin Buzzard]

Back in hell again; working on a branch, desktop and laptop, laptop works fine, desktop LaTeX workshop is compiling the wrong file. Full error here, version with truncated lines below but it's the usual "undefined control sequence \github" error

Rc files read:
  /etc/LatexMk
  latexmkrc
Latexmk: This is Latexmk, John Collins, 31 Jan. 2024. Version 4.83.
No existing .aux file, so I'll make a simple one, and require run of *latex.
Latexmk: applying rule 'xelatex'...
Rule 'xelatex':  Reasons for rerun
Category 'other':
  Rerun of 'xelatex' forced or previously required:
    Reason or flag: 'Initial setup'

------------
Run number 1 of rule 'xelatex'
------------
------------
Running 'xelatex -no-pdf -synctex=1 -interaction=nonstopmode -file-line-error -recorder -output-directory="/home/buzzard/FLT/blueprint/print"  "/home/buzzard/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
(/home/buzzard/FLT/blueprint/src/web.tex
LaTeX2e <2023-11-01> patch level 1
L3 programming layer <2024-01-22>
(/usr/share/texlive/texmf-dist/tex/latex/base/report.cls
Document Class: report 2023/05/17 v1.4n Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)) (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
For additional information on amsmath, use the `?' option.
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty)) (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty) (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty)) (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty) (/usr/share/texlive/texmf-dist/tex/latex/amscls/amsthm.sty) (/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty) [many other filenames in brackets omitted] (/usr/share/texlive/texmf-dist/tex/generic/pgf/frontendlayer/tikz/libraries/tikzlibraryquotes.code.tex) (/usr/share/texlive/texmf-dist/tex/generic/pgf/libraries/pgflibraryarrows.meta.code.tex))) (./macro/common.tex) (./macro/web.tex)
/home/buzzard/FLT/blueprint/src/web.tex:19: Undefined control sequence.
l.19 \github
            {https://github.com/ImperialCollegeLondon/FLT/}

/home/buzzard/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.

[Kevin Buzzard]

...and it's randomly fixed. I wish I knew what I'd done.

[Shreyas Srinivas]

latex workshop is compiling web.tex again by the looks of it

[Shreyas Srinivas]

Follow step 1 in these instructions : https://github.com/james-yu/latex-workshop/wiki/compile#the-root-file

[Shreyas Srinivas]

your root file should be print.tex