public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Petr Vorel <pvorel@suse.cz>,
	linux-doc@vger.kernel.org,  man-pages@man7.org
Subject: Re: [PATCH v3 0/3] Documentation: Link man pages to https://man7.org/
Date: Fri, 16 Jan 2026 21:37:20 +0100	[thread overview]
Message-ID: <aWqg5XwPRXlzq4FI@devuan> (raw)
In-Reply-To: <87a4ydo1hf.fsf@trenco.lwn.net>

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

Hi Jon,

On Fri, Jan 16, 2026 at 11:29:16AM -0700, Jonathan Corbet wrote:
> Petr Vorel <pvorel@suse.cz> writes:
> 
> > Changes v1->v2:
> > * Remove `...` (italic) from non-existing man pages (Jonathan).
> > * Squash fix for sp_SP to following commit (Jonathan).
> > * Remove :manpage: also from fxyzzy(3) (non-existing man page).
> > * Add CSS for man page.
> >
> > Link to v2:
> > https://lore.kernel.org/linux-doc/20260111233534.183272-1-pvorel@suse.cz/
> >
> > Link to v1:
> > https://lore.kernel.org/linux-doc/20260109183012.114372-1-pvorel@suse.cz/
> >
> > Petr Vorel (3):
> >   Documentation: Remove :manpage: from non-existing man pages
> >   Documentation: Link man pages to https://man7.org/
> >   Documentation: CSS: Improve man page font
> >
> >  Documentation/conf.py                            |  3 +++
> >  Documentation/process/adding-syscalls.rst        | 16 ++++++++--------
> >  Documentation/sphinx-static/custom.css           |  8 +++++++-
> >  .../it_IT/process/adding-syscalls.rst            | 16 ++++++++--------
> >  .../sp_SP/process/adding-syscalls.rst            | 16 ++++++++--------
> >  5 files changed, 34 insertions(+), 25 deletions(-)
> 
> I have applied this set, thanks.
> 
> Even nicer, of course, would be to have automarkup recognize man-page
> references and add the links automatically so we wouldn't need the
> :manpage: noise.  Something for another day, I guess...

We had some old scripts within the manual pages, which did something
similar, and they had false positives.  For example, 'exit(1)' is
ambiguous, since a script can't know if it refers to calling exit(3)
with value 1, or if it's a reference to the shell builtin.

I'd recommend being cautious about it.  :)


Have a lovely night!
Alex

-- 
<https://www.alejandro-colomar.es>

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

  reply	other threads:[~2026-01-16 20:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-13 11:36 [PATCH v3 0/3] Documentation: Link man pages to https://man7.org/ Petr Vorel
2026-01-13 11:36 ` [PATCH v3 1/3] Documentation: Remove :manpage: from non-existing man pages Petr Vorel
2026-01-13 11:36 ` [PATCH v3 2/3] Documentation: Link man pages to https://man7.org/ Petr Vorel
2026-01-13 11:36 ` [PATCH v3 3/3] Documentation: CSS: Improve man page font Petr Vorel
2026-01-13 22:45   ` Bagas Sanjaya
2026-01-14  8:36     ` Petr Vorel
2026-01-14 10:33       ` Bagas Sanjaya
2026-01-16 18:29 ` [PATCH v3 0/3] Documentation: Link man pages to https://man7.org/ Jonathan Corbet
2026-01-16 20:37   ` Alejandro Colomar [this message]
2026-01-20 10:51     ` Petr Vorel
2026-01-20 10:48   ` Petr Vorel

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=aWqg5XwPRXlzq4FI@devuan \
    --to=alx@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=man-pages@man7.org \
    --cc=pvorel@suse.cz \
    /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