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:46:21 +0100 [thread overview]
Message-ID: <ZUKA3XWzystXKgmh@debian> (raw)
In-Reply-To: <ZUJaZLJyT5jFlHmX@meinfjell.helgefjelltest.de>
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
Hi Helge,
On Wed, Nov 01, 2023 at 02:02:12PM +0000, Helge Kreutzmann wrote:
> Without further ado, the following was found:
>
> Issue 1: alphabetic?
> Issue 2: multiple cases → both cases?
Depending on the locale, more than 2 are possible, AFAIK, so multiple
would be more accurate in that context, I think.
Cheers,
Alex
>
> "If case-independent matching is specified, the effect is much as if all case "
> "distinctions had vanished from the alphabet. When an alphabetic that exists "
> "in multiple cases appears as an ordinary character outside a bracket "
> "expression, it is effectively transformed into a bracket expression "
> "containing both cases, for example, \\[aq]x\\[aq] becomes \"I<[xX]>\". When "
> "it appears inside a bracket expression, all case counterparts of it are "
> "added to the bracket expression, so that, for example, \"I<[x]>\" becomes "
> "\"I<[xX]>\" and \"I<[\\[ha]x]>\" becomes \"I<[\\[ha]xX]>\"."
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-11-01 16:46 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:46 ` 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:54 ` 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=ZUKA3XWzystXKgmh@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.