titlesec makes fancyhdr mistreating the document class












0















MWE is pretty simple:



documentclass[twoside]{article}
%usepackage{titlesec}
usepackage{fancyhdr}
begin{document}
pagestyle{fancy}
section{tist1}
subsection{a}
newpage
subsection{b}
end{document}


On the second page, there is the subsection name on the left and the section name on the right.



Now, uncomment the titlesec import, and the behaviour changes: the section name on the left and nothing (actually, a fantom of non-existent chapter name) on the right.



It happens because titlesec redefines chapter as relax, though normally it's undefined in article class. The fancyhdr packages has a following check:



ifxchapter@undefined


It fails, and marks are defined as in classes that have chapters. I can work it around with



letchapterundefined


after usepackage{titlesec}, or by explicitly redefining sectionmark/subsectionmark after pagestyle{fancy}. But why should I? Is this a bug in titlesec, or setting chapter to relax has some purpose?



UPD:



 *File List*
article.cls 2018/09/03 v1.4i Standard LaTeX document class
size10.clo 2018/09/03 v1.4i Standard LaTeX file (size option)
titlesec.sty 2016/03/21 v2.10.2 Sectioning titles
fancyhdr.sty 2017/06/30 v3.9a Extensive control of page headers and footers
***********









share|improve this question

























  • What versions of the packages are you using? (Put listfiles before documentclass and report the output here.) I get identical output with or without titlesec.

    – Alan Munn
    Mar 12 at 2:54













  • @AlanMunn added to the post.

    – bodqhrohro
    Mar 12 at 12:02











  • Update fancyhdr; the current version is 2019/01/31 v3.10

    – egreg
    Mar 12 at 12:14











  • @egreg yes, the new version of fancyhdr has a f@nch@ifundefined macro which handles both undefined and relax, thanks. But anyway, is there any purpose to set chapter to relax instead of undefined in titlesec?

    – bodqhrohro
    Mar 12 at 12:31











  • @bodqhrohro That should be asked to the package maintainer.

    – egreg
    Mar 12 at 13:06
















0















MWE is pretty simple:



documentclass[twoside]{article}
%usepackage{titlesec}
usepackage{fancyhdr}
begin{document}
pagestyle{fancy}
section{tist1}
subsection{a}
newpage
subsection{b}
end{document}


On the second page, there is the subsection name on the left and the section name on the right.



Now, uncomment the titlesec import, and the behaviour changes: the section name on the left and nothing (actually, a fantom of non-existent chapter name) on the right.



It happens because titlesec redefines chapter as relax, though normally it's undefined in article class. The fancyhdr packages has a following check:



ifxchapter@undefined


It fails, and marks are defined as in classes that have chapters. I can work it around with



letchapterundefined


after usepackage{titlesec}, or by explicitly redefining sectionmark/subsectionmark after pagestyle{fancy}. But why should I? Is this a bug in titlesec, or setting chapter to relax has some purpose?



UPD:



 *File List*
article.cls 2018/09/03 v1.4i Standard LaTeX document class
size10.clo 2018/09/03 v1.4i Standard LaTeX file (size option)
titlesec.sty 2016/03/21 v2.10.2 Sectioning titles
fancyhdr.sty 2017/06/30 v3.9a Extensive control of page headers and footers
***********









share|improve this question

























  • What versions of the packages are you using? (Put listfiles before documentclass and report the output here.) I get identical output with or without titlesec.

    – Alan Munn
    Mar 12 at 2:54













  • @AlanMunn added to the post.

    – bodqhrohro
    Mar 12 at 12:02











  • Update fancyhdr; the current version is 2019/01/31 v3.10

    – egreg
    Mar 12 at 12:14











  • @egreg yes, the new version of fancyhdr has a f@nch@ifundefined macro which handles both undefined and relax, thanks. But anyway, is there any purpose to set chapter to relax instead of undefined in titlesec?

    – bodqhrohro
    Mar 12 at 12:31











  • @bodqhrohro That should be asked to the package maintainer.

    – egreg
    Mar 12 at 13:06














0












0








0








MWE is pretty simple:



documentclass[twoside]{article}
%usepackage{titlesec}
usepackage{fancyhdr}
begin{document}
pagestyle{fancy}
section{tist1}
subsection{a}
newpage
subsection{b}
end{document}


On the second page, there is the subsection name on the left and the section name on the right.



Now, uncomment the titlesec import, and the behaviour changes: the section name on the left and nothing (actually, a fantom of non-existent chapter name) on the right.



It happens because titlesec redefines chapter as relax, though normally it's undefined in article class. The fancyhdr packages has a following check:



ifxchapter@undefined


It fails, and marks are defined as in classes that have chapters. I can work it around with



letchapterundefined


after usepackage{titlesec}, or by explicitly redefining sectionmark/subsectionmark after pagestyle{fancy}. But why should I? Is this a bug in titlesec, or setting chapter to relax has some purpose?



UPD:



 *File List*
article.cls 2018/09/03 v1.4i Standard LaTeX document class
size10.clo 2018/09/03 v1.4i Standard LaTeX file (size option)
titlesec.sty 2016/03/21 v2.10.2 Sectioning titles
fancyhdr.sty 2017/06/30 v3.9a Extensive control of page headers and footers
***********









share|improve this question
















MWE is pretty simple:



documentclass[twoside]{article}
%usepackage{titlesec}
usepackage{fancyhdr}
begin{document}
pagestyle{fancy}
section{tist1}
subsection{a}
newpage
subsection{b}
end{document}


On the second page, there is the subsection name on the left and the section name on the right.



Now, uncomment the titlesec import, and the behaviour changes: the section name on the left and nothing (actually, a fantom of non-existent chapter name) on the right.



It happens because titlesec redefines chapter as relax, though normally it's undefined in article class. The fancyhdr packages has a following check:



ifxchapter@undefined


It fails, and marks are defined as in classes that have chapters. I can work it around with



letchapterundefined


after usepackage{titlesec}, or by explicitly redefining sectionmark/subsectionmark after pagestyle{fancy}. But why should I? Is this a bug in titlesec, or setting chapter to relax has some purpose?



UPD:



 *File List*
article.cls 2018/09/03 v1.4i Standard LaTeX document class
size10.clo 2018/09/03 v1.4i Standard LaTeX file (size option)
titlesec.sty 2016/03/21 v2.10.2 Sectioning titles
fancyhdr.sty 2017/06/30 v3.9a Extensive control of page headers and footers
***********






fancyhdr titlesec article






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 12 at 12:00







bodqhrohro

















asked Mar 12 at 1:15









bodqhrohrobodqhrohro

24816




24816













  • What versions of the packages are you using? (Put listfiles before documentclass and report the output here.) I get identical output with or without titlesec.

    – Alan Munn
    Mar 12 at 2:54













  • @AlanMunn added to the post.

    – bodqhrohro
    Mar 12 at 12:02











  • Update fancyhdr; the current version is 2019/01/31 v3.10

    – egreg
    Mar 12 at 12:14











  • @egreg yes, the new version of fancyhdr has a f@nch@ifundefined macro which handles both undefined and relax, thanks. But anyway, is there any purpose to set chapter to relax instead of undefined in titlesec?

    – bodqhrohro
    Mar 12 at 12:31











  • @bodqhrohro That should be asked to the package maintainer.

    – egreg
    Mar 12 at 13:06



















  • What versions of the packages are you using? (Put listfiles before documentclass and report the output here.) I get identical output with or without titlesec.

    – Alan Munn
    Mar 12 at 2:54













  • @AlanMunn added to the post.

    – bodqhrohro
    Mar 12 at 12:02











  • Update fancyhdr; the current version is 2019/01/31 v3.10

    – egreg
    Mar 12 at 12:14











  • @egreg yes, the new version of fancyhdr has a f@nch@ifundefined macro which handles both undefined and relax, thanks. But anyway, is there any purpose to set chapter to relax instead of undefined in titlesec?

    – bodqhrohro
    Mar 12 at 12:31











  • @bodqhrohro That should be asked to the package maintainer.

    – egreg
    Mar 12 at 13:06

















What versions of the packages are you using? (Put listfiles before documentclass and report the output here.) I get identical output with or without titlesec.

– Alan Munn
Mar 12 at 2:54







What versions of the packages are you using? (Put listfiles before documentclass and report the output here.) I get identical output with or without titlesec.

– Alan Munn
Mar 12 at 2:54















@AlanMunn added to the post.

– bodqhrohro
Mar 12 at 12:02





@AlanMunn added to the post.

– bodqhrohro
Mar 12 at 12:02













Update fancyhdr; the current version is 2019/01/31 v3.10

– egreg
Mar 12 at 12:14





Update fancyhdr; the current version is 2019/01/31 v3.10

– egreg
Mar 12 at 12:14













@egreg yes, the new version of fancyhdr has a f@nch@ifundefined macro which handles both undefined and relax, thanks. But anyway, is there any purpose to set chapter to relax instead of undefined in titlesec?

– bodqhrohro
Mar 12 at 12:31





@egreg yes, the new version of fancyhdr has a f@nch@ifundefined macro which handles both undefined and relax, thanks. But anyway, is there any purpose to set chapter to relax instead of undefined in titlesec?

– bodqhrohro
Mar 12 at 12:31













@bodqhrohro That should be asked to the package maintainer.

– egreg
Mar 12 at 13:06





@bodqhrohro That should be asked to the package maintainer.

– egreg
Mar 12 at 13:06










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


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f479007%2ftitlesec-makes-fancyhdr-mistreating-the-document-class%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














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f479007%2ftitlesec-makes-fancyhdr-mistreating-the-document-class%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

How to change which sound is reproduced for terminal bell?

Can I use Tabulator js library in my java Spring + Thymeleaf project?

Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents