-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
latexmk portion of recipe terminates with error "perl not found" #2390
Comments
This is mostly because your |
I'm not sure what you mean by this. Could you clarify by chance? |
Check the following two commands in your terminal (not inside vscode's terminal)
Compare the output of the second command with |
The first command doesn't do anything significant since it's only waiting for Perl input. As for the second command, the PATH you gave directly matches with the output I get, except |
What is the output of |
|
Yet, You have to investigate why |
I wasn't able to find anything related to |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This is because the |
Do you mean something like |
Please show us:
Notice that you are using an unofficial build of VS Code, which we do not officially support. See microsoft/vscode#107997 (comment) |
Here's the portion of
Can you clarify where to find Lastly, does you mean LaTeX-Workshop doesn't support OSS? (My understanding was that OSS is essentially VSCode minus Microsoft branding, but if there is a bigger difference please let me know) |
This is the cause. It overrides the |
I use the Code-OSS build Arch Linux provides on both my machines without issue. The issue is that Arch Linux uses it's own native electron package rather than the one provided in the code repository which caused one issue. Then there was an issue with how open-vsx was packaging the extension (#2160). Both issues are resolved now and hopefully there are no further issues but we do not control the Arch Linux package/VSCodium/the open-vsx package so we would like to test the official extension on the official build to know if the issue is on our end or somewhere else. |
Hmm yeah, that seems to have been a symptom of the root problem, as when I took out the
Now I can see the problem clearly:
However PATH according to VSCode's internal terminal (and my standalone terminal) indicate otherwise:
According to the documentation entry on environment variables this means something's broken with my LaTeX setup. As I mentioned earlier, |
Please add the following to your setting instead of the previous one:
|
Well I'll be damned, that worked! Sorry for bugging you with so many small questions. |
Preliminary questions [Required]
Disable all the other extensions except for LaTeX Workshop, and check that you still see this issue. [Required]
You still see this issue?: Yes/No
Make sure to visit the wiki FAQ before filling an issue.
You visited the wiki?: Yes/No
If your issue is with compiling a document (not having to do with finding the root file of a project), check first that you can compile manually.
You can compile a TeX document manually?: Yes/No
Describe the bug [Required]
When I run the stock LaTeX build recipe,
latexmk
reports thatperl
cannot be found on my system. I've double checked that (a)perl -v
works properly and is installed on my system and (b)pdflatex
andlatexmk
work when directly called on my terminal. (i.e. TeX Live is properly installed on my system) My immediate thought was that my PATH was set wrong somewhere, but that seems very unlikely since all of the previous commands worked as expected. I'm out of ideas what could be going wrong -- does anyone know what's going wrong?I'm using TeX Live (installed directly from TeXGroup's website) on Arch Linux.
To Reproduce
Steps to reproduce the behavior:
.tex
fileappears.
Expected behavior
Either (a) the project should cleanly compile (since it does successfully compile when directly run) or (b) an error that isn't perl-related pops up and happens after the initial
latexmk
recipe.Logs [Required]
Please paste the whole log messages here, not parts of ones. The log should start with
Initializing LaTeX Workshop
. It is very important to identify problems.LaTeX Workshop Output [Required]
Developer Tools Console [Required]
Nothing particularly suspicious came up when Developer Tools was toggled.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop [Required]
Additional questions
Are you using VSCodium?
Yes/No
Are you using LaTeX Workshop with VS Code Remote?
Yes/No
If the answer is Yes, please write which one you are using. Write the versions of the remote extension.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: