Strange “no line here to end” error
Unfortunately I didn't find any helpful question that already exists, so I need to open a new one on my problem.
I have two main documents I use. One is the main.tex with the entire thesis, and one is the SingleChapter.tex where I use single chapters for faster PDF creation. The files look pretty similar with both of them having some (working) header and settings part, and lots of included chapter.tex files.
When using the SingleChapter file everything works fine, but when using the main.tex I get the "no line here to end" error on
chapter{Chaptername}
include{./Chapter/Chaptername.tex}
Also, with commenting these two lines out the same error occurs in the same lines.
I don't get it.
Can you please help me?
Thanks a lot! :)
errors
edited Mar 25 at 12:06
JouleV
10.5k22559
asked Mar 25 at 12:05
user184234user184234
1
|
show 3 more comments
Unfortunately I didn't find any helpful question that already exists, so I need to open a new one on my problem.
I have two main documents I use. One is the main.tex with the entire thesis, and one is the SingleChapter.tex where I use single chapters for faster PDF creation. The files look pretty similar with both of them having some (working) header and settings part, and lots of included chapter.tex files.
When using the SingleChapter file everything works fine, but when using the main.tex I get the "no line here to end" error on
chapter{Chaptername}
include{./Chapter/Chaptername.tex}
Also, with commenting these two lines out the same error occurs in the same lines.
I don't get it.
Can you please help me?
Thanks a lot! :)
errors
edited Mar 25 at 12:06
JouleV
10.5k22559
asked Mar 25 at 12:05
user184234user184234
1
1
Put the chapter command inside the include file, or don't use include but input.
– Ulrike Fischer
Mar 25 at 12:07
2
it will not generate the error that you state but almost always thechapterheading should be inside the included file otherwise you get a forced page break after the heading. The error is telling you of a bad use of\but unless you show your code it is not possible to say what you have done wrong.
– David Carlisle
Mar 25 at 12:08
1
also never use the explicit.texextension withincludejust useinclude{./Chapter/Chaptername}
– David Carlisle
Mar 25 at 12:09
Hi Guys,Thanks for the quick response. I will check that, and swap the include by inputs and throw away the .tex's and report if the error still occurs.
– user184234
Mar 25 at 13:29
It's really better to put thechapterline in the included file; leave it in the main file but comment it out -- that will allow you to take advantage ofincludeonly. That said, the error is probably being reported for the line just previous to thechapterline -- and that means it's quite possibly in another file.
– barbara beeton
Mar 25 at 13:57
|
show 3 more comments
Unfortunately I didn't find any helpful question that already exists, so I need to open a new one on my problem.
I have two main documents I use. One is the main.tex with the entire thesis, and one is the SingleChapter.tex where I use single chapters for faster PDF creation. The files look pretty similar with both of them having some (working) header and settings part, and lots of included chapter.tex files.
When using the SingleChapter file everything works fine, but when using the main.tex I get the "no line here to end" error on
chapter{Chaptername}
include{./Chapter/Chaptername.tex}
Also, with commenting these two lines out the same error occurs in the same lines.
I don't get it.
Can you please help me?
Thanks a lot! :)
errors
edited Mar 25 at 12:06
JouleV
10.5k22559
asked Mar 25 at 12:05
user184234user184234
1
Unfortunately I didn't find any helpful question that already exists, so I need to open a new one on my problem.
I have two main documents I use. One is the main.tex with the entire thesis, and one is the SingleChapter.tex where I use single chapters for faster PDF creation. The files look pretty similar with both of them having some (working) header and settings part, and lots of included chapter.tex files.
When using the SingleChapter file everything works fine, but when using the main.tex I get the "no line here to end" error on
chapter{Chaptername}
include{./Chapter/Chaptername.tex}
Also, with commenting these two lines out the same error occurs in the same lines.
I don't get it.
Can you please help me?
Thanks a lot! :)
errors
errors
edited Mar 25 at 12:06
JouleV
10.5k22559
asked Mar 25 at 12:05
user184234user184234
1
edited Mar 25 at 12:06
JouleV
10.5k22559
asked Mar 25 at 12:05
user184234user184234
1
edited Mar 25 at 12:06
JouleV
10.5k22559
edited Mar 25 at 12:06
JouleV
10.5k22559
edited Mar 25 at 12:06
JouleV
10.5k22559
10.5k22559
asked Mar 25 at 12:05
user184234user184234
1
asked Mar 25 at 12:05
user184234user184234
1
asked Mar 25 at 12:05
user184234user184234
1
1
1
Put the chapter command inside the include file, or don't use include but input.
– Ulrike Fischer
Mar 25 at 12:07
2
it will not generate the error that you state but almost always thechapterheading should be inside the included file otherwise you get a forced page break after the heading. The error is telling you of a bad use of\but unless you show your code it is not possible to say what you have done wrong.
– David Carlisle
Mar 25 at 12:08
1
also never use the explicit.texextension withincludejust useinclude{./Chapter/Chaptername}
– David Carlisle
Mar 25 at 12:09
Hi Guys,Thanks for the quick response. I will check that, and swap the include by inputs and throw away the .tex's and report if the error still occurs.
– user184234
Mar 25 at 13:29
It's really better to put thechapterline in the included file; leave it in the main file but comment it out -- that will allow you to take advantage ofincludeonly. That said, the error is probably being reported for the line just previous to thechapterline -- and that means it's quite possibly in another file.
– barbara beeton
Mar 25 at 13:57
|
show 3 more comments
1
Put the chapter command inside the include file, or don't use include but input.
– Ulrike Fischer
Mar 25 at 12:07
2
it will not generate the error that you state but almost always thechapterheading should be inside the included file otherwise you get a forced page break after the heading. The error is telling you of a bad use of\but unless you show your code it is not possible to say what you have done wrong.
– David Carlisle
Mar 25 at 12:08
1
also never use the explicit.texextension withincludejust useinclude{./Chapter/Chaptername}
– David Carlisle
Mar 25 at 12:09
Hi Guys,Thanks for the quick response. I will check that, and swap the include by inputs and throw away the .tex's and report if the error still occurs.
– user184234
Mar 25 at 13:29
It's really better to put thechapterline in the included file; leave it in the main file but comment it out -- that will allow you to take advantage ofincludeonly. That said, the error is probably being reported for the line just previous to thechapterline -- and that means it's quite possibly in another file.
– barbara beeton
Mar 25 at 13:57
1
1
Put the chapter command inside the include file, or don't use include but input.
– Ulrike Fischer
Mar 25 at 12:07
Put the chapter command inside the include file, or don't use include but input.
– Ulrike Fischer
Mar 25 at 12:07
2
2
it will not generate the error that you state but almost always the
chapter heading should be inside the included file otherwise you get a forced page break after the heading. The error is telling you of a bad use of \ but unless you show your code it is not possible to say what you have done wrong.– David Carlisle
Mar 25 at 12:08
it will not generate the error that you state but almost always the
chapter heading should be inside the included file otherwise you get a forced page break after the heading. The error is telling you of a bad use of \ but unless you show your code it is not possible to say what you have done wrong.– David Carlisle
Mar 25 at 12:08
1
1
also never use the explicit
.tex extension with include just use include{./Chapter/Chaptername}– David Carlisle
Mar 25 at 12:09
also never use the explicit
.tex extension with include just use include{./Chapter/Chaptername}– David Carlisle
Mar 25 at 12:09
Hi Guys,Thanks for the quick response. I will check that, and swap the include by inputs and throw away the .tex's and report if the error still occurs.
– user184234
Mar 25 at 13:29
Hi Guys,Thanks for the quick response. I will check that, and swap the include by inputs and throw away the .tex's and report if the error still occurs.
– user184234
Mar 25 at 13:29
It's really better to put the
chapter line in the included file; leave it in the main file but comment it out -- that will allow you to take advantage of includeonly. That said, the error is probably being reported for the line just previous to the chapter line -- and that means it's quite possibly in another file.– barbara beeton
Mar 25 at 13:57
It's really better to put the
chapter line in the included file; leave it in the main file but comment it out -- that will allow you to take advantage of includeonly. That said, the error is probably being reported for the line just previous to the chapter line -- and that means it's quite possibly in another file.– barbara beeton
Mar 25 at 13:57
|
show 3 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
});
}
});
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%2f481336%2fstrange-no-line-here-to-end-error%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%2f481336%2fstrange-no-line-here-to-end-error%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
Put the chapter command inside the include file, or don't use include but input.
– Ulrike Fischer
Mar 25 at 12:07
2
it will not generate the error that you state but almost always the
chapterheading should be inside the included file otherwise you get a forced page break after the heading. The error is telling you of a bad use of\but unless you show your code it is not possible to say what you have done wrong.– David Carlisle
Mar 25 at 12:08
1
also never use the explicit
.texextension withincludejust useinclude{./Chapter/Chaptername}– David Carlisle
Mar 25 at 12:09
Hi Guys,Thanks for the quick response. I will check that, and swap the include by inputs and throw away the .tex's and report if the error still occurs.
– user184234
Mar 25 at 13:29
It's really better to put the
chapterline in the included file; leave it in the main file but comment it out -- that will allow you to take advantage ofincludeonly. That said, the error is probably being reported for the line just previous to thechapterline -- and that means it's quite possibly in another file.– barbara beeton
Mar 25 at 13:57