Section header text appearing one page early in a specific situation
Due to specific reasons, I created an alternative section command called nsection. The simplified version below should behave similarly to the original section command, however, I get an unexpected behavior regarding the header text.
When I use nsection at a place where page-break occurs, the header text appears one page too early. In the example below, the title D header should appear only on page 4, but it appears already on page 3. Apparently, the original section command does something to prevent this behavior, as the title C header does not appear on page 2.
I am interested in knowing why this happens and how to configure my custom command to prevent it.
I realized, that calling clearpage before my nsection solves the issue, however, this would result in unwanted behavior if placed anywhere but the page break.
documentclass[b5paper]{book}
usepackage{lipsum}
usepackage{fancyhdr}
DeclareDocumentCommand{nsection}{oom}{%
section*{#3}
fancyhead[RE,LO]{sffamily slshape #3}
}
begin{document}
pagestyle{fancy}
fancyhf{}
fancyhead[RE,LO]{rightmark}
fancyhead[LE,RO]{thepage}
section{title A}
lipsum[1-4]
section{title B}
lipsum[1-4]
section{title C}
lipsum[1-4]
nsection{title D}
lipsum[1-4]
end{document}
sectioning header-footer
asked 3 hours ago
OndrianOndrian
1,249614
add a comment |
Due to specific reasons, I created an alternative section command called nsection. The simplified version below should behave similarly to the original section command, however, I get an unexpected behavior regarding the header text.
When I use nsection at a place where page-break occurs, the header text appears one page too early. In the example below, the title D header should appear only on page 4, but it appears already on page 3. Apparently, the original section command does something to prevent this behavior, as the title C header does not appear on page 2.
I am interested in knowing why this happens and how to configure my custom command to prevent it.
I realized, that calling clearpage before my nsection solves the issue, however, this would result in unwanted behavior if placed anywhere but the page break.
documentclass[b5paper]{book}
usepackage{lipsum}
usepackage{fancyhdr}
DeclareDocumentCommand{nsection}{oom}{%
section*{#3}
fancyhead[RE,LO]{sffamily slshape #3}
}
begin{document}
pagestyle{fancy}
fancyhf{}
fancyhead[RE,LO]{rightmark}
fancyhead[LE,RO]{thepage}
section{title A}
lipsum[1-4]
section{title B}
lipsum[1-4]
section{title C}
lipsum[1-4]
nsection{title D}
lipsum[1-4]
end{document}
sectioning header-footer
asked 3 hours ago
OndrianOndrian
1,249614
the first question to be asked should be: Are all of those section (in general) be unnumbered? Why aren't you using the mark mechanism?markright{Wombat title}
– Johannes_B
14 mins ago
github.com/johannesbottcher/unnumberedtotoc might be suited for you.
– Johannes_B
13 mins ago
add a comment |
Due to specific reasons, I created an alternative section command called nsection. The simplified version below should behave similarly to the original section command, however, I get an unexpected behavior regarding the header text.
When I use nsection at a place where page-break occurs, the header text appears one page too early. In the example below, the title D header should appear only on page 4, but it appears already on page 3. Apparently, the original section command does something to prevent this behavior, as the title C header does not appear on page 2.
I am interested in knowing why this happens and how to configure my custom command to prevent it.
I realized, that calling clearpage before my nsection solves the issue, however, this would result in unwanted behavior if placed anywhere but the page break.
documentclass[b5paper]{book}
usepackage{lipsum}
usepackage{fancyhdr}
DeclareDocumentCommand{nsection}{oom}{%
section*{#3}
fancyhead[RE,LO]{sffamily slshape #3}
}
begin{document}
pagestyle{fancy}
fancyhf{}
fancyhead[RE,LO]{rightmark}
fancyhead[LE,RO]{thepage}
section{title A}
lipsum[1-4]
section{title B}
lipsum[1-4]
section{title C}
lipsum[1-4]
nsection{title D}
lipsum[1-4]
end{document}
sectioning header-footer
asked 3 hours ago
OndrianOndrian
1,249614
Due to specific reasons, I created an alternative section command called nsection. The simplified version below should behave similarly to the original section command, however, I get an unexpected behavior regarding the header text.
When I use nsection at a place where page-break occurs, the header text appears one page too early. In the example below, the title D header should appear only on page 4, but it appears already on page 3. Apparently, the original section command does something to prevent this behavior, as the title C header does not appear on page 2.
I am interested in knowing why this happens and how to configure my custom command to prevent it.
I realized, that calling clearpage before my nsection solves the issue, however, this would result in unwanted behavior if placed anywhere but the page break.
documentclass[b5paper]{book}
usepackage{lipsum}
usepackage{fancyhdr}
DeclareDocumentCommand{nsection}{oom}{%
section*{#3}
fancyhead[RE,LO]{sffamily slshape #3}
}
begin{document}
pagestyle{fancy}
fancyhf{}
fancyhead[RE,LO]{rightmark}
fancyhead[LE,RO]{thepage}
section{title A}
lipsum[1-4]
section{title B}
lipsum[1-4]
section{title C}
lipsum[1-4]
nsection{title D}
lipsum[1-4]
end{document}
sectioning header-footer
sectioning header-footer
asked 3 hours ago
OndrianOndrian
1,249614
asked 3 hours ago
OndrianOndrian
1,249614
asked 3 hours ago
OndrianOndrian
1,249614
asked 3 hours ago
OndrianOndrian
1,249614
asked 3 hours ago
OndrianOndrian
1,249614
1,249614
the first question to be asked should be: Are all of those section (in general) be unnumbered? Why aren't you using the mark mechanism?markright{Wombat title}
– Johannes_B
14 mins ago
github.com/johannesbottcher/unnumberedtotoc might be suited for you.
– Johannes_B
13 mins ago
add a comment |
the first question to be asked should be: Are all of those section (in general) be unnumbered? Why aren't you using the mark mechanism?markright{Wombat title}
– Johannes_B
14 mins ago
github.com/johannesbottcher/unnumberedtotoc might be suited for you.
– Johannes_B
13 mins ago
the first question to be asked should be: Are all of those section (in general) be unnumbered? Why aren't you using the mark mechanism?
markright{Wombat title}– Johannes_B
14 mins ago
the first question to be asked should be: Are all of those section (in general) be unnumbered? Why aren't you using the mark mechanism?
markright{Wombat title}– Johannes_B
14 mins ago
github.com/johannesbottcher/unnumberedtotoc might be suited for you.
– Johannes_B
13 mins ago
github.com/johannesbottcher/unnumberedtotoc might be suited for you.
– Johannes_B
13 mins 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%2f481826%2fsection-header-text-appearing-one-page-early-in-a-specific-situation%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%2f481826%2fsection-header-text-appearing-one-page-early-in-a-specific-situation%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
the first question to be asked should be: Are all of those section (in general) be unnumbered? Why aren't you using the mark mechanism?
markright{Wombat title}– Johannes_B
14 mins ago
github.com/johannesbottcher/unnumberedtotoc might be suited for you.
– Johannes_B
13 mins ago