public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Tom Schwindl" <schwindl@posteo.de>
To: наб <nabijaczleweli@nabijaczleweli.xyz>,
	"Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: <linux-man@vger.kernel.org>
Subject: Re: [PATCH] regex.3: "([^...])" is not an end of sentence
Date: Sat, 08 Jul 2023 10:10:01 +0000	[thread overview]
Message-ID: <CTWPJBPKXRDW.3KYB31EMTA2B5@morphine> (raw)
In-Reply-To: <cndmjlonfcjogtpy7fsrtouncxn335fu52u35poylcwtxihztd@hq2fb3sqvizd>

Hi,

On Sat Jul 8, 2023 at 5:11 AM CEST, наб wrote:
> Caused a double space before "not".
>
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
> ---
>  man3/regex.3 | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> 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.
After applying the patch, there are no visible changes. So if there really are
issues for some people, your patch at least doesn't break anything.

-- 
Best Regards,
Tom Schwindl

  reply	other threads:[~2023-07-08 10:11 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 [this message]
2023-07-08 13:52   ` G. Branden Robinson
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=CTWPJBPKXRDW.3KYB31EMTA2B5@morphine \
    --to=schwindl@posteo.de \
    --cc=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=nabijaczleweli@nabijaczleweli.xyz \
    /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