Tectonic setup in VSCode with Latex Workshop #1181
Unanswered
thuvasooriya
asked this question in
Q&A
Replies: 1 comment 2 replies
-
If you install Tectonic with homebrew on macOS, it will be automatically added to the PATH. You don't need to add the PATH to TinyTeX.
Actually, I think what you are doing here is breaking the PATH variable, just remove the env variables. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've recently found tectonic and fell in love with it as it compiles my somewhat complex latex project with just one command with no effort. CLI and the tool is topnotch but I had to go through what I would call a trial by fire to set it up in vscode with latex workshop to make it work somewhat reliable. Noob alert. It took me about 2 days. Most of it has to do with me and the dumb decisions I made.
I couldn't get tectonic command to get detected by the extension due to some path issue with the extension with nix installed packages which works in CLI anyway.
I have referenced the other discussion here about the VSCode setup and a whole lot of reading docs and this is what I could come up with.
I wanted to use TinyTeX if I must install another TeXLive since I didn't know any better to fix the latexindent error but finally had to install a homebrew package and set the path to make it work.
This is clearly not ideal and I'm somewhat stressed with the things I might be doing wrong.
https://github.com/thuvasooriya/tectomin
Please point out the things I can do to improve this to flush the configuration to make it work with minimal effort in a new machine.
Some specific issues I faced:
What should I do to make other latex workshop features (like synctex and other tools) work?
Even when I change only a single chapter the whole pdf is compiling? i guess. I there anything I can do to make it better? or is it supposed to happen.
Beta Was this translation helpful? Give feedback.
All reactions