From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Tom Schwindl <schwindl@posteo.de>
Cc: наб <nabijaczleweli@nabijaczleweli.xyz>,
"Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>,
linux-man@vger.kernel.org
Subject: Re: [PATCH] regex.3: "([^...])" is not an end of sentence
Date: Sat, 8 Jul 2023 08:52:40 -0500 [thread overview]
Message-ID: <20230708135240.b2wmsbatluv2keko@illithid> (raw)
In-Reply-To: <CTWPJBPKXRDW.3KYB31EMTA2B5@morphine>
[-- Attachment #1: Type: text/plain, Size: 2378 bytes --]
Hi Tom,
At 2023-07-08T10:10:01+0000, Tom Schwindl wrote:
> On Sat Jul 8, 2023 at 5:11 AM CEST, наб wrote:
> > diff --git a/man3/regex.3 b/man3/regex.3
> > index 13e540b22..630c0369d 100644
> > --- a/man3/regex.3
> > +++ b/man3/regex.3
> > @@ -109,7 +109,7 @@ .SS Compilation
> > Match-any-character operators don't match a newline.
> > .IP
> > A nonmatching list
> > -.RB ( [\[ha]...] )
> > +.RB ( [\[ha]...\&] )
> > not containing a newline does not match a newline.
> > .IP
> > Match-beginning-of-line operator
>
> I cannot reproduce this on my system; only one space is rendered.
You may have the inter-sentence space amount configured to zero.[1]
I get the extra space with all of DWB 3.3 nroff, Heirloom Doctools
nroff, mandoc, and groff.
$ printf '.ll 100n\nA nonmatching list\n([\(ha...])\nnot containing a newline does not match a newline.\n' | groff -Tascii | cat -s
A nonmatching list ([^...]) not containing a newline does not match a newline.
[cd DWB][2]
$ printf '.ll 100n\nA nonmatching list\n([\(ha...])\nnot containing a newline does not match a newline.\n' | DWBHOME=. ./bin/nroff | cat -s
A nonmatching list ([...]) not containing a newline does not match a newline.
[cd Heirloom]
$ printf '.ll 100n\nA nonmatching list\n([\(ha...])\nnot containing a newline does not match a newline.\n' | ./bin/nroff | cat -s
A nonmatching list ([^...]) not containing a newline does not match a newline.
$ printf '.ll 100n\nA nonmatching list\n([\(ha...])\nnot containing a newline does not match a newline.\n' | mandoc | cat -s
() ()
A nonmatching list ([^...]) not containing a newline does not match a newline.
()
Regards,
Branden
[1] Adding the following line to your man.local file in a groff
installation would do the trick.
.ss 12 0
In groff, this is also the default for several "groff locales",
including "cs", "de", "fr", "sv", and, new in groff 1.23.0, "it".
[2] I respelled the \[ha] special character escape sequence in legacy
form for greater portability, but the "ha" special character _name_
is not recognized by DWB troff (which has not been maintained for
about 30 years).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-07-08 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-08 3:11 [PATCH] regex.3: "([^...])" is not an end of sentence наб
2023-07-08 10:10 ` Tom Schwindl
2023-07-08 13:52 ` G. Branden Robinson [this message]
2023-07-08 17:49 ` 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=20230708135240.b2wmsbatluv2keko@illithid \
--to=g.branden.robinson@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
--cc=schwindl@posteo.de \
/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