public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Deri <deri@chuzzlewit.myzen.co.uk>
Cc: linux-man@vger.kernel.org, branden@debian.org
Subject: Re: Bogus index in man-pages book from other projects
Date: Tue, 12 Mar 2024 17:20:06 +0100	[thread overview]
Message-ID: <ZfCAtl5Q-F2uPJM4@debian> (raw)
In-Reply-To: <ZfB52IQowBB9zVU7@debian>

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

On Tue, Mar 12, 2024 at 04:50:47PM +0100, Alejandro Colomar wrote:
> 	alx@debian:~/src/shadow/shadow/build/man/ru$ tail man1/gpasswd.1
> 	содержит защищаемую информацию о группах
> 	.RE
> 	.SH "СМОТРИТЕ ТАКЖЕ"
> 	.PP
> 	\fBnewgrp\fR(1),
> 	\fBgroupadd\fR(8),
> 	\fBgroupdel\fR(8),
> 	\fBgroupmod\fR(8),
> 	\fBgrpck\fR(8),
> 	\fBgroup\fR(5), \fBgshadow\fR(5)\&.
> 
> So it might be due to having two references in the same line.  I suspect
> maybe the updated regex has some issues?

Ahh, I tought there was a group(5) page in shadow, but there isn't.  And
since you only parse that pattern at the begining of a line, it didn't
try the second one.  Let's ignore these small and rare glitches, I guess.

Cheers,
Alex

-- 
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.

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

      reply	other threads:[~2024-03-12 16:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-09 16:21 Bogus index in man-pages book from other projects Alejandro Colomar
2024-03-12 12:47 ` Deri
2024-03-12 14:12   ` Alejandro Colomar
2024-03-12 15:15     ` G. Branden Robinson
2024-03-12 18:25       ` Deri
2024-03-12 20:49         ` G. Branden Robinson
2024-03-12 15:39     ` Deri
     [not found]     ` <1873292.UaS1mDKzQr@pip>
2024-03-12 15:50       ` Alejandro Colomar
2024-03-12 16:20         ` Alejandro Colomar [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=ZfCAtl5Q-F2uPJM4@debian \
    --to=alx@kernel.org \
    --cc=branden@debian.org \
    --cc=deri@chuzzlewit.myzen.co.uk \
    --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