From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <colomar.6.4.3@gmail.com>,
"Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>,
"G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: .RS
Date: Fri, 13 Nov 2020 11:27:04 +0100 [thread overview]
Message-ID: <9197f3ab-582f-7f4a-5e03-afdf7c10db99@gmail.com> (raw)
In-Reply-To: <a1705306-0d38-522a-e903-5e63aafdb4eb@gmail.com>
Hi ALex,
On 11/13/20 11:15 AM, Alejandro Colomar wrote:
>
> Hi Michael,
>
> On 11/13/20 9:52 AM, Michael Kerrisk (man-pages) wrote:
> [...]
>>> Do you know why is that?
>>
>> Hmmm -- I don't know. I was going to ask, doesn't s/>RS 4/.RS +4n/
>> fix the problem? But I see that it does not.
>
> No; I tried many things, but I didn't find a solution.
> So, we'll have to keep using .in, right?
It looks that way to me.
>> By the way, your comments (\") actually cause the rendered
>> output to change, as far as I can see! In particular,
>> the \" on the final .RE leads to some strangeness:
>>
>> [[
>> .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
>> .EX
>> I am indented 4n from normal paragraphs!!!
>> .EE
>> .RE \" nom
>> .\"""""""""""""""""""""""""""""""""""""""""""
>> .PP
>> Augue interdum velit euismod in pellentesque.
>> ]]
>>
>> Gives:
>>
>> [[
>> * 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.
>>
>> I am indented 6n from normal paragraphs.
>>
>> * Augue interdum velit euismod in pellentesque. Tristique senec‐
>> tus et netus et malesuada fames ac turpis egestas. Gravida arcu
>> ac tortor dignissim convallis.
>>
>> I am indented 4n from normal paragraphs!!!
>>
>> Augue interdum velit euismod in pellentesque.
>> ]]
>>
>> No indent at all on the final line!
>
> Hmm that's weird. I added the comments in the email, so I didn't test them.
Branden could not reproduce, and now I can't either. So I must have
messed up. Ignore my comments please.
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-11-13 10:27 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 ` .RS Alejandro Colomar (man-pages)
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 ` Michael Kerrisk (man-pages) [this message]
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=9197f3ab-582f-7f4a-5e03-afdf7c10db99@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=colomar.6.4.3@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@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