When I try to typeset pdflatex I get pdftex error on my output console
0
When I typeset my latex file with pdflatex, I get an output console with this error message:
This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015) (preloaded format=pdftex)
restricted write18 enabled.
entering extended mode. restricted write18 enabled. (./PaperOne-03-16-19.tex
! Undefined control sequence.
l.6 documentclass
[12pt,leqno]{article}
errors
edited Mar 15 at 1:19
David Carlisle
495k4111411889
asked Mar 14 at 18:10
Carl SimonCarl Simon
1
|
show 2 more comments
0
When I typeset my latex file with pdflatex, I get an output console with this error message:
This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015) (preloaded format=pdftex)
restricted write18 enabled.
entering extended mode. restricted write18 enabled. (./PaperOne-03-16-19.tex
! Undefined control sequence.
l.6 documentclass
[12pt,leqno]{article}
errors
edited Mar 15 at 1:19
David Carlisle
495k4111411889
asked Mar 14 at 18:10
Carl SimonCarl Simon
1
2
You need to use thepdflatex(which loads the LaTeX format) executable, notpdftex(which loads pĺain).
– Phelype Oleinik
Mar 14 at 18:14
1
Welcome to TeX.SE. Please tell us which front-end program -- TeXworks, TeXshop, TeXmaker, TeXstudio, etc -- you employ to edit and typeset your LaTeX documents.
– Mico
Mar 14 at 18:20
you give us little in the way of clues looks like your using an old 2015 TeX Live on a file in a subdirectory ? and that file has ? five lines of directives before the class definition ? which is possibly a maths article If your running direct from command line it would help to know if you have a main.tex that's including a number of subfiles and what is FIRST error as shown in main.log plus any FIRST error if there is a /PaperOne….log
– KJO
Mar 14 at 18:56
@supa-mega-ducky-momo-da-waffle you should use a code block not a quote for error messages, line endings are vital to understand tex errors.
– David Carlisle
Mar 14 at 22:29
1
@SupaMegaDuckyMomodaWaffle tex error messages are not understandable if you lose the line breaks, eg the one above it is only by the linebreak after the command that shows which command is undefined., the first line shows the line read so far the linebreak is the point of the error and the indented second line is the rest of the source not yet read. if you show it using the quote format all information is lost.
– David Carlisle
Mar 15 at 1:17
|
show 2 more comments
0
0
0
When I typeset my latex file with pdflatex, I get an output console with this error message:
This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015) (preloaded format=pdftex)
restricted write18 enabled.
entering extended mode. restricted write18 enabled. (./PaperOne-03-16-19.tex
! Undefined control sequence.
l.6 documentclass
[12pt,leqno]{article}
errors
edited Mar 15 at 1:19
David Carlisle
495k4111411889
asked Mar 14 at 18:10
Carl SimonCarl Simon
1
When I typeset my latex file with pdflatex, I get an output console with this error message:
This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015) (preloaded format=pdftex)
restricted write18 enabled.
entering extended mode. restricted write18 enabled. (./PaperOne-03-16-19.tex
! Undefined control sequence.
l.6 documentclass
[12pt,leqno]{article}
errors
errors
edited Mar 15 at 1:19
David Carlisle
495k4111411889
asked Mar 14 at 18:10
Carl SimonCarl Simon
1
edited Mar 15 at 1:19
David Carlisle
495k4111411889
asked Mar 14 at 18:10
Carl SimonCarl Simon
1
edited Mar 15 at 1:19
David Carlisle
495k4111411889
edited Mar 15 at 1:19
David Carlisle
495k4111411889
edited Mar 15 at 1:19
David Carlisle
495k4111411889
495k4111411889
asked Mar 14 at 18:10
Carl SimonCarl Simon
1
asked Mar 14 at 18:10
Carl SimonCarl Simon
1
asked Mar 14 at 18:10
Carl SimonCarl Simon
1
1
2
You need to use thepdflatex(which loads the LaTeX format) executable, notpdftex(which loads pĺain).
– Phelype Oleinik
Mar 14 at 18:14
1
Welcome to TeX.SE. Please tell us which front-end program -- TeXworks, TeXshop, TeXmaker, TeXstudio, etc -- you employ to edit and typeset your LaTeX documents.
– Mico
Mar 14 at 18:20
you give us little in the way of clues looks like your using an old 2015 TeX Live on a file in a subdirectory ? and that file has ? five lines of directives before the class definition ? which is possibly a maths article If your running direct from command line it would help to know if you have a main.tex that's including a number of subfiles and what is FIRST error as shown in main.log plus any FIRST error if there is a /PaperOne….log
– KJO
Mar 14 at 18:56
@supa-mega-ducky-momo-da-waffle you should use a code block not a quote for error messages, line endings are vital to understand tex errors.
– David Carlisle
Mar 14 at 22:29
1
@SupaMegaDuckyMomodaWaffle tex error messages are not understandable if you lose the line breaks, eg the one above it is only by the linebreak after the command that shows which command is undefined., the first line shows the line read so far the linebreak is the point of the error and the indented second line is the rest of the source not yet read. if you show it using the quote format all information is lost.
– David Carlisle
Mar 15 at 1:17
|
show 2 more comments
2
You need to use thepdflatex(which loads the LaTeX format) executable, notpdftex(which loads pĺain).
– Phelype Oleinik
Mar 14 at 18:14
1
Welcome to TeX.SE. Please tell us which front-end program -- TeXworks, TeXshop, TeXmaker, TeXstudio, etc -- you employ to edit and typeset your LaTeX documents.
– Mico
Mar 14 at 18:20
you give us little in the way of clues looks like your using an old 2015 TeX Live on a file in a subdirectory ? and that file has ? five lines of directives before the class definition ? which is possibly a maths article If your running direct from command line it would help to know if you have a main.tex that's including a number of subfiles and what is FIRST error as shown in main.log plus any FIRST error if there is a /PaperOne….log
– KJO
Mar 14 at 18:56
@supa-mega-ducky-momo-da-waffle you should use a code block not a quote for error messages, line endings are vital to understand tex errors.
– David Carlisle
Mar 14 at 22:29
1
@SupaMegaDuckyMomodaWaffle tex error messages are not understandable if you lose the line breaks, eg the one above it is only by the linebreak after the command that shows which command is undefined., the first line shows the line read so far the linebreak is the point of the error and the indented second line is the rest of the source not yet read. if you show it using the quote format all information is lost.
– David Carlisle
Mar 15 at 1:17
2
2
You need to use the
pdflatex (which loads the LaTeX format) executable, not pdftex (which loads pĺain).– Phelype Oleinik
Mar 14 at 18:14
You need to use the
pdflatex (which loads the LaTeX format) executable, not pdftex (which loads pĺain).– Phelype Oleinik
Mar 14 at 18:14
1
1
Welcome to TeX.SE. Please tell us which front-end program -- TeXworks, TeXshop, TeXmaker, TeXstudio, etc -- you employ to edit and typeset your LaTeX documents.
– Mico
Mar 14 at 18:20
Welcome to TeX.SE. Please tell us which front-end program -- TeXworks, TeXshop, TeXmaker, TeXstudio, etc -- you employ to edit and typeset your LaTeX documents.
– Mico
Mar 14 at 18:20
you give us little in the way of clues looks like your using an old 2015 TeX Live on a file in a subdirectory ? and that file has ? five lines of directives before the class definition ? which is possibly a maths article If your running direct from command line it would help to know if you have a main.tex that's including a number of subfiles and what is FIRST error as shown in main.log plus any FIRST error if there is a /PaperOne….log
– KJO
Mar 14 at 18:56
you give us little in the way of clues looks like your using an old 2015 TeX Live on a file in a subdirectory ? and that file has ? five lines of directives before the class definition ? which is possibly a maths article If your running direct from command line it would help to know if you have a main.tex that's including a number of subfiles and what is FIRST error as shown in main.log plus any FIRST error if there is a /PaperOne….log
– KJO
Mar 14 at 18:56
@supa-mega-ducky-momo-da-waffle you should use a code block not a quote for error messages, line endings are vital to understand tex errors.
– David Carlisle
Mar 14 at 22:29
@supa-mega-ducky-momo-da-waffle you should use a code block not a quote for error messages, line endings are vital to understand tex errors.
– David Carlisle
Mar 14 at 22:29
1
1
@SupaMegaDuckyMomodaWaffle tex error messages are not understandable if you lose the line breaks, eg the one above it is only by the linebreak after the command that shows which command is undefined., the first line shows the line read so far the linebreak is the point of the error and the indented second line is the rest of the source not yet read. if you show it using the quote format all information is lost.
– David Carlisle
Mar 15 at 1:17
@SupaMegaDuckyMomodaWaffle tex error messages are not understandable if you lose the line breaks, eg the one above it is only by the linebreak after the command that shows which command is undefined., the first line shows the line read so far the linebreak is the point of the error and the indented second line is the rest of the source not yet read. if you show it using the quote format all information is lost.
– David Carlisle
Mar 15 at 1:17
|
show 2 more comments
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
});
}
});
draft saved
draft discarded
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%2f479530%2fwhen-i-try-to-typeset-pdflatex-i-get-pdftex-error-on-my-output-console%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
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f479530%2fwhen-i-try-to-typeset-pdflatex-i-get-pdftex-error-on-my-output-console%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
2
You need to use the
pdflatex(which loads the LaTeX format) executable, notpdftex(which loads pĺain).– Phelype Oleinik
Mar 14 at 18:14
1
Welcome to TeX.SE. Please tell us which front-end program -- TeXworks, TeXshop, TeXmaker, TeXstudio, etc -- you employ to edit and typeset your LaTeX documents.
– Mico
Mar 14 at 18:20
you give us little in the way of clues looks like your using an old 2015 TeX Live on a file in a subdirectory ? and that file has ? five lines of directives before the class definition ? which is possibly a maths article If your running direct from command line it would help to know if you have a main.tex that's including a number of subfiles and what is FIRST error as shown in main.log plus any FIRST error if there is a /PaperOne….log
– KJO
Mar 14 at 18:56
@supa-mega-ducky-momo-da-waffle you should use a code block not a quote for error messages, line endings are vital to understand tex errors.
– David Carlisle
Mar 14 at 22:29
1
@SupaMegaDuckyMomodaWaffle tex error messages are not understandable if you lose the line breaks, eg the one above it is only by the linebreak after the command that shows which command is undefined., the first line shows the line read so far the linebreak is the point of the error and the indented second line is the rest of the source not yet read. if you show it using the quote format all information is lost.
– David Carlisle
Mar 15 at 1:17