linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
	"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, colomar.6.4.3@gmail.com
Subject: Re: .RS
Date: Thu, 12 Nov 2020 20:57:59 +0100	[thread overview]
Message-ID: <60a7fa20-d41e-12d9-a81e-558512a74f0c@gmail.com> (raw)
In-Reply-To: <1ae93b8f-c6e2-f11d-0844-a8cf702f933b@gmail.com>

Hi Branden and Michael,

Okay, after some testing:

* [.in 4] simply doesn't seem to work at all.
* [.RS 4] and [.RS +4n] seem to be equivalent.
* [.RS 4] is different (worse) than [.in +4n]
          in some very specific scenario:

[[
.IP * 2
Lorem ipsum dolor sit amet, consectetur adipiscing elit,
sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris
nisi ut aliquip ex ea commodo consequat.
.\""""""""""""""""""""""""""""""""""""""""""
.IP		\" Indent is 2n after this
.in +4n		\" Indent is 6n after this
.EX
I am indented 6n from normal paragraphs.
.EE
.in		\" Return to normal
.\"""""""""""""""""""""""""""""""""""""""""""
.IP *
Augue interdum velit euismod in pellentesque.
Tristique senectus et netus et malesuada fames ac turpis egestas.
Gravida arcu ac tortor dignissim convallis.
.\"""""""""""""""""""""""""""""""""""""""""""
.IP		\" Indent is 2n after this
.RS 4		\" Indent is _4n_ after this
.EX
I am indented 4n from normal paragraphs!!!
.EE
.RE		\" Return to normal
.\"""""""""""""""""""""""""""""""""""""""""""
]]

This happens in perf_event_open.2,
where [.in +4n] is used,
and when I changed it to [.RS/.RE] I saw this change in behavior.

Do you know why is that?

Thanks,

Alex

  reply	other threads:[~2020-11-12 19:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-11 14:22 .RS Alejandro Colomar (man-pages)
2020-11-11 15:09 ` .RS G. Branden Robinson
2020-11-11 15:34   ` .RS Alejandro Colomar (man-pages)
2020-11-12  7:09     ` .RS G. Branden Robinson
2020-11-12  9:49       ` .RS Alejandro Colomar (man-pages)
2020-11-12 19:57         ` Alejandro Colomar (man-pages) [this message]
2020-11-12 20:57           ` .RS Alejandro Colomar (man-pages)
2020-11-13  8:03             ` .RS G. Branden Robinson
2020-11-13  8:52           ` .RS Michael Kerrisk (man-pages)
     [not found]             ` <20201113093846.jzxlkw3o3pqkkr47@localhost.localdomain>
2020-11-13 10:02               ` .RS Michael Kerrisk (man-pages)
2020-11-13 10:15             ` .RS Alejandro Colomar
2020-11-13 10:27               ` .RS Michael Kerrisk (man-pages)
2020-11-13 10:34       ` .RS G. Branden Robinson

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=60a7fa20-d41e-12d9-a81e-558512a74f0c@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=colomar.6.4.3@gmail.com \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).