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?










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
    1 hour ago


















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?










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
    1 hour ago
















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?










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?







fancyhdr titlesec article






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 2 hours ago









bodqhrohrobodqhrohro

1083




1083













  • 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
    1 hour ago





















  • 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
    1 hour ago



















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
1 hour ago







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
1 hour ago












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

A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

Calculate evaluation metrics using cross_val_predict sklearn

Insert data from modal to MySQL (multiple modal on website)