Thanks to @Bernard comment, adding \raggedbottom
fixed this warning. While searching it, I found the questions:
- \flushbottom vs \raggedbottom)
- Do I have to care about bad boxes?
- badness messages when changing from report to book class
- \raggedbottom in book. Is it right way?
- Restore default \raggedbottom footnote behaviour when using one of the Koma script classes
Also filling that specific page with text fixed the warning. Basically somehow the contents of the page where being pushed to the next page letting a big whole on the original page.
On this version the warning is fixed by filling up text:
% ----------------------------------------------------------
\chapter[Nullam elementum urna vel imperdiet sodales elit ipsum]{Nullam elementum urna vel imperdiet sodales elit ipsum pharetra ligula
ac pretium ante justo a nulla curabitur tristique arcu eu metus}
% ----------------------------------------------------------
\showfont
\section[Some encoding tests]{\showfont}
1. How to display the font size in use in the final output,
2. How to display the font size in use in the final output,
3. How to display the font size in use in the final output,
4. How to display the font size in use in the final output,
5. How to display the font size in use in the final output,
6. How to display the font size in use in the final output,
7. How to display the font size in use in the final output,
8. How to display the font size in use in the final output,
9. How to display the font size in use in the final output,
10. How to display the font size in use in the final output,
11. How to display the font size in use in the final output,
12. How to display the font size in use in the final output,
\subsection{\showfont}
1. How to display the font size in use in the final output,
2. How to display the font size in use in the final output,
3. How to display the font size in use in the final output,
4. How to display the font size in use in the final output,
5. How to display the font size in use in the final output,
6. How to display the font size in use in the final output,
7. How to display the font size in use in the final output,
8. How to display the font size in use in the final output,
9. How to display the font size in use in the final output,
10. How to display the font size in use in the final output,
11. How to display the font size in use in the final output,
12. How to display the font size in use in the final output,
\subsubsection{\showfont}
1. How to display the font size in use in the final output,
2. How to display the font size in use in the final output,
3. How to display the font size in use in the final output,
4. How to display the font size in use in the final output,
5. How to display the font size in use in the final output,
6. How to display the font size in use in the final output,
7. How to display the font size in use in the final output,
8. How to display the font size in use in the final output,
9. How to display the font size in use in the final output,
10. How to display the font size in use in the final output,
11. How to display the font size in use in the final output,
12. How to display the font size in use in the final output,
\subsubsubsection{\showfont}
1. How to display the font size in use in the final output,
2. How to display the font size in use in the final output,
3. How to display the font size in use in the final output,
4. How to display the font size in use in the final output,
5. How to display the font size in use in the final output,
6. How to display the font size in use in the final output,
7. How to display the font size in use in the final output,
8. How to display the font size in use in the final output,
9. How to display the font size in use in the final output,
10. How to display the font size in use in the final output,
11. How to display the font size in use in the final output,
12. How to display the font size in use in the final output,
Lipsum me [55-57]
![enter image description here](https://i.stack.imgur.com/x7Ijh.png)
I would prefer this alternative over disabling the pages bottom justifications with \raggedbottom
. I believe the problem was caused by pilling up empty of sections as showed on question end, which somehow pushed all the empty sections to the next page creating the whole at the first page bottom:
% ----------------------------------------------------------
\chapter[Nullam elementum urna vel imperdiet sodales elit ipsum]{Nullam
elementum urna vel imperdiet sodales elit ipsum pharetra ligula
ac pretium ante justo a nulla curabitur tristique arcu eu metus}
% ----------------------------------------------------------
\showfont
\section[Some encoding tests]{\showfont}
\subsection{\showfont}
\subsubsection{\showfont}
\subsubsubsection{\showfont}
![enter image description here](https://i.stack.imgur.com/eKx12.png)
The solution to the above case is to manually insert a \newpage
command, on the page which is issuing the warning. On this case the document would be like:
% ----------------------------------------------------------
\chapter[Nullam elementum urna vel imperdiet sodales elit ipsum]{Nullam
elementum urna vel imperdiet sodales elit ipsum pharetra ligula
ac pretium ante justo a nulla curabitur tristique arcu eu metus}
% ----------------------------------------------------------
\showfont
\newpage
\section[Some encoding tests]{\showfont}
\subsection{\showfont}
\subsubsection{\showfont}
\subsubsubsection{\showfont}
Just notice this last example only works if attached to my main document. When this is reproduced alone, no empty page is throw down:
![enter image description here](https://i.stack.imgur.com/tcHIT.png)
This is probably due some other setting somewhere embedded on my main document class.
Best Answer
This is a perfect example of where
-wall
can bite you with ChkTeX. This warning is simply a check for any command which is doesn't start with a letter or a space. So ) counts as that. Personally, I find this a bit silly, but I'm reluctant to completely delete it in case some people find it useful. From the documentation:Here it's easy to see how a novice could make that mistake, and why this might be a useful warning. However, it's not the type of mistake that I have made for a long time and it causes other problems like the one you mention. I suppose I could special case
\(
and\)
, but I'm not sure that would actually be much help. Eventually you'll need to use\.
or\:
or ...What I recommend is adding to your chktexrc all the warnings that you are interested in, or even start with
-wall
and remove the ones that aren't useful to you. Your life will be much better. At least to the extent that a simple program like ChkTeX can make it better.:)
You can also add your own simple warnings (based on regular expressions).Full Disclosure: I'm the current maintainer of ChkTeX.