Linux Manual Pages development
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: "Dirk Müller" <dmueller@suse.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [BUG] typo in man2/readlink.2
Date: Wed, 15 Apr 2026 13:24:17 -0500	[thread overview]
Message-ID: <20260415182417.b6cvefbzk6ss3lmw@illithid> (raw)
In-Reply-To: <CAN6Ha9b5Tujw=sB5MwhLhnt1XJodmH1TOfeZWJk_VWnWE_smzg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]

Hi Dirk,

At 2026-04-15T20:12:59+0200, Dirk Müller wrote:
> Hi,
> 
> I noticed that man pages 6.17 release includes this in the Synopsis
> section of man -l man/man2/readlink.2:
> 
>       ssize_t readlink(size_t bufsiz;
>                        const char *restrict path,
>                        char buf[restrict bufsiz], size_t bufsiz);
> 
> I believe this is a typo and it should be:
> 
>       ssize_t readlink(const char *restrict path,
>                        char buf[restrict bufsiz], size_t bufsiz);
> 
> instead.

This is something of a FAQ on this mailing list.

https://lore.kernel.org/linux-man/adupQhfJQ7kws17U@debian/

It's a GCC syntax extension.

https://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html

> Sorry for not including a patch, but I am not sufficiently skilled at
> editing man page sources :-)

Have you seen groff_man_style(7)?

https://man7.org/linux/man-pages/man7/groff_man_style.7.html

</shameless self-plug>

(Unfortunately Michael hasn't updated to groff 1.24.{0,1} yet.)

Regards,
Branden

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-04-15 18:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-15 18:12 [BUG] typo in man2/readlink.2 Dirk Müller
2026-04-15 18:24 ` G. Branden Robinson [this message]
2026-04-15 20:00   ` Dirk Müller
2026-04-15 21:36     ` Alejandro Colomar
2026-04-15 21:57       ` Dirk Müller
2026-04-15 23:26         ` Alejandro Colomar
2026-04-17  6:41           ` Dirk Müller
2026-04-17 13:28             ` 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=20260415182417.b6cvefbzk6ss3lmw@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=dmueller@suse.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