Why is tex_par:D behaving differently from par?
As illustrated in the MWE, using tex_par:D rather than par within a list environment leads to unexpected side-effects. Is this intended behavior? If so, it's likely to break a lot of code. I ran across this issue trying to use the current version of lipsum, which uses the expl3 version, within KOMA-Script's addmargin environment, and any other environment that uses the same list trick is going to be broken in this case.
documentclass{article}
usepackage{xparse}
ExplSyntaxOn
NewDocumentCommand{mypar} {} {tex_par:D}
ExplSyntaxOff
begin{document}
noindenthrulefill
begin{list}{}{
setlength{leftmargin}{2cm}
setlength{rightmargin}{2cm}
}
item Here's a paragraph with enough text that we can see where the line wraps.
Here's another paragraph after a traditional paragraph break. This is fine.
Now we'll end this one with the expl3 version to see what happens next.mypar
And here's a forth to see where we are. The left and right margins are now disregarded.par
And they don't come back.
end{list}
end{document}
Resulting in this output:

lists indentation expl3
add a comment |
As illustrated in the MWE, using tex_par:D rather than par within a list environment leads to unexpected side-effects. Is this intended behavior? If so, it's likely to break a lot of code. I ran across this issue trying to use the current version of lipsum, which uses the expl3 version, within KOMA-Script's addmargin environment, and any other environment that uses the same list trick is going to be broken in this case.
documentclass{article}
usepackage{xparse}
ExplSyntaxOn
NewDocumentCommand{mypar} {} {tex_par:D}
ExplSyntaxOff
begin{document}
noindenthrulefill
begin{list}{}{
setlength{leftmargin}{2cm}
setlength{rightmargin}{2cm}
}
item Here's a paragraph with enough text that we can see where the line wraps.
Here's another paragraph after a traditional paragraph break. This is fine.
Now we'll end this one with the expl3 version to see what happens next.mypar
And here's a forth to see where we are. The left and right margins are now disregarded.par
And they don't come back.
end{list}
end{document}
Resulting in this output:

lists indentation expl3
Doesn't par has a special meaning inside lists? Thus the inserted mypar is different from the normal par inside lists.
– daleif
5 mins ago
add a comment |
As illustrated in the MWE, using tex_par:D rather than par within a list environment leads to unexpected side-effects. Is this intended behavior? If so, it's likely to break a lot of code. I ran across this issue trying to use the current version of lipsum, which uses the expl3 version, within KOMA-Script's addmargin environment, and any other environment that uses the same list trick is going to be broken in this case.
documentclass{article}
usepackage{xparse}
ExplSyntaxOn
NewDocumentCommand{mypar} {} {tex_par:D}
ExplSyntaxOff
begin{document}
noindenthrulefill
begin{list}{}{
setlength{leftmargin}{2cm}
setlength{rightmargin}{2cm}
}
item Here's a paragraph with enough text that we can see where the line wraps.
Here's another paragraph after a traditional paragraph break. This is fine.
Now we'll end this one with the expl3 version to see what happens next.mypar
And here's a forth to see where we are. The left and right margins are now disregarded.par
And they don't come back.
end{list}
end{document}
Resulting in this output:

lists indentation expl3
As illustrated in the MWE, using tex_par:D rather than par within a list environment leads to unexpected side-effects. Is this intended behavior? If so, it's likely to break a lot of code. I ran across this issue trying to use the current version of lipsum, which uses the expl3 version, within KOMA-Script's addmargin environment, and any other environment that uses the same list trick is going to be broken in this case.
documentclass{article}
usepackage{xparse}
ExplSyntaxOn
NewDocumentCommand{mypar} {} {tex_par:D}
ExplSyntaxOff
begin{document}
noindenthrulefill
begin{list}{}{
setlength{leftmargin}{2cm}
setlength{rightmargin}{2cm}
}
item Here's a paragraph with enough text that we can see where the line wraps.
Here's another paragraph after a traditional paragraph break. This is fine.
Now we'll end this one with the expl3 version to see what happens next.mypar
And here's a forth to see where we are. The left and right margins are now disregarded.par
And they don't come back.
end{list}
end{document}
Resulting in this output:

lists indentation expl3
lists indentation expl3
asked 10 mins ago
Karl Hagen
659416
659416
Doesn't par has a special meaning inside lists? Thus the inserted mypar is different from the normal par inside lists.
– daleif
5 mins ago
add a comment |
Doesn't par has a special meaning inside lists? Thus the inserted mypar is different from the normal par inside lists.
– daleif
5 mins ago
Doesn't par has a special meaning inside lists? Thus the inserted mypar is different from the normal par inside lists.
– daleif
5 mins ago
Doesn't par has a special meaning inside lists? Thus the inserted mypar is different from the normal par inside lists.
– daleif
5 mins ago
add a comment |
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%2f467245%2fwhy-is-tex-pard-behaving-differently-from-par%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f467245%2fwhy-is-tex-pard-behaving-differently-from-par%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
Doesn't par has a special meaning inside lists? Thus the inserted mypar is different from the normal par inside lists.
– daleif
5 mins ago