public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH] circleq.3, list.3, slist.3, stailq.3, tailq.3: Improve readability, especially in SYNOPSIS
Date: Tue, 5 Jan 2021 13:00:55 +0100	[thread overview]
Message-ID: <ae31daa2-a44b-2e79-1a70-a95428b7e231@gmail.com> (raw)
In-Reply-To: <20210104224515.140403-1-alx.manpages@gmail.com>

Hello Alex,

On 1/4/21 11:45 PM, Alejandro Colomar wrote:
> - Group macros by kinds.

Looks good.

> - Align so that it's easiest to distinguish differences>   between related macros.

The problem with this is that it doesn't render well in PDF [1],
I think. The spaces render small in PDF, and the alignment looks
random. Better to use the same indent for all continuations.
Could you amend and resend please.

> - Fix minor typos.

Okay.

> - Remove redundant text ('The macro xxx() ...')>   The first paragraph already says that these are macros.

Okay.

> - Fit lines into 78 columns.

Okay.

> I noticed a bug which should be fixed next:
> CIRCLEQ_LOOP_*() return a 'struct TYPE *'.

Okay.

> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
> ---
> 
> Hi Michael,
> 
> Here's my attempt of making queue.3 pages more readable.
> I think it's quite nicer now.

Agreed.

> But please, review it, because I may have introduced a few bugs
> while moving the text around.

At aa quick glance, it looks okay to me.

> Also, if you feel something could be nicer, please tell me.
> 
> BTW, it's been the first time I use Vim for something not trivial,
> and I quite liked it.
> I think I'll stop using Gedit for a while :-)

Good choice :-).

[...]

Cheers,

Michael

[1]
Usage: pdfman <man-page.n>

function pdfman {
    man -Tps -l $1 > /tmp/$(basename $1).$$.ps
    ps2pdf /tmp/$(basename $1).$$.ps $1.pdf
    evince $1.pdf
}

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

  parent reply	other threads:[~2021-01-05 12:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-04 22:45 [PATCH] circleq.3, list.3, slist.3, stailq.3, tailq.3: Improve readability, especially in SYNOPSIS Alejandro Colomar
2021-01-04 23:05 ` Alejandro Colomar (man-pages)
2021-01-05 13:25   ` Michael Kerrisk (man-pages)
2021-01-05 22:39     ` [PATCH v2] " Alejandro Colomar
2021-01-05 22:53       ` Alejandro Colomar (man-pages)
2021-01-06 12:54         ` Michael Kerrisk (man-pages)
2021-01-06 11:12       ` Michael Kerrisk (man-pages)
2021-01-05 12:00 ` Michael Kerrisk (man-pages) [this message]
2021-01-05 14:05   ` pdfman Alejandro Colomar (man-pages)
2021-01-06 11:09     ` pdfman Michael Kerrisk (man-pages)
2024-11-03  5:31       ` pdfman Alejandro Colomar

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=ae31daa2-a44b-2e79-1a70-a95428b7e231@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=alx.manpages@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