All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page regex.7
Date: Wed, 1 Nov 2023 17:54:32 +0100	[thread overview]
Message-ID: <ZUKCyYniLLfYL4NY@debian> (raw)
In-Reply-To: <ZUJaZKpi3x1c29CQ@meinfjell.helgefjelltest.de>

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

On Wed, Nov 01, 2023 at 02:02:12PM +0000, Helge Kreutzmann wrote:
> Without further ado, the following was found:
> 
> Issue:    I<egrep> → B<egrep>(1)

Fixed:
<https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=f43a9ed0f80c18ca8a033883d726bfa78fa5c7d6>

Thanks,
Alex

> 
> "Regular expressions (\"RE\"s), as defined in POSIX.2, come in two forms: "
> "modern REs (roughly those of I<egrep>; POSIX.2 calls these \"extended\" "
> "REs)  and obsolete REs (roughly those of B<ed>(1); POSIX.2 \"basic\" REs).  "
> "Obsolete REs mostly exist for backward compatibility in some old programs; "
> "they will be discussed at the end.  POSIX.2 leaves some aspects of RE syntax "
> "and semantics open; \"\\*(dg\" marks decisions on these aspects that may not "
> "be fully portable to other POSIX.2 implementations."

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

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

  reply	other threads:[~2023-11-01 16:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01 14:02 Issue in man page regex.7 Helge Kreutzmann
2023-11-01 16:54 ` Alejandro Colomar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-17 10:46 Helge Kreutzmann
2024-11-17 11:28 ` Alejandro Colomar
2023-11-01 14:02 Helge Kreutzmann
2023-11-01 16:46 ` 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=ZUKCyYniLLfYL4NY@debian \
    --to=alx@kernel.org \
    --cc=debian@helgefjell.de \
    --cc=linux-man@vger.kernel.org \
    --cc=mario.blaettermann@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.