public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Jakub Wilk <jwilk@jwilk.net>,
	linux-man@vger.kernel.org,
	Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH] mmap.2: ffix
Date: Mon, 28 Feb 2022 16:11:07 +0100	[thread overview]
Message-ID: <2525645b-73ff-67a4-b82a-511f6b904d23@gmail.com> (raw)
In-Reply-To: <20220228131812.3mslwzg45gzyixb4@localhost.localdomain>

Hi, Branden!

On 2/28/22 14:18, G. Branden Robinson wrote:
> Hi, Alex!
> 
>> Then, should I report a bug in groff?
>>
>> I could reproduce the incorrect formatted output with
>> GNU groff version 1.23.0.rc1.1931-35c9b
> 
> I didn't even see the run-on bold at first; I was looking for
> breaking/spacing problems.
> 
> No, groff is behaving correctly as I understand it (and consistently
> with Heirloom Doctools troff--I didn't fire up the PDP-11 simulator for
> this).
> 

Ahh, I thought I knew \c.  It seems I didn't.  I thought it was as
simple as "remove any spaces between this line and the next, but
consider them separate in terms of formatting".  But it continues
formatting too.

$ cat c.man
.TH \ec 7 $TODAY alx experiments
.SH NAME
\ec \- experiment
.SH TEST
foo\c
.B bar\c
baz
$ man ./c.man | cat
\c(7)                      experiments                     \c(7)

NAME
       \c - experiment

TEST
       foobarbaz

alx                          $TODAY                        \c(7)


"barbaz" is bold.  I thought only "bar" would be bold.


>> Okay, I'll fix that.
> 
> I'm looking forward to seeing a PDF-hyperlinked rendition of the next
> Linux man-pages release, as I've done with the 384-page
> "groff-man-pages.pdf".  :)

Might be :)
Maybe you release groff-1.23 before we (I?) release man-pages-next (if
it's me releasing, I may delay it until linux-6.0).  If that's the case,
and most distros ship it by that time, I may introduce .MR.

BTW, have you seen the changes I introduced this week?  I'd like to know
your opinion about them, if you have one, since there are quite a lot
of them:

$ git shortlog  --since 'last week' | wc -l
499


They reduce to 3 kinds of changes:

- Add LIBRARY section.  Similar in FreeBSD and NetBSD,
  but I used lowercase for everything but the first letter.

- Remove most of the license texts (all except those that don't have a
  SPDX license tag), and replace them by the license tag.  Add the
  licenses to <LICENSES/>.

- Move types out of system_data_types to separate pages, that are
  much more manageable.  system_data_types(7) was becoming something
  huge like queue(3) once was.  I also wonder if we should inaugurate
  a new subsection of man3 (maybe 3types?).


Regards,
Alex


-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

      reply	other threads:[~2022-02-28 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12 10:39 [PATCH] mmap.2: ffix Jakub Wilk
2022-02-27 17:09 ` Alejandro Colomar
2022-02-27 18:57   ` G. Branden Robinson
2022-02-27 19:02     ` Alejandro Colomar (man-pages)
2022-02-28 13:18       ` G. Branden Robinson
2022-02-28 15:11         ` Alejandro Colomar (man-pages) [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=2525645b-73ff-67a4-b82a-511f6b904d23@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=g.branden.robinson@gmail.com \
    --cc=jwilk@jwilk.net \
    --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