From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] treewide: Add \noindent where necessary
Date: Sun, 4 Sep 2016 08:04:28 -0700 [thread overview]
Message-ID: <20160904150428.GV3663@linux.vnet.ibm.com> (raw)
In-Reply-To: <269e7880-07e9-43f6-70c9-b1d321b3e442@gmail.com>
On Sun, Sep 04, 2016 at 11:53:53PM +0900, Akira Yokosawa wrote:
> On 2016/09/04 02:58:21 -0700, Paul E. McKenney wrote:
> > On Sun, Sep 04, 2016 at 08:44:27AM +0900, Akira Yokosawa wrote:
> >> >From e11254e95c6d33eaf999a1e1c4831af2e141fb91 Mon Sep 17 00:00:00 2001
> >> From: Akira Yokosawa <akiyks@gmail.com>
> >> Date: Sun, 4 Sep 2016 08:01:50 +0900
> >> Subject: [PATCH] treewide: Add \noindent where necessary
> >>
> >> Since commit 213f584cd55b ("Add a few epigraphs") and following
> >> commits, implicit no-indentation of first paragraph of a Chapter
> >> has been lost.
> >>
> >> This commit adds explicit "\noindent" after \epigraph{}s.
> >>
> >> It also adds "\noindent" where some environment is used just
> >> after "\section{}", "subsection{}", or "subsubsection{}.
> >>
> >> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
> >
> > Good eyes! I honestly had not noticed.
>
> Well, now I know why. In the two-column layout, there was no change
> in indentation of the first paragraph of a chapter...
> I suppose you mostly see the two-column layout so it's natural you
> didn't see any difference.
>
> I don't know why, but when you specify "twocolumn" option to the "book"
> documentclass, the first paragraph of a chapter *is* indented.
>
> I noticed the difference in perfbook-1c.pdf first, and wrongly assumed
> it was also the case in two-column layout.
>
> Sorry for my confusion.
>
> I have no idea if the behavior of twocolumn option is intended or not.
>
> So the addition of epigraphs actually made the indentation consistent
> in both two-column and one-column layout.
>
> I can resubmit a patch that only changes at the first paragraphs of
> sections.
>
> >
> > But wouldn't it make more sense to fix the epigraph package? For that
> > matter, what exactly are the rules regarding epigraphs and indentation
> > of first paragraphs and chapters?
>
> \epigraph{} command does have this side-effect in one-column layout.
> I found several examples where people use \noindent after \epigraph{},
> but there seems to be no strong rules here.
>
> So just doing consistently can be said of as the rule.
> It's the editor's call, I think.
When there is no clear rule, as in this case, we should let the tool
(in this case, LaTeX) be our guide. ;-)
Thanx, Paul
prev parent reply other threads:[~2016-09-04 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 23:44 [PATCH] treewide: Add \noindent where necessary Akira Yokosawa
2016-09-04 9:58 ` Paul E. McKenney
2016-09-04 14:53 ` Akira Yokosawa
2016-09-04 15:04 ` Paul E. McKenney [this message]
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=20160904150428.GV3663@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akiyks@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox