Reporting LaTeX error at custom location
I'm familiar with PackageError as a way to cause LaTeX to report a custom error message when the command is run. But I'm wondering, is there a way to cause LaTeX to report an error, with a custom filename and location?
I run my .tex files through an external preprocessor, and when that preprocessor fails, I'd like to have my editor (vscode Latex-workshop) report the error inline. My thinking is that, if the preprocessor fails, I can have it generate a "dummy" file that calls PackageError reporting the location of the preprocessing error.
I also use latexmk, so if there's a way to do this using its tools, that would work too.
errors packages package-writing latexmk compilation-error
asked 5 hours ago
jmitejmite
6361618
add a comment |
I'm familiar with PackageError as a way to cause LaTeX to report a custom error message when the command is run. But I'm wondering, is there a way to cause LaTeX to report an error, with a custom filename and location?
I run my .tex files through an external preprocessor, and when that preprocessor fails, I'd like to have my editor (vscode Latex-workshop) report the error inline. My thinking is that, if the preprocessor fails, I can have it generate a "dummy" file that calls PackageError reporting the location of the preprocessing error.
I also use latexmk, so if there's a way to do this using its tools, that would work too.
errors packages package-writing latexmk compilation-error
asked 5 hours ago
jmitejmite
6361618
I think the answer to your question is "no". But it is a bit hard to understand so perhaps I misunderstood the question. If you want to generate an error that says it is made on line 100 of foo.tex you could generate a 100 line text file which is blank except for aPackageErroron line 100, but I don't think you mean that?
– David Carlisle
5 hours ago
@DavidCarlisle That's what I'm trying to avoid. I'll generate the 100-line file if I have to, but I'd rather a command that says "output the error as if I'd generated a 100 line file".
– jmite
5 hours ago
well it depends who or what the error is for, you can of course simplytypeoutexactly that message and then throw aerrmessageto cause an error, but you may need to fake tex's format more or less exactly if for example you want an existing editor error log parser to pick it up
– David Carlisle
1 hour ago
add a comment |
I'm familiar with PackageError as a way to cause LaTeX to report a custom error message when the command is run. But I'm wondering, is there a way to cause LaTeX to report an error, with a custom filename and location?
I run my .tex files through an external preprocessor, and when that preprocessor fails, I'd like to have my editor (vscode Latex-workshop) report the error inline. My thinking is that, if the preprocessor fails, I can have it generate a "dummy" file that calls PackageError reporting the location of the preprocessing error.
I also use latexmk, so if there's a way to do this using its tools, that would work too.
errors packages package-writing latexmk compilation-error
asked 5 hours ago
jmitejmite
6361618
I'm familiar with PackageError as a way to cause LaTeX to report a custom error message when the command is run. But I'm wondering, is there a way to cause LaTeX to report an error, with a custom filename and location?
I run my .tex files through an external preprocessor, and when that preprocessor fails, I'd like to have my editor (vscode Latex-workshop) report the error inline. My thinking is that, if the preprocessor fails, I can have it generate a "dummy" file that calls PackageError reporting the location of the preprocessing error.
I also use latexmk, so if there's a way to do this using its tools, that would work too.
errors packages package-writing latexmk compilation-error
errors packages package-writing latexmk compilation-error
asked 5 hours ago
jmitejmite
6361618
asked 5 hours ago
jmitejmite
6361618
asked 5 hours ago
jmitejmite
6361618
asked 5 hours ago
jmitejmite
6361618
asked 5 hours ago
jmitejmite
6361618
6361618
I think the answer to your question is "no". But it is a bit hard to understand so perhaps I misunderstood the question. If you want to generate an error that says it is made on line 100 of foo.tex you could generate a 100 line text file which is blank except for aPackageErroron line 100, but I don't think you mean that?
– David Carlisle
5 hours ago
@DavidCarlisle That's what I'm trying to avoid. I'll generate the 100-line file if I have to, but I'd rather a command that says "output the error as if I'd generated a 100 line file".
– jmite
5 hours ago
well it depends who or what the error is for, you can of course simplytypeoutexactly that message and then throw aerrmessageto cause an error, but you may need to fake tex's format more or less exactly if for example you want an existing editor error log parser to pick it up
– David Carlisle
1 hour ago
add a comment |
I think the answer to your question is "no". But it is a bit hard to understand so perhaps I misunderstood the question. If you want to generate an error that says it is made on line 100 of foo.tex you could generate a 100 line text file which is blank except for aPackageErroron line 100, but I don't think you mean that?
– David Carlisle
5 hours ago
@DavidCarlisle That's what I'm trying to avoid. I'll generate the 100-line file if I have to, but I'd rather a command that says "output the error as if I'd generated a 100 line file".
– jmite
5 hours ago
well it depends who or what the error is for, you can of course simplytypeoutexactly that message and then throw aerrmessageto cause an error, but you may need to fake tex's format more or less exactly if for example you want an existing editor error log parser to pick it up
– David Carlisle
1 hour ago
I think the answer to your question is "no". But it is a bit hard to understand so perhaps I misunderstood the question. If you want to generate an error that says it is made on line 100 of foo.tex you could generate a 100 line text file which is blank except for a
PackageError on line 100, but I don't think you mean that?– David Carlisle
5 hours ago
I think the answer to your question is "no". But it is a bit hard to understand so perhaps I misunderstood the question. If you want to generate an error that says it is made on line 100 of foo.tex you could generate a 100 line text file which is blank except for a
PackageError on line 100, but I don't think you mean that?– David Carlisle
5 hours ago
@DavidCarlisle That's what I'm trying to avoid. I'll generate the 100-line file if I have to, but I'd rather a command that says "output the error as if I'd generated a 100 line file".
– jmite
5 hours ago
@DavidCarlisle That's what I'm trying to avoid. I'll generate the 100-line file if I have to, but I'd rather a command that says "output the error as if I'd generated a 100 line file".
– jmite
5 hours ago
well it depends who or what the error is for, you can of course simply
typeout exactly that message and then throw a errmessage to cause an error, but you may need to fake tex's format more or less exactly if for example you want an existing editor error log parser to pick it up– David Carlisle
1 hour ago
well it depends who or what the error is for, you can of course simply
typeout exactly that message and then throw a errmessage to cause an error, but you may need to fake tex's format more or less exactly if for example you want an existing editor error log parser to pick it up– David Carlisle
1 hour ago
add a comment |
0
active
oldest
votes
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%2f481425%2freporting-latex-error-at-custom-location%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f481425%2freporting-latex-error-at-custom-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
I think the answer to your question is "no". But it is a bit hard to understand so perhaps I misunderstood the question. If you want to generate an error that says it is made on line 100 of foo.tex you could generate a 100 line text file which is blank except for a
PackageErroron line 100, but I don't think you mean that?– David Carlisle
5 hours ago
@DavidCarlisle That's what I'm trying to avoid. I'll generate the 100-line file if I have to, but I'd rather a command that says "output the error as if I'd generated a 100 line file".
– jmite
5 hours ago
well it depends who or what the error is for, you can of course simply
typeoutexactly that message and then throw aerrmessageto cause an error, but you may need to fake tex's format more or less exactly if for example you want an existing editor error log parser to pick it up– David Carlisle
1 hour ago