VS Code - Latex Workshop - custom recipes file location
I want to use the vs code extension Latex Workshop and want to set up my own recipe for compiling the documents.
The faq are good but missing the part where they tell where the recipes are stored and where to put your custom recipe.
Could someone help me out on that?
compiling editors
edited Mar 11 at 10:09
samcarter
92.2k7105298
asked Mar 11 at 10:02
FuzzyTemperFuzzyTemper
83
add a comment |
I want to use the vs code extension Latex Workshop and want to set up my own recipe for compiling the documents.
The faq are good but missing the part where they tell where the recipes are stored and where to put your custom recipe.
Could someone help me out on that?
compiling editors
edited Mar 11 at 10:09
samcarter
92.2k7105298
asked Mar 11 at 10:02
FuzzyTemperFuzzyTemper
83
add a comment |
I want to use the vs code extension Latex Workshop and want to set up my own recipe for compiling the documents.
The faq are good but missing the part where they tell where the recipes are stored and where to put your custom recipe.
Could someone help me out on that?
compiling editors
edited Mar 11 at 10:09
samcarter
92.2k7105298
asked Mar 11 at 10:02
FuzzyTemperFuzzyTemper
83
I want to use the vs code extension Latex Workshop and want to set up my own recipe for compiling the documents.
The faq are good but missing the part where they tell where the recipes are stored and where to put your custom recipe.
Could someone help me out on that?
compiling editors
compiling editors
edited Mar 11 at 10:09
samcarter
92.2k7105298
asked Mar 11 at 10:02
FuzzyTemperFuzzyTemper
83
edited Mar 11 at 10:09
samcarter
92.2k7105298
asked Mar 11 at 10:02
FuzzyTemperFuzzyTemper
83
edited Mar 11 at 10:09
samcarter
92.2k7105298
edited Mar 11 at 10:09
samcarter
92.2k7105298
edited Mar 11 at 10:09
samcarter
92.2k7105298
92.2k7105298
asked Mar 11 at 10:02
FuzzyTemperFuzzyTemper
83
asked Mar 11 at 10:02
FuzzyTemperFuzzyTemper
83
asked Mar 11 at 10:02
FuzzyTemperFuzzyTemper
83
83
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Assume that you have to make a recipe that uses pdflatex once only, not pdflatex > biblatex > pdflatex > pdflatex.
In settings.json:
Add this to
"latex-workshop.latex.recipes":
{
"name": "pdflatex",
"tools": [
"pdflatex"
]
}
Add this to
"latex-workshop.latex.tools"if it is not present:
{
"name": "pdflatex",
"command": "pdflatex",
"args": [
"--shell-escape", // if you want to have the shell-escape flag
"-synctex=1",
"-interaction=nonstopmode",
"-file-line-error",
"%DOC%"
]
}
answered Mar 11 at 10:15
JouleVJouleV
6,68521951
Thanks @JouleV that solved my problem. Still I have no idea about the recipe but, I could remove latexmk from the tool chain, can compile my pdf now. In addition I learned something new about how to use VS code. Double thx :)
– FuzzyTemper
Mar 11 at 13:36
Actually I am wondering why someone wanted to use pdflatex > biblatex > pdflatex > pdflatex. What would be the benefit?
– FuzzyTemper
Mar 11 at 13:43
@FuzzyTemper Well, you should not removelatexmk. As for the second recipe: look at the amazing use of BibLaTeX.
– JouleV
Mar 11 at 14:03
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%2f478865%2fvs-code-latex-workshop-custom-recipes-file-location%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Assume that you have to make a recipe that uses pdflatex once only, not pdflatex > biblatex > pdflatex > pdflatex.
In settings.json:
Add this to
"latex-workshop.latex.recipes":
{
"name": "pdflatex",
"tools": [
"pdflatex"
]
}
Add this to
"latex-workshop.latex.tools"if it is not present:
{
"name": "pdflatex",
"command": "pdflatex",
"args": [
"--shell-escape", // if you want to have the shell-escape flag
"-synctex=1",
"-interaction=nonstopmode",
"-file-line-error",
"%DOC%"
]
}
answered Mar 11 at 10:15
JouleVJouleV
6,68521951
Thanks @JouleV that solved my problem. Still I have no idea about the recipe but, I could remove latexmk from the tool chain, can compile my pdf now. In addition I learned something new about how to use VS code. Double thx :)
– FuzzyTemper
Mar 11 at 13:36
Actually I am wondering why someone wanted to use pdflatex > biblatex > pdflatex > pdflatex. What would be the benefit?
– FuzzyTemper
Mar 11 at 13:43
@FuzzyTemper Well, you should not removelatexmk. As for the second recipe: look at the amazing use of BibLaTeX.
– JouleV
Mar 11 at 14:03
add a comment |
Assume that you have to make a recipe that uses pdflatex once only, not pdflatex > biblatex > pdflatex > pdflatex.
In settings.json:
Add this to
"latex-workshop.latex.recipes":
{
"name": "pdflatex",
"tools": [
"pdflatex"
]
}
Add this to
"latex-workshop.latex.tools"if it is not present:
{
"name": "pdflatex",
"command": "pdflatex",
"args": [
"--shell-escape", // if you want to have the shell-escape flag
"-synctex=1",
"-interaction=nonstopmode",
"-file-line-error",
"%DOC%"
]
}
answered Mar 11 at 10:15
JouleVJouleV
6,68521951
Thanks @JouleV that solved my problem. Still I have no idea about the recipe but, I could remove latexmk from the tool chain, can compile my pdf now. In addition I learned something new about how to use VS code. Double thx :)
– FuzzyTemper
Mar 11 at 13:36
Actually I am wondering why someone wanted to use pdflatex > biblatex > pdflatex > pdflatex. What would be the benefit?
– FuzzyTemper
Mar 11 at 13:43
@FuzzyTemper Well, you should not removelatexmk. As for the second recipe: look at the amazing use of BibLaTeX.
– JouleV
Mar 11 at 14:03
add a comment |
Assume that you have to make a recipe that uses pdflatex once only, not pdflatex > biblatex > pdflatex > pdflatex.
In settings.json:
Add this to
"latex-workshop.latex.recipes":
{
"name": "pdflatex",
"tools": [
"pdflatex"
]
}
Add this to
"latex-workshop.latex.tools"if it is not present:
{
"name": "pdflatex",
"command": "pdflatex",
"args": [
"--shell-escape", // if you want to have the shell-escape flag
"-synctex=1",
"-interaction=nonstopmode",
"-file-line-error",
"%DOC%"
]
}
answered Mar 11 at 10:15
JouleVJouleV
6,68521951
Assume that you have to make a recipe that uses pdflatex once only, not pdflatex > biblatex > pdflatex > pdflatex.
In settings.json:
Add this to
"latex-workshop.latex.recipes":
{
"name": "pdflatex",
"tools": [
"pdflatex"
]
}
Add this to
"latex-workshop.latex.tools"if it is not present:
{
"name": "pdflatex",
"command": "pdflatex",
"args": [
"--shell-escape", // if you want to have the shell-escape flag
"-synctex=1",
"-interaction=nonstopmode",
"-file-line-error",
"%DOC%"
]
}
answered Mar 11 at 10:15
JouleVJouleV
6,68521951
answered Mar 11 at 10:15
JouleVJouleV
6,68521951
answered Mar 11 at 10:15
JouleVJouleV
6,68521951
answered Mar 11 at 10:15
JouleVJouleV
6,68521951
6,68521951
Thanks @JouleV that solved my problem. Still I have no idea about the recipe but, I could remove latexmk from the tool chain, can compile my pdf now. In addition I learned something new about how to use VS code. Double thx :)
– FuzzyTemper
Mar 11 at 13:36
Actually I am wondering why someone wanted to use pdflatex > biblatex > pdflatex > pdflatex. What would be the benefit?
– FuzzyTemper
Mar 11 at 13:43
@FuzzyTemper Well, you should not removelatexmk. As for the second recipe: look at the amazing use of BibLaTeX.
– JouleV
Mar 11 at 14:03
add a comment |
Thanks @JouleV that solved my problem. Still I have no idea about the recipe but, I could remove latexmk from the tool chain, can compile my pdf now. In addition I learned something new about how to use VS code. Double thx :)
– FuzzyTemper
Mar 11 at 13:36
Actually I am wondering why someone wanted to use pdflatex > biblatex > pdflatex > pdflatex. What would be the benefit?
– FuzzyTemper
Mar 11 at 13:43
@FuzzyTemper Well, you should not removelatexmk. As for the second recipe: look at the amazing use of BibLaTeX.
– JouleV
Mar 11 at 14:03
Thanks @JouleV that solved my problem. Still I have no idea about the recipe but, I could remove latexmk from the tool chain, can compile my pdf now. In addition I learned something new about how to use VS code. Double thx :)
– FuzzyTemper
Mar 11 at 13:36
Thanks @JouleV that solved my problem. Still I have no idea about the recipe but, I could remove latexmk from the tool chain, can compile my pdf now. In addition I learned something new about how to use VS code. Double thx :)
– FuzzyTemper
Mar 11 at 13:36
Actually I am wondering why someone wanted to use pdflatex > biblatex > pdflatex > pdflatex. What would be the benefit?
– FuzzyTemper
Mar 11 at 13:43
Actually I am wondering why someone wanted to use pdflatex > biblatex > pdflatex > pdflatex. What would be the benefit?
– FuzzyTemper
Mar 11 at 13:43
@FuzzyTemper Well, you should not remove
latexmk. As for the second recipe: look at the amazing use of BibLaTeX.– JouleV
Mar 11 at 14:03
@FuzzyTemper Well, you should not remove
latexmk. As for the second recipe: look at the amazing use of BibLaTeX.– JouleV
Mar 11 at 14:03
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%2f478865%2fvs-code-latex-workshop-custom-recipes-file-location%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
