LuaLaTeX not recognised as a VS Code tool
I've been trying to adopt VS Code as my LaTeX editior of choice, since it has all of the features Atom has but more, once the extension LaTeX Workshop has been installed. My only gripe with it is that I can't seem to actually compile anything with LuaLaTeX as the compiler. What follows is for people who actually know something about how the settings are supposed to work in VSCode (because I sure don't).
I've added the following settings to the file settings.json
, which is opened in a tab inside VSCode when USER SETTINGS
are opened:
{
"latex-workshop.view.pdf.viewer": "browser",
"latex-workshop.latex.clean.onFailBuild.enabled": true,
"latex-workshop.latex.recipes": [
{
"name": "lualatex->biber->lualatex",
"tools": [
"lualatex",
"biber",
"lualatex"
]
},
{
"name": "latexmk",
"tools": [
"latexmk"
]
},
{
"name": "pdflatex -> bibtex -> pdflatex*2",
"tools": [
"pdflatex",
"bibtex",
"pdflatex",
"pdflatex"
]
}
]
}
The settings themselves seem to have been entered correctly, since I get the error Skipping undefined tool "lualatex" in recipe "lualatex->biber->lualatex", Source: LaTeX Workshop (Extension)
. This indcates that the editor is able to parse the settings, but is unable to find lualatex
.
The default setting of using latexmk
seems to work, but it uses pdflatex
by default. I'm running Ubuntu with a "normal" TeXLive installation, so LuaLaTeX should be available.
Has anyone ran into a similar issue and if so, how was it fixed?
EDIT:
LuaLaTeX is indeed available, since running lualatex --version
in the terminal nets:
This is LuaTeX, Version 1.07.0 (TeX Live 2018)
Execute 'luatex --credits' for credits and version details.
There is NO warranty. Redistribution of this software is covered by
the terms of the GNU General Public License, version 2 or (at your option)
any later version. For more information about these matters, see the file
named COPYING and the LuaTeX source.
LuaTeX is Copyright 2018 Taco Hoekwater and the LuaTeX Team.
luatex compiling editors linux
add a comment |
I've been trying to adopt VS Code as my LaTeX editior of choice, since it has all of the features Atom has but more, once the extension LaTeX Workshop has been installed. My only gripe with it is that I can't seem to actually compile anything with LuaLaTeX as the compiler. What follows is for people who actually know something about how the settings are supposed to work in VSCode (because I sure don't).
I've added the following settings to the file settings.json
, which is opened in a tab inside VSCode when USER SETTINGS
are opened:
{
"latex-workshop.view.pdf.viewer": "browser",
"latex-workshop.latex.clean.onFailBuild.enabled": true,
"latex-workshop.latex.recipes": [
{
"name": "lualatex->biber->lualatex",
"tools": [
"lualatex",
"biber",
"lualatex"
]
},
{
"name": "latexmk",
"tools": [
"latexmk"
]
},
{
"name": "pdflatex -> bibtex -> pdflatex*2",
"tools": [
"pdflatex",
"bibtex",
"pdflatex",
"pdflatex"
]
}
]
}
The settings themselves seem to have been entered correctly, since I get the error Skipping undefined tool "lualatex" in recipe "lualatex->biber->lualatex", Source: LaTeX Workshop (Extension)
. This indcates that the editor is able to parse the settings, but is unable to find lualatex
.
The default setting of using latexmk
seems to work, but it uses pdflatex
by default. I'm running Ubuntu with a "normal" TeXLive installation, so LuaLaTeX should be available.
Has anyone ran into a similar issue and if so, how was it fixed?
EDIT:
LuaLaTeX is indeed available, since running lualatex --version
in the terminal nets:
This is LuaTeX, Version 1.07.0 (TeX Live 2018)
Execute 'luatex --credits' for credits and version details.
There is NO warranty. Redistribution of this software is covered by
the terms of the GNU General Public License, version 2 or (at your option)
any later version. For more information about these matters, see the file
named COPYING and the LuaTeX source.
LuaTeX is Copyright 2018 Taco Hoekwater and the LuaTeX Team.
luatex compiling editors linux
1
Did you check if lualatex is really available? What happens in a terminal afterlualatex --version
?
– Ulrike Fischer
Oct 18 '18 at 8:57
LuaLaTeX is installed: This is LuaTeX, Version 1.07.0 (TeX Live 2018) Execute 'luatex --credits' for credits and version details. There is NO warranty. Redistribution of this software is covered by the terms of the GNU General Public License, version 2 or (at your option) any later version. For more information about these matters, see the file named COPYING and the LuaTeX source. LuaTeX is Copyright 2018 Taco Hoekwater and the LuaTeX Team.
– TheSodesa
Oct 18 '18 at 9:01
1
Then I would guess that "lualatex" is not a call to an application but a reference to some other section in the setting and that you need to setup it there. Is there somewhere in the settings something that setups the names "pdflatex" or "bibtex"?
– Ulrike Fischer
Oct 18 '18 at 9:04
Ah, there is alatex-workshop.latex.tools
key, where the available tools are defined. I'll try editing that.
– TheSodesa
Oct 18 '18 at 9:11
add a comment |
I've been trying to adopt VS Code as my LaTeX editior of choice, since it has all of the features Atom has but more, once the extension LaTeX Workshop has been installed. My only gripe with it is that I can't seem to actually compile anything with LuaLaTeX as the compiler. What follows is for people who actually know something about how the settings are supposed to work in VSCode (because I sure don't).
I've added the following settings to the file settings.json
, which is opened in a tab inside VSCode when USER SETTINGS
are opened:
{
"latex-workshop.view.pdf.viewer": "browser",
"latex-workshop.latex.clean.onFailBuild.enabled": true,
"latex-workshop.latex.recipes": [
{
"name": "lualatex->biber->lualatex",
"tools": [
"lualatex",
"biber",
"lualatex"
]
},
{
"name": "latexmk",
"tools": [
"latexmk"
]
},
{
"name": "pdflatex -> bibtex -> pdflatex*2",
"tools": [
"pdflatex",
"bibtex",
"pdflatex",
"pdflatex"
]
}
]
}
The settings themselves seem to have been entered correctly, since I get the error Skipping undefined tool "lualatex" in recipe "lualatex->biber->lualatex", Source: LaTeX Workshop (Extension)
. This indcates that the editor is able to parse the settings, but is unable to find lualatex
.
The default setting of using latexmk
seems to work, but it uses pdflatex
by default. I'm running Ubuntu with a "normal" TeXLive installation, so LuaLaTeX should be available.
Has anyone ran into a similar issue and if so, how was it fixed?
EDIT:
LuaLaTeX is indeed available, since running lualatex --version
in the terminal nets:
This is LuaTeX, Version 1.07.0 (TeX Live 2018)
Execute 'luatex --credits' for credits and version details.
There is NO warranty. Redistribution of this software is covered by
the terms of the GNU General Public License, version 2 or (at your option)
any later version. For more information about these matters, see the file
named COPYING and the LuaTeX source.
LuaTeX is Copyright 2018 Taco Hoekwater and the LuaTeX Team.
luatex compiling editors linux
I've been trying to adopt VS Code as my LaTeX editior of choice, since it has all of the features Atom has but more, once the extension LaTeX Workshop has been installed. My only gripe with it is that I can't seem to actually compile anything with LuaLaTeX as the compiler. What follows is for people who actually know something about how the settings are supposed to work in VSCode (because I sure don't).
I've added the following settings to the file settings.json
, which is opened in a tab inside VSCode when USER SETTINGS
are opened:
{
"latex-workshop.view.pdf.viewer": "browser",
"latex-workshop.latex.clean.onFailBuild.enabled": true,
"latex-workshop.latex.recipes": [
{
"name": "lualatex->biber->lualatex",
"tools": [
"lualatex",
"biber",
"lualatex"
]
},
{
"name": "latexmk",
"tools": [
"latexmk"
]
},
{
"name": "pdflatex -> bibtex -> pdflatex*2",
"tools": [
"pdflatex",
"bibtex",
"pdflatex",
"pdflatex"
]
}
]
}
The settings themselves seem to have been entered correctly, since I get the error Skipping undefined tool "lualatex" in recipe "lualatex->biber->lualatex", Source: LaTeX Workshop (Extension)
. This indcates that the editor is able to parse the settings, but is unable to find lualatex
.
The default setting of using latexmk
seems to work, but it uses pdflatex
by default. I'm running Ubuntu with a "normal" TeXLive installation, so LuaLaTeX should be available.
Has anyone ran into a similar issue and if so, how was it fixed?
EDIT:
LuaLaTeX is indeed available, since running lualatex --version
in the terminal nets:
This is LuaTeX, Version 1.07.0 (TeX Live 2018)
Execute 'luatex --credits' for credits and version details.
There is NO warranty. Redistribution of this software is covered by
the terms of the GNU General Public License, version 2 or (at your option)
any later version. For more information about these matters, see the file
named COPYING and the LuaTeX source.
LuaTeX is Copyright 2018 Taco Hoekwater and the LuaTeX Team.
luatex compiling editors linux
luatex compiling editors linux
edited Oct 18 '18 at 9:02
TheSodesa
asked Oct 18 '18 at 8:37
TheSodesaTheSodesa
1339
1339
1
Did you check if lualatex is really available? What happens in a terminal afterlualatex --version
?
– Ulrike Fischer
Oct 18 '18 at 8:57
LuaLaTeX is installed: This is LuaTeX, Version 1.07.0 (TeX Live 2018) Execute 'luatex --credits' for credits and version details. There is NO warranty. Redistribution of this software is covered by the terms of the GNU General Public License, version 2 or (at your option) any later version. For more information about these matters, see the file named COPYING and the LuaTeX source. LuaTeX is Copyright 2018 Taco Hoekwater and the LuaTeX Team.
– TheSodesa
Oct 18 '18 at 9:01
1
Then I would guess that "lualatex" is not a call to an application but a reference to some other section in the setting and that you need to setup it there. Is there somewhere in the settings something that setups the names "pdflatex" or "bibtex"?
– Ulrike Fischer
Oct 18 '18 at 9:04
Ah, there is alatex-workshop.latex.tools
key, where the available tools are defined. I'll try editing that.
– TheSodesa
Oct 18 '18 at 9:11
add a comment |
1
Did you check if lualatex is really available? What happens in a terminal afterlualatex --version
?
– Ulrike Fischer
Oct 18 '18 at 8:57
LuaLaTeX is installed: This is LuaTeX, Version 1.07.0 (TeX Live 2018) Execute 'luatex --credits' for credits and version details. There is NO warranty. Redistribution of this software is covered by the terms of the GNU General Public License, version 2 or (at your option) any later version. For more information about these matters, see the file named COPYING and the LuaTeX source. LuaTeX is Copyright 2018 Taco Hoekwater and the LuaTeX Team.
– TheSodesa
Oct 18 '18 at 9:01
1
Then I would guess that "lualatex" is not a call to an application but a reference to some other section in the setting and that you need to setup it there. Is there somewhere in the settings something that setups the names "pdflatex" or "bibtex"?
– Ulrike Fischer
Oct 18 '18 at 9:04
Ah, there is alatex-workshop.latex.tools
key, where the available tools are defined. I'll try editing that.
– TheSodesa
Oct 18 '18 at 9:11
1
1
Did you check if lualatex is really available? What happens in a terminal after
lualatex --version
?– Ulrike Fischer
Oct 18 '18 at 8:57
Did you check if lualatex is really available? What happens in a terminal after
lualatex --version
?– Ulrike Fischer
Oct 18 '18 at 8:57
LuaLaTeX is installed: This is LuaTeX, Version 1.07.0 (TeX Live 2018) Execute 'luatex --credits' for credits and version details. There is NO warranty. Redistribution of this software is covered by the terms of the GNU General Public License, version 2 or (at your option) any later version. For more information about these matters, see the file named COPYING and the LuaTeX source. LuaTeX is Copyright 2018 Taco Hoekwater and the LuaTeX Team.
– TheSodesa
Oct 18 '18 at 9:01
LuaLaTeX is installed: This is LuaTeX, Version 1.07.0 (TeX Live 2018) Execute 'luatex --credits' for credits and version details. There is NO warranty. Redistribution of this software is covered by the terms of the GNU General Public License, version 2 or (at your option) any later version. For more information about these matters, see the file named COPYING and the LuaTeX source. LuaTeX is Copyright 2018 Taco Hoekwater and the LuaTeX Team.
– TheSodesa
Oct 18 '18 at 9:01
1
1
Then I would guess that "lualatex" is not a call to an application but a reference to some other section in the setting and that you need to setup it there. Is there somewhere in the settings something that setups the names "pdflatex" or "bibtex"?
– Ulrike Fischer
Oct 18 '18 at 9:04
Then I would guess that "lualatex" is not a call to an application but a reference to some other section in the setting and that you need to setup it there. Is there somewhere in the settings something that setups the names "pdflatex" or "bibtex"?
– Ulrike Fischer
Oct 18 '18 at 9:04
Ah, there is a
latex-workshop.latex.tools
key, where the available tools are defined. I'll try editing that.– TheSodesa
Oct 18 '18 at 9:11
Ah, there is a
latex-workshop.latex.tools
key, where the available tools are defined. I'll try editing that.– TheSodesa
Oct 18 '18 at 9:11
add a comment |
2 Answers
2
active
oldest
votes
Alright, so the issue was that I hadn't defined the tools lualatex
and biber
in the VS Code user settings file settings.json
.
The following entries should be present in said file for things to work:
"latex-workshop.latex.recipes": [
{
"name": "lualatex->biber->lualatex",
"tools": [
"lualatex",
"biber",
"lualatex"
]
}
],
"latex-workshop.latex.tools": [
{
"name": "lualatex",
"command": "lualatex",
"args": [
"-synctex=1",
"-interaction=nonstopmode",
"-file-line-error",
"-pdf",
"%DOC%"
]
},
{
"name": "biber",
"command": "biber",
"args": [
"%DOCFILE%"
]
}
]
add a comment |
I think you should change it to
"name": "lualatex->biber->lualatex x2",
"tools": [
"lualatex",
"biber",
"lualatex",
"lualatex"
]
I can't really comprehend why but I've seen a couple of posts mentioning that something that is along the lines of keyword may be mixed due to biber compiling (?) the document. Just make it similar to "pdfLatex x2", I suppose.
New contributor
1
The problem the OP is/was facing is that LaTeX Workshop doesn't have a tool namedlualatex
yet (this is resolved in the accepted answer where we tell LaTeX Workshop whatlualatex
is inlatex-workshop.latex.tools
). Placing the code above tosettings.json
won't solve the problem.
– JouleV
2 hours ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f455648%2flualatex-not-recognised-as-a-vs-code-tool%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Alright, so the issue was that I hadn't defined the tools lualatex
and biber
in the VS Code user settings file settings.json
.
The following entries should be present in said file for things to work:
"latex-workshop.latex.recipes": [
{
"name": "lualatex->biber->lualatex",
"tools": [
"lualatex",
"biber",
"lualatex"
]
}
],
"latex-workshop.latex.tools": [
{
"name": "lualatex",
"command": "lualatex",
"args": [
"-synctex=1",
"-interaction=nonstopmode",
"-file-line-error",
"-pdf",
"%DOC%"
]
},
{
"name": "biber",
"command": "biber",
"args": [
"%DOCFILE%"
]
}
]
add a comment |
Alright, so the issue was that I hadn't defined the tools lualatex
and biber
in the VS Code user settings file settings.json
.
The following entries should be present in said file for things to work:
"latex-workshop.latex.recipes": [
{
"name": "lualatex->biber->lualatex",
"tools": [
"lualatex",
"biber",
"lualatex"
]
}
],
"latex-workshop.latex.tools": [
{
"name": "lualatex",
"command": "lualatex",
"args": [
"-synctex=1",
"-interaction=nonstopmode",
"-file-line-error",
"-pdf",
"%DOC%"
]
},
{
"name": "biber",
"command": "biber",
"args": [
"%DOCFILE%"
]
}
]
add a comment |
Alright, so the issue was that I hadn't defined the tools lualatex
and biber
in the VS Code user settings file settings.json
.
The following entries should be present in said file for things to work:
"latex-workshop.latex.recipes": [
{
"name": "lualatex->biber->lualatex",
"tools": [
"lualatex",
"biber",
"lualatex"
]
}
],
"latex-workshop.latex.tools": [
{
"name": "lualatex",
"command": "lualatex",
"args": [
"-synctex=1",
"-interaction=nonstopmode",
"-file-line-error",
"-pdf",
"%DOC%"
]
},
{
"name": "biber",
"command": "biber",
"args": [
"%DOCFILE%"
]
}
]
Alright, so the issue was that I hadn't defined the tools lualatex
and biber
in the VS Code user settings file settings.json
.
The following entries should be present in said file for things to work:
"latex-workshop.latex.recipes": [
{
"name": "lualatex->biber->lualatex",
"tools": [
"lualatex",
"biber",
"lualatex"
]
}
],
"latex-workshop.latex.tools": [
{
"name": "lualatex",
"command": "lualatex",
"args": [
"-synctex=1",
"-interaction=nonstopmode",
"-file-line-error",
"-pdf",
"%DOC%"
]
},
{
"name": "biber",
"command": "biber",
"args": [
"%DOCFILE%"
]
}
]
answered Oct 18 '18 at 9:19
TheSodesaTheSodesa
1339
1339
add a comment |
add a comment |
I think you should change it to
"name": "lualatex->biber->lualatex x2",
"tools": [
"lualatex",
"biber",
"lualatex",
"lualatex"
]
I can't really comprehend why but I've seen a couple of posts mentioning that something that is along the lines of keyword may be mixed due to biber compiling (?) the document. Just make it similar to "pdfLatex x2", I suppose.
New contributor
1
The problem the OP is/was facing is that LaTeX Workshop doesn't have a tool namedlualatex
yet (this is resolved in the accepted answer where we tell LaTeX Workshop whatlualatex
is inlatex-workshop.latex.tools
). Placing the code above tosettings.json
won't solve the problem.
– JouleV
2 hours ago
add a comment |
I think you should change it to
"name": "lualatex->biber->lualatex x2",
"tools": [
"lualatex",
"biber",
"lualatex",
"lualatex"
]
I can't really comprehend why but I've seen a couple of posts mentioning that something that is along the lines of keyword may be mixed due to biber compiling (?) the document. Just make it similar to "pdfLatex x2", I suppose.
New contributor
1
The problem the OP is/was facing is that LaTeX Workshop doesn't have a tool namedlualatex
yet (this is resolved in the accepted answer where we tell LaTeX Workshop whatlualatex
is inlatex-workshop.latex.tools
). Placing the code above tosettings.json
won't solve the problem.
– JouleV
2 hours ago
add a comment |
I think you should change it to
"name": "lualatex->biber->lualatex x2",
"tools": [
"lualatex",
"biber",
"lualatex",
"lualatex"
]
I can't really comprehend why but I've seen a couple of posts mentioning that something that is along the lines of keyword may be mixed due to biber compiling (?) the document. Just make it similar to "pdfLatex x2", I suppose.
New contributor
I think you should change it to
"name": "lualatex->biber->lualatex x2",
"tools": [
"lualatex",
"biber",
"lualatex",
"lualatex"
]
I can't really comprehend why but I've seen a couple of posts mentioning that something that is along the lines of keyword may be mixed due to biber compiling (?) the document. Just make it similar to "pdfLatex x2", I suppose.
New contributor
New contributor
answered 3 hours ago
CendermeCenderme
1
1
New contributor
New contributor
1
The problem the OP is/was facing is that LaTeX Workshop doesn't have a tool namedlualatex
yet (this is resolved in the accepted answer where we tell LaTeX Workshop whatlualatex
is inlatex-workshop.latex.tools
). Placing the code above tosettings.json
won't solve the problem.
– JouleV
2 hours ago
add a comment |
1
The problem the OP is/was facing is that LaTeX Workshop doesn't have a tool namedlualatex
yet (this is resolved in the accepted answer where we tell LaTeX Workshop whatlualatex
is inlatex-workshop.latex.tools
). Placing the code above tosettings.json
won't solve the problem.
– JouleV
2 hours ago
1
1
The problem the OP is/was facing is that LaTeX Workshop doesn't have a tool named
lualatex
yet (this is resolved in the accepted answer where we tell LaTeX Workshop what lualatex
is in latex-workshop.latex.tools
). Placing the code above to settings.json
won't solve the problem.– JouleV
2 hours ago
The problem the OP is/was facing is that LaTeX Workshop doesn't have a tool named
lualatex
yet (this is resolved in the accepted answer where we tell LaTeX Workshop what lualatex
is in latex-workshop.latex.tools
). Placing the code above to settings.json
won't solve the problem.– JouleV
2 hours ago
add a comment |
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f455648%2flualatex-not-recognised-as-a-vs-code-tool%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Did you check if lualatex is really available? What happens in a terminal after
lualatex --version
?– Ulrike Fischer
Oct 18 '18 at 8:57
LuaLaTeX is installed: This is LuaTeX, Version 1.07.0 (TeX Live 2018) Execute 'luatex --credits' for credits and version details. There is NO warranty. Redistribution of this software is covered by the terms of the GNU General Public License, version 2 or (at your option) any later version. For more information about these matters, see the file named COPYING and the LuaTeX source. LuaTeX is Copyright 2018 Taco Hoekwater and the LuaTeX Team.
– TheSodesa
Oct 18 '18 at 9:01
1
Then I would guess that "lualatex" is not a call to an application but a reference to some other section in the setting and that you need to setup it there. Is there somewhere in the settings something that setups the names "pdflatex" or "bibtex"?
– Ulrike Fischer
Oct 18 '18 at 9:04
Ah, there is a
latex-workshop.latex.tools
key, where the available tools are defined. I'll try editing that.– TheSodesa
Oct 18 '18 at 9:11