all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Vincent Lefevre <vincent@vinc17.net>
Cc: Eli Zaretskii <eliz@gnu.org>, 58992@debbugs.gnu.org
Subject: bug#58992: 28.2; "lax space matching" no longer works
Date: Fri, 04 Nov 2022 12:38:14 +0100	[thread overview]
Message-ID: <87o7tnhrvd.fsf@igel.home> (raw)
In-Reply-To: <20221104101513.GM9807@zira.vinc17.org> (Vincent Lefevre's message of "Fri, 4 Nov 2022 11:15:13 +0100")

On Nov 04 2022, Vincent Lefevre wrote:

> Wow! This is really confusing! [:space:] is defined by POSIX,

Emacs regexps are _not_ defined by POSIX.

>     A character alternative can also specify named character classes
>     (*note Char Classes::).  This is a POSIX feature.  [...]

Did you read the referenced node?

‘[:space:]’
     This matches any character that has whitespace syntax (*note Syntax
     Class Table::).

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."





  reply	other threads:[~2022-11-04 11:38 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 16:53 bug#58992: 28.2; "lax space matching" no longer works Vincent Lefevre
2022-11-03 17:04 ` Eli Zaretskii
2022-11-03 17:21   ` Vincent Lefevre
2022-11-03 17:34     ` Vincent Lefevre
2022-11-03 18:05       ` Eli Zaretskii
2022-11-03 17:49     ` Gregory Heytings
2022-11-03 17:56       ` Vincent Lefevre
2022-11-03 18:02         ` Vincent Lefevre
2022-11-03 18:04           ` Gregory Heytings
2022-11-03 18:04           ` Vincent Lefevre
2022-11-03 18:11             ` Gregory Heytings
2022-11-03 18:18               ` Gregory Heytings
2022-11-03 18:28                 ` Vincent Lefevre
2022-11-03 18:39                   ` Eli Zaretskii
2022-11-03 18:43                   ` Gregory Heytings
2022-11-03 18:36                 ` Juri Linkov
2022-11-03 18:18               ` Eli Zaretskii
2022-11-03 18:02         ` Gregory Heytings
2022-11-03 18:03     ` Eli Zaretskii
2022-11-03 18:33       ` Vincent Lefevre
2022-11-03 18:42         ` Eli Zaretskii
2022-11-03 18:52           ` Vincent Lefevre
2022-11-03 19:22             ` Eli Zaretskii
2022-11-04  2:29               ` Vincent Lefevre
2022-11-04  3:38                 ` Vincent Lefevre
2022-11-04  7:25                   ` Eli Zaretskii
2022-11-04 10:46                     ` Vincent Lefevre
2022-11-04 11:50                       ` Eli Zaretskii
2022-11-04  7:14                 ` Eli Zaretskii
2022-11-04 10:41                   ` Vincent Lefevre
2022-11-04 10:56                     ` Vincent Lefevre
2022-11-04 11:52                       ` Eli Zaretskii
2022-11-04 13:04                         ` Vincent Lefevre
2022-11-04 13:40                           ` Eli Zaretskii
2022-11-04 11:48                     ` Eli Zaretskii
2022-11-04  3:30       ` Vincent Lefevre
2022-11-04  7:21         ` Eli Zaretskii
2022-11-04 10:15           ` Vincent Lefevre
2022-11-04 11:38             ` Andreas Schwab [this message]
2022-11-04 12:47               ` Vincent Lefevre
2022-11-04 13:25                 ` Andreas Schwab
2022-11-04 14:32                   ` Vincent Lefevre
2022-11-04 14:35                     ` Andreas Schwab
2022-11-04 15:02                       ` Vincent Lefevre
2022-11-04 15:24                         ` Andreas Schwab
2022-11-04 11:45             ` Eli Zaretskii
2022-11-04 13:56               ` Robert Pluim
2022-11-04 14:04                 ` Eli Zaretskii
2022-11-04 15:00                   ` Vincent Lefevre
2022-11-04 15:23                     ` Eli Zaretskii
2022-11-05  1:55                       ` Vincent Lefevre
2022-11-05  6:47                         ` Eli Zaretskii
2022-11-05 11:20                           ` Vincent Lefevre

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=87o7tnhrvd.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=58992@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=vincent@vinc17.net \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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.