When to use par and when \, newline, or blank lines
What is the difference between par
, newline and \
and blank lines and when should I use par
instead of \
?
line-breaking paragraphs best-practices syntax
add a comment |
What is the difference between par
, newline and \
and blank lines and when should I use par
instead of \
?
line-breaking paragraphs best-practices syntax
10
Well, usepar
when you want a new paragraph (and don't wan to insert a blank line for some reason, such as in macro/environment definitions), and use\
inarray
andtabular
. That's the rules I have been following.
– Peter Grill
Nov 14 '12 at 0:57
add a comment |
What is the difference between par
, newline and \
and blank lines and when should I use par
instead of \
?
line-breaking paragraphs best-practices syntax
What is the difference between par
, newline and \
and blank lines and when should I use par
instead of \
?
line-breaking paragraphs best-practices syntax
line-breaking paragraphs best-practices syntax
edited 4 hours ago
Jonas Stein
asked Nov 14 '12 at 0:56
Jonas SteinJonas Stein
3,26542744
3,26542744
10
Well, usepar
when you want a new paragraph (and don't wan to insert a blank line for some reason, such as in macro/environment definitions), and use\
inarray
andtabular
. That's the rules I have been following.
– Peter Grill
Nov 14 '12 at 0:57
add a comment |
10
Well, usepar
when you want a new paragraph (and don't wan to insert a blank line for some reason, such as in macro/environment definitions), and use\
inarray
andtabular
. That's the rules I have been following.
– Peter Grill
Nov 14 '12 at 0:57
10
10
Well, use
par
when you want a new paragraph (and don't wan to insert a blank line for some reason, such as in macro/environment definitions), and use \
in array
and tabular
. That's the rules I have been following.– Peter Grill
Nov 14 '12 at 0:57
Well, use
par
when you want a new paragraph (and don't wan to insert a blank line for some reason, such as in macro/environment definitions), and use \
in array
and tabular
. That's the rules I have been following.– Peter Grill
Nov 14 '12 at 0:57
add a comment |
2 Answers
2
active
oldest
votes
par
is a TeX primitive and is the same as a blank line (except in special environments such as verbatim
where the usual rules don't apply). It ends horizontal mode, causes TeX to break the horizontal text into lines placed on the current vertical list, and exercises the page breaker which may possibly cause the next page to be shipped out.
\
is different in almost every respect. It is a macro not a primitive, and its definition changes wildly in almost every LaTeX definition. The definition in normal text, a center
environment a flushleft
environment and a table are all different.
In normal running text when it forces a linebreak it is essentially a shorthand for newline
this does not end horizontal mode or end the paragraph, it just inserts some glue and penalties at that point into the horizontal material so that when the paragraph does end a linebreak will occur at that point with the short line padded with white space.
\
at the end of a paragraph causes bad output with an empty, maximally underfull, box, and so you get a warning about badness 10000, the visual affect looks a bit like extra vertical space but it is not it is an extra spurious line at the end of the paragraph, and for example it is not dropped at a page break and will break widow/club line calculations.
You should rarely need to use \
in documents apart from its use in alignments (where it is a macro based on the cr
primitive), and you should rarely need par
in documents as a blank line should suffice.
15
a consequence of using\
instead of paragraph breaks is that (la)tex continues to load text into memory, and doesn't actually output anything until an actual paragraph break occurs. this may not be so important now, with memory capacity being so large, but when memory was a much more scarce resource, failing to use paragraph breaks was a sure way to run out of memory and crash the job before it finished. it will still slow down the processing when the "paragraphs" are very long.
– barbara beeton
May 2 '14 at 1:39
1
@JonasStein hmm I would have said better to ask a new question but someone did that but it was closed as duplicate of this (not by me:-) so OK if you edit the question to ask about blank lines I'll add something here (basically they are the same aspar
except in verbatim and other special cases)
– David Carlisle
Aug 29 '16 at 5:40
I've seen people say that using\
is a cause of bad box warnings. Is it? cc. @barbarabeeton
– cfr
Jul 9 '18 at 1:12
1
@cfr\
at the end of a paragraph causes spectacularly bad output with an empty, maximally underfull, box, and so you get a warning about badness 10000, if that is what you mean. I wouldn't say that\
itself makes the warning, as that makes it sound like it is some kind of spurious warning and the warning itself is the issue.
– David Carlisle
Jul 9 '18 at 6:54
@DavidCarlisle But I can't get it to give me any warnings at all. Or did you mean it only does so at the end of paragraphs?
– cfr
Jul 9 '18 at 22:21
|
show 1 more comment
In text mode, par
starts a new paragraph, while \
ends the current line.
So when to use each one?
\
should be used with parsimony, when you want to break of the rhythm of your current argumentation, but without jumping to a new idea / argument (which would require starting a new paragraph).
par
should actually be used even less frequently. Not that you do not want to start new paragraphs (you do want to keep paragraphs to reasonable lengths!), but you should start new paragraphs by leaving an empty line in your TeX code. This has the exact same effect as using par
, but will make your code much more readable. par
is therefore mostly used when defining macros.
Note that outside of text mode, par
will usually lead to an error, while \
usually works as expected to start a new line (like while in an tabular
or array
).
` in text usually works except when it says
! LaTeX Error: There's no line here to end. (e.g., dual
` to produce two blank lines in a paragraph ... there are more reliable ways to do that.) [gosh — don't understand where that
– wasteofspace
Jan 12 '15 at 20:04
the previous one by me showed my non-understanding of markdown (or whatever it is). i was trying to use backslashes, and the output was all to pot ... and in the allowed 5 minutes i couldn't sort the problem. must remember to keep my mouth shut in future... :-(
– wasteofspace
Jan 15 '15 at 10:13
1
@wasteofspace to put a double backslash in code markdown you need to type backtick, dobule backslash, space, backtick. This yields\
. I guess you comment above was meant to be «\
in text usually works except when it says! LaTeX Error: There's no line here to end
. (e.g., dual\
to produce two blank lines in a paragraph ... there are more reliable ways to do that.)», right?
– MickG
May 29 '15 at 9:49
add a comment |
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%2f82664%2fwhen-to-use-par-and-when-newline-or-blank-lines%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
par
is a TeX primitive and is the same as a blank line (except in special environments such as verbatim
where the usual rules don't apply). It ends horizontal mode, causes TeX to break the horizontal text into lines placed on the current vertical list, and exercises the page breaker which may possibly cause the next page to be shipped out.
\
is different in almost every respect. It is a macro not a primitive, and its definition changes wildly in almost every LaTeX definition. The definition in normal text, a center
environment a flushleft
environment and a table are all different.
In normal running text when it forces a linebreak it is essentially a shorthand for newline
this does not end horizontal mode or end the paragraph, it just inserts some glue and penalties at that point into the horizontal material so that when the paragraph does end a linebreak will occur at that point with the short line padded with white space.
\
at the end of a paragraph causes bad output with an empty, maximally underfull, box, and so you get a warning about badness 10000, the visual affect looks a bit like extra vertical space but it is not it is an extra spurious line at the end of the paragraph, and for example it is not dropped at a page break and will break widow/club line calculations.
You should rarely need to use \
in documents apart from its use in alignments (where it is a macro based on the cr
primitive), and you should rarely need par
in documents as a blank line should suffice.
15
a consequence of using\
instead of paragraph breaks is that (la)tex continues to load text into memory, and doesn't actually output anything until an actual paragraph break occurs. this may not be so important now, with memory capacity being so large, but when memory was a much more scarce resource, failing to use paragraph breaks was a sure way to run out of memory and crash the job before it finished. it will still slow down the processing when the "paragraphs" are very long.
– barbara beeton
May 2 '14 at 1:39
1
@JonasStein hmm I would have said better to ask a new question but someone did that but it was closed as duplicate of this (not by me:-) so OK if you edit the question to ask about blank lines I'll add something here (basically they are the same aspar
except in verbatim and other special cases)
– David Carlisle
Aug 29 '16 at 5:40
I've seen people say that using\
is a cause of bad box warnings. Is it? cc. @barbarabeeton
– cfr
Jul 9 '18 at 1:12
1
@cfr\
at the end of a paragraph causes spectacularly bad output with an empty, maximally underfull, box, and so you get a warning about badness 10000, if that is what you mean. I wouldn't say that\
itself makes the warning, as that makes it sound like it is some kind of spurious warning and the warning itself is the issue.
– David Carlisle
Jul 9 '18 at 6:54
@DavidCarlisle But I can't get it to give me any warnings at all. Or did you mean it only does so at the end of paragraphs?
– cfr
Jul 9 '18 at 22:21
|
show 1 more comment
par
is a TeX primitive and is the same as a blank line (except in special environments such as verbatim
where the usual rules don't apply). It ends horizontal mode, causes TeX to break the horizontal text into lines placed on the current vertical list, and exercises the page breaker which may possibly cause the next page to be shipped out.
\
is different in almost every respect. It is a macro not a primitive, and its definition changes wildly in almost every LaTeX definition. The definition in normal text, a center
environment a flushleft
environment and a table are all different.
In normal running text when it forces a linebreak it is essentially a shorthand for newline
this does not end horizontal mode or end the paragraph, it just inserts some glue and penalties at that point into the horizontal material so that when the paragraph does end a linebreak will occur at that point with the short line padded with white space.
\
at the end of a paragraph causes bad output with an empty, maximally underfull, box, and so you get a warning about badness 10000, the visual affect looks a bit like extra vertical space but it is not it is an extra spurious line at the end of the paragraph, and for example it is not dropped at a page break and will break widow/club line calculations.
You should rarely need to use \
in documents apart from its use in alignments (where it is a macro based on the cr
primitive), and you should rarely need par
in documents as a blank line should suffice.
15
a consequence of using\
instead of paragraph breaks is that (la)tex continues to load text into memory, and doesn't actually output anything until an actual paragraph break occurs. this may not be so important now, with memory capacity being so large, but when memory was a much more scarce resource, failing to use paragraph breaks was a sure way to run out of memory and crash the job before it finished. it will still slow down the processing when the "paragraphs" are very long.
– barbara beeton
May 2 '14 at 1:39
1
@JonasStein hmm I would have said better to ask a new question but someone did that but it was closed as duplicate of this (not by me:-) so OK if you edit the question to ask about blank lines I'll add something here (basically they are the same aspar
except in verbatim and other special cases)
– David Carlisle
Aug 29 '16 at 5:40
I've seen people say that using\
is a cause of bad box warnings. Is it? cc. @barbarabeeton
– cfr
Jul 9 '18 at 1:12
1
@cfr\
at the end of a paragraph causes spectacularly bad output with an empty, maximally underfull, box, and so you get a warning about badness 10000, if that is what you mean. I wouldn't say that\
itself makes the warning, as that makes it sound like it is some kind of spurious warning and the warning itself is the issue.
– David Carlisle
Jul 9 '18 at 6:54
@DavidCarlisle But I can't get it to give me any warnings at all. Or did you mean it only does so at the end of paragraphs?
– cfr
Jul 9 '18 at 22:21
|
show 1 more comment
par
is a TeX primitive and is the same as a blank line (except in special environments such as verbatim
where the usual rules don't apply). It ends horizontal mode, causes TeX to break the horizontal text into lines placed on the current vertical list, and exercises the page breaker which may possibly cause the next page to be shipped out.
\
is different in almost every respect. It is a macro not a primitive, and its definition changes wildly in almost every LaTeX definition. The definition in normal text, a center
environment a flushleft
environment and a table are all different.
In normal running text when it forces a linebreak it is essentially a shorthand for newline
this does not end horizontal mode or end the paragraph, it just inserts some glue and penalties at that point into the horizontal material so that when the paragraph does end a linebreak will occur at that point with the short line padded with white space.
\
at the end of a paragraph causes bad output with an empty, maximally underfull, box, and so you get a warning about badness 10000, the visual affect looks a bit like extra vertical space but it is not it is an extra spurious line at the end of the paragraph, and for example it is not dropped at a page break and will break widow/club line calculations.
You should rarely need to use \
in documents apart from its use in alignments (where it is a macro based on the cr
primitive), and you should rarely need par
in documents as a blank line should suffice.
par
is a TeX primitive and is the same as a blank line (except in special environments such as verbatim
where the usual rules don't apply). It ends horizontal mode, causes TeX to break the horizontal text into lines placed on the current vertical list, and exercises the page breaker which may possibly cause the next page to be shipped out.
\
is different in almost every respect. It is a macro not a primitive, and its definition changes wildly in almost every LaTeX definition. The definition in normal text, a center
environment a flushleft
environment and a table are all different.
In normal running text when it forces a linebreak it is essentially a shorthand for newline
this does not end horizontal mode or end the paragraph, it just inserts some glue and penalties at that point into the horizontal material so that when the paragraph does end a linebreak will occur at that point with the short line padded with white space.
\
at the end of a paragraph causes bad output with an empty, maximally underfull, box, and so you get a warning about badness 10000, the visual affect looks a bit like extra vertical space but it is not it is an extra spurious line at the end of the paragraph, and for example it is not dropped at a page break and will break widow/club line calculations.
You should rarely need to use \
in documents apart from its use in alignments (where it is a macro based on the cr
primitive), and you should rarely need par
in documents as a blank line should suffice.
edited Mar 8 at 21:16
answered Nov 14 '12 at 1:07
David CarlisleDavid Carlisle
497k4111441890
497k4111441890
15
a consequence of using\
instead of paragraph breaks is that (la)tex continues to load text into memory, and doesn't actually output anything until an actual paragraph break occurs. this may not be so important now, with memory capacity being so large, but when memory was a much more scarce resource, failing to use paragraph breaks was a sure way to run out of memory and crash the job before it finished. it will still slow down the processing when the "paragraphs" are very long.
– barbara beeton
May 2 '14 at 1:39
1
@JonasStein hmm I would have said better to ask a new question but someone did that but it was closed as duplicate of this (not by me:-) so OK if you edit the question to ask about blank lines I'll add something here (basically they are the same aspar
except in verbatim and other special cases)
– David Carlisle
Aug 29 '16 at 5:40
I've seen people say that using\
is a cause of bad box warnings. Is it? cc. @barbarabeeton
– cfr
Jul 9 '18 at 1:12
1
@cfr\
at the end of a paragraph causes spectacularly bad output with an empty, maximally underfull, box, and so you get a warning about badness 10000, if that is what you mean. I wouldn't say that\
itself makes the warning, as that makes it sound like it is some kind of spurious warning and the warning itself is the issue.
– David Carlisle
Jul 9 '18 at 6:54
@DavidCarlisle But I can't get it to give me any warnings at all. Or did you mean it only does so at the end of paragraphs?
– cfr
Jul 9 '18 at 22:21
|
show 1 more comment
15
a consequence of using\
instead of paragraph breaks is that (la)tex continues to load text into memory, and doesn't actually output anything until an actual paragraph break occurs. this may not be so important now, with memory capacity being so large, but when memory was a much more scarce resource, failing to use paragraph breaks was a sure way to run out of memory and crash the job before it finished. it will still slow down the processing when the "paragraphs" are very long.
– barbara beeton
May 2 '14 at 1:39
1
@JonasStein hmm I would have said better to ask a new question but someone did that but it was closed as duplicate of this (not by me:-) so OK if you edit the question to ask about blank lines I'll add something here (basically they are the same aspar
except in verbatim and other special cases)
– David Carlisle
Aug 29 '16 at 5:40
I've seen people say that using\
is a cause of bad box warnings. Is it? cc. @barbarabeeton
– cfr
Jul 9 '18 at 1:12
1
@cfr\
at the end of a paragraph causes spectacularly bad output with an empty, maximally underfull, box, and so you get a warning about badness 10000, if that is what you mean. I wouldn't say that\
itself makes the warning, as that makes it sound like it is some kind of spurious warning and the warning itself is the issue.
– David Carlisle
Jul 9 '18 at 6:54
@DavidCarlisle But I can't get it to give me any warnings at all. Or did you mean it only does so at the end of paragraphs?
– cfr
Jul 9 '18 at 22:21
15
15
a consequence of using
\
instead of paragraph breaks is that (la)tex continues to load text into memory, and doesn't actually output anything until an actual paragraph break occurs. this may not be so important now, with memory capacity being so large, but when memory was a much more scarce resource, failing to use paragraph breaks was a sure way to run out of memory and crash the job before it finished. it will still slow down the processing when the "paragraphs" are very long.– barbara beeton
May 2 '14 at 1:39
a consequence of using
\
instead of paragraph breaks is that (la)tex continues to load text into memory, and doesn't actually output anything until an actual paragraph break occurs. this may not be so important now, with memory capacity being so large, but when memory was a much more scarce resource, failing to use paragraph breaks was a sure way to run out of memory and crash the job before it finished. it will still slow down the processing when the "paragraphs" are very long.– barbara beeton
May 2 '14 at 1:39
1
1
@JonasStein hmm I would have said better to ask a new question but someone did that but it was closed as duplicate of this (not by me:-) so OK if you edit the question to ask about blank lines I'll add something here (basically they are the same as
par
except in verbatim and other special cases)– David Carlisle
Aug 29 '16 at 5:40
@JonasStein hmm I would have said better to ask a new question but someone did that but it was closed as duplicate of this (not by me:-) so OK if you edit the question to ask about blank lines I'll add something here (basically they are the same as
par
except in verbatim and other special cases)– David Carlisle
Aug 29 '16 at 5:40
I've seen people say that using
\
is a cause of bad box warnings. Is it? cc. @barbarabeeton– cfr
Jul 9 '18 at 1:12
I've seen people say that using
\
is a cause of bad box warnings. Is it? cc. @barbarabeeton– cfr
Jul 9 '18 at 1:12
1
1
@cfr
\
at the end of a paragraph causes spectacularly bad output with an empty, maximally underfull, box, and so you get a warning about badness 10000, if that is what you mean. I wouldn't say that \
itself makes the warning, as that makes it sound like it is some kind of spurious warning and the warning itself is the issue.– David Carlisle
Jul 9 '18 at 6:54
@cfr
\
at the end of a paragraph causes spectacularly bad output with an empty, maximally underfull, box, and so you get a warning about badness 10000, if that is what you mean. I wouldn't say that \
itself makes the warning, as that makes it sound like it is some kind of spurious warning and the warning itself is the issue.– David Carlisle
Jul 9 '18 at 6:54
@DavidCarlisle But I can't get it to give me any warnings at all. Or did you mean it only does so at the end of paragraphs?
– cfr
Jul 9 '18 at 22:21
@DavidCarlisle But I can't get it to give me any warnings at all. Or did you mean it only does so at the end of paragraphs?
– cfr
Jul 9 '18 at 22:21
|
show 1 more comment
In text mode, par
starts a new paragraph, while \
ends the current line.
So when to use each one?
\
should be used with parsimony, when you want to break of the rhythm of your current argumentation, but without jumping to a new idea / argument (which would require starting a new paragraph).
par
should actually be used even less frequently. Not that you do not want to start new paragraphs (you do want to keep paragraphs to reasonable lengths!), but you should start new paragraphs by leaving an empty line in your TeX code. This has the exact same effect as using par
, but will make your code much more readable. par
is therefore mostly used when defining macros.
Note that outside of text mode, par
will usually lead to an error, while \
usually works as expected to start a new line (like while in an tabular
or array
).
` in text usually works except when it says
! LaTeX Error: There's no line here to end. (e.g., dual
` to produce two blank lines in a paragraph ... there are more reliable ways to do that.) [gosh — don't understand where that
– wasteofspace
Jan 12 '15 at 20:04
the previous one by me showed my non-understanding of markdown (or whatever it is). i was trying to use backslashes, and the output was all to pot ... and in the allowed 5 minutes i couldn't sort the problem. must remember to keep my mouth shut in future... :-(
– wasteofspace
Jan 15 '15 at 10:13
1
@wasteofspace to put a double backslash in code markdown you need to type backtick, dobule backslash, space, backtick. This yields\
. I guess you comment above was meant to be «\
in text usually works except when it says! LaTeX Error: There's no line here to end
. (e.g., dual\
to produce two blank lines in a paragraph ... there are more reliable ways to do that.)», right?
– MickG
May 29 '15 at 9:49
add a comment |
In text mode, par
starts a new paragraph, while \
ends the current line.
So when to use each one?
\
should be used with parsimony, when you want to break of the rhythm of your current argumentation, but without jumping to a new idea / argument (which would require starting a new paragraph).
par
should actually be used even less frequently. Not that you do not want to start new paragraphs (you do want to keep paragraphs to reasonable lengths!), but you should start new paragraphs by leaving an empty line in your TeX code. This has the exact same effect as using par
, but will make your code much more readable. par
is therefore mostly used when defining macros.
Note that outside of text mode, par
will usually lead to an error, while \
usually works as expected to start a new line (like while in an tabular
or array
).
` in text usually works except when it says
! LaTeX Error: There's no line here to end. (e.g., dual
` to produce two blank lines in a paragraph ... there are more reliable ways to do that.) [gosh — don't understand where that
– wasteofspace
Jan 12 '15 at 20:04
the previous one by me showed my non-understanding of markdown (or whatever it is). i was trying to use backslashes, and the output was all to pot ... and in the allowed 5 minutes i couldn't sort the problem. must remember to keep my mouth shut in future... :-(
– wasteofspace
Jan 15 '15 at 10:13
1
@wasteofspace to put a double backslash in code markdown you need to type backtick, dobule backslash, space, backtick. This yields\
. I guess you comment above was meant to be «\
in text usually works except when it says! LaTeX Error: There's no line here to end
. (e.g., dual\
to produce two blank lines in a paragraph ... there are more reliable ways to do that.)», right?
– MickG
May 29 '15 at 9:49
add a comment |
In text mode, par
starts a new paragraph, while \
ends the current line.
So when to use each one?
\
should be used with parsimony, when you want to break of the rhythm of your current argumentation, but without jumping to a new idea / argument (which would require starting a new paragraph).
par
should actually be used even less frequently. Not that you do not want to start new paragraphs (you do want to keep paragraphs to reasonable lengths!), but you should start new paragraphs by leaving an empty line in your TeX code. This has the exact same effect as using par
, but will make your code much more readable. par
is therefore mostly used when defining macros.
Note that outside of text mode, par
will usually lead to an error, while \
usually works as expected to start a new line (like while in an tabular
or array
).
In text mode, par
starts a new paragraph, while \
ends the current line.
So when to use each one?
\
should be used with parsimony, when you want to break of the rhythm of your current argumentation, but without jumping to a new idea / argument (which would require starting a new paragraph).
par
should actually be used even less frequently. Not that you do not want to start new paragraphs (you do want to keep paragraphs to reasonable lengths!), but you should start new paragraphs by leaving an empty line in your TeX code. This has the exact same effect as using par
, but will make your code much more readable. par
is therefore mostly used when defining macros.
Note that outside of text mode, par
will usually lead to an error, while \
usually works as expected to start a new line (like while in an tabular
or array
).
answered Nov 14 '12 at 1:15
XavierXavier
10.8k64772
10.8k64772
` in text usually works except when it says
! LaTeX Error: There's no line here to end. (e.g., dual
` to produce two blank lines in a paragraph ... there are more reliable ways to do that.) [gosh — don't understand where that
– wasteofspace
Jan 12 '15 at 20:04
the previous one by me showed my non-understanding of markdown (or whatever it is). i was trying to use backslashes, and the output was all to pot ... and in the allowed 5 minutes i couldn't sort the problem. must remember to keep my mouth shut in future... :-(
– wasteofspace
Jan 15 '15 at 10:13
1
@wasteofspace to put a double backslash in code markdown you need to type backtick, dobule backslash, space, backtick. This yields\
. I guess you comment above was meant to be «\
in text usually works except when it says! LaTeX Error: There's no line here to end
. (e.g., dual\
to produce two blank lines in a paragraph ... there are more reliable ways to do that.)», right?
– MickG
May 29 '15 at 9:49
add a comment |
` in text usually works except when it says
! LaTeX Error: There's no line here to end. (e.g., dual
` to produce two blank lines in a paragraph ... there are more reliable ways to do that.) [gosh — don't understand where that
– wasteofspace
Jan 12 '15 at 20:04
the previous one by me showed my non-understanding of markdown (or whatever it is). i was trying to use backslashes, and the output was all to pot ... and in the allowed 5 minutes i couldn't sort the problem. must remember to keep my mouth shut in future... :-(
– wasteofspace
Jan 15 '15 at 10:13
1
@wasteofspace to put a double backslash in code markdown you need to type backtick, dobule backslash, space, backtick. This yields\
. I guess you comment above was meant to be «\
in text usually works except when it says! LaTeX Error: There's no line here to end
. (e.g., dual\
to produce two blank lines in a paragraph ... there are more reliable ways to do that.)», right?
– MickG
May 29 '15 at 9:49
` in text usually works except when it says
! LaTeX Error: There's no line here to end. (e.g., dual
` to produce two blank lines in a paragraph ... there are more reliable ways to do that.) [gosh — don't understand where that– wasteofspace
Jan 12 '15 at 20:04
` in text usually works except when it says
! LaTeX Error: There's no line here to end. (e.g., dual
` to produce two blank lines in a paragraph ... there are more reliable ways to do that.) [gosh — don't understand where that– wasteofspace
Jan 12 '15 at 20:04
the previous one by me showed my non-understanding of markdown (or whatever it is). i was trying to use backslashes, and the output was all to pot ... and in the allowed 5 minutes i couldn't sort the problem. must remember to keep my mouth shut in future... :-(
– wasteofspace
Jan 15 '15 at 10:13
the previous one by me showed my non-understanding of markdown (or whatever it is). i was trying to use backslashes, and the output was all to pot ... and in the allowed 5 minutes i couldn't sort the problem. must remember to keep my mouth shut in future... :-(
– wasteofspace
Jan 15 '15 at 10:13
1
1
@wasteofspace to put a double backslash in code markdown you need to type backtick, dobule backslash, space, backtick. This yields
\
. I guess you comment above was meant to be «\
in text usually works except when it says ! LaTeX Error: There's no line here to end
. (e.g., dual \
to produce two blank lines in a paragraph ... there are more reliable ways to do that.)», right?– MickG
May 29 '15 at 9:49
@wasteofspace to put a double backslash in code markdown you need to type backtick, dobule backslash, space, backtick. This yields
\
. I guess you comment above was meant to be «\
in text usually works except when it says ! LaTeX Error: There's no line here to end
. (e.g., dual \
to produce two blank lines in a paragraph ... there are more reliable ways to do that.)», right?– MickG
May 29 '15 at 9:49
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%2f82664%2fwhen-to-use-par-and-when-newline-or-blank-lines%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
10
Well, use
par
when you want a new paragraph (and don't wan to insert a blank line for some reason, such as in macro/environment definitions), and use\
inarray
andtabular
. That's the rules I have been following.– Peter Grill
Nov 14 '12 at 0:57