From: Robert Pluim <rpluim@gmail.com>
To: "Michał Nazarewicz" <mina86@mina86.com>
Cc: Alan Mackenzie <acm@muc.de>, emacs-devel@gnu.org
Subject: Re: Regexp for c-or-c++-mode
Date: Wed, 10 Jun 2020 13:40:21 +0200 [thread overview]
Message-ID: <m2zh9bf8t6.fsf@gmail.com> (raw)
In-Reply-To: <CA+pa1O3Z=iAeAFtQKUVJQ1hnyoZikqZmuZ+8LuwZqaD3Ana-zQ@mail.gmail.com> ("Michał Nazarewicz"'s message of "Wed, 10 Jun 2020 12:35:19 +0100")
>>>>> On Wed, 10 Jun 2020 12:35:19 +0100, Michał Nazarewicz <mina86@mina86.com> said:
Michał> On Tue, 9 Jun 2020 at 21:13, Alan Mackenzie <acm@muc.de> wrote:
>> On Sun, Jun 07, 2020 at 19:07:12 +0100, Michał Nazarewicz wrote:
>> > On Sun, 7 Jun 2020 at 17:41, Alan Mackenzie <acm@muc.de> wrote:
>> > > In c-or-c++-mode--regexp, there are several occurrences of
>>
>> > > [ \t\r]
>>
>> > > . These expressions notably lack \n. This seems strange, given how \n
>> > > is the normal line terminator in Emacs and \r is a rarely used artefact.
>>
>> > I wanted the regex to match single-line rather than multi-line statements
>> > to avoid false positives. Though, other than #include lines, either will
>> > probably work equally well.
>>
>> I don't fully understand. Why have you got the \r there?
Michał> I suppose you’re right. It should be [ \t\v\f] instead to catch
Michał> all non-new-line white-space characters. Or [ \t\v\f\r\n] to catch
Michał> all white-space characters.
[[:blank:]] ?
Robert
next prev parent reply other threads:[~2020-06-10 11:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 16:41 Regexp for c-or-c++-mode Alan Mackenzie
2020-06-07 18:07 ` Michał Nazarewicz
2020-06-09 20:12 ` Alan Mackenzie
2020-06-10 11:35 ` Michał Nazarewicz
2020-06-10 11:40 ` Robert Pluim [this message]
2020-06-10 13:58 ` Michał Nazarewicz
2020-06-10 14:15 ` Robert Pluim
2020-06-10 23:42 ` Michał Nazarewicz
2020-06-11 9:40 ` Alan Mackenzie
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2zh9bf8t6.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=mina86@mina86.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).