From: Akira Yokosawa <akiyks@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: perfbook@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: [PATCH -perfbook 0/4] Address potential widowing of headings
Date: Wed, 8 Dec 2021 16:37:26 +0900 [thread overview]
Message-ID: <4350078f-4054-cb28-157b-305d6df087ea@gmail.com> (raw)
Hi Paul,
There was some confusion on my side WRT undesired page/column
breaks.
While testing the added checks in cleverefcheck.pl, I saw too
many potential such cases flagged. This made me do some tests
to reproduce unfortunate page/column breaks.
There are three such patterns I have confirmed.
1. "listing" environment (with contents of fancyvrb) next to proper
LaTeX headings (\chapter, \section, \subsection, etc.)
2. Any environment (not necessarily float) next to QQA heading
of "Answer:"
3. Any environment (not necessarily float) next to epigraph
This means commit f106e0e6dc43 ("defer/rcuusage: Move float objects
away of section titles") has no merit. It is safe to revert it if
you'd like. I was confused by patterns 2 and 3 and thought that
floating objects can cause undesired breaks.
Patches 1/4--3/4 add tests in cleverefcheck.pl that check patterns
listed above respectively.
Patch 4/4 fixes problematic places flagged by the updated script.
Feel free to wordsmith the leading phrases I added in QQAs.
Thanks, Akira
--
Akira Yokosawa (4):
cleverefcheck.pl: Add test of listing next to heading
cleverefcheck.pl: Add test of \begin{...} at head of QQA
cleverefcheck.pl: Add test of \begin{...} next to epigraph
treewide: Address potential widowing of headings
appendix/questions/after.tex | 4 +++
datastruct/datastruct.tex | 14 +++++-----
defer/refcnt.tex | 24 ++++++++---------
formal/axiomatic.tex | 22 +++++++--------
locking/locking-existence.tex | 9 ++++---
memorder/memorder.tex | 6 ++---
utilities/cleverefcheck.pl | 50 +++++++++++++++++++++++++++++++++++
7 files changed, 92 insertions(+), 37 deletions(-)
base-commit: f106e0e6dc436683bb119dd8992c6f173994d182
--
2.17.1
next reply other threads:[~2021-12-08 7:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 7:37 Akira Yokosawa [this message]
2021-12-08 7:39 ` [PATCH -perfbook 1/4] cleverefcheck.pl: Add test of listing next to heading Akira Yokosawa
2021-12-08 7:41 ` [PATCH -perfbook 2/4] cleverefcheck.pl: Add test of \begin{...} at head of QQA Akira Yokosawa
2021-12-08 7:49 ` [PATCH -perfbook 3/4] cleverefcheck.pl: Add test of \begin{...} next to epigraph Akira Yokosawa
2021-12-08 7:52 ` [PATCH -perfbook 4/4] treewide: Address potential widowing of headings Akira Yokosawa
2021-12-08 19:55 ` [PATCH -perfbook 0/4] " Paul E. McKenney
2021-12-08 22:20 ` Akira Yokosawa
2021-12-08 23:58 ` Paul E. McKenney
2021-12-09 0:03 ` Akira Yokosawa
2021-12-09 6:28 ` Zhouyi Zhou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4350078f-4054-cb28-157b-305d6df087ea@gmail.com \
--to=akiyks@gmail.com \
--cc=paulmck@kernel.org \
--cc=perfbook@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.