From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Mattias Engdegård" <mattiase@acm.org>, 3687@debbugs.gnu.org
Subject: bug#3687: 23.1.50; inconsistency in multibyte eight-bit regexps [PATCH]
Date: Fri, 28 Jun 2019 11:18:43 -0400 [thread overview]
Message-ID: <jwvzhm1pwo3.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83r27dhi7l.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 28 Jun 2019 17:56:14 +0300")
>> To match raw bytes, just write them. They are not special in regexp syntax and need no escaping.
Right: the proposal has nothing to do with how raw-bytes are added into
strings or buffers.
> And one more question about this part: if hex and octal escapes are
> reserved for raw bytes, then what is \123456 and its ilk, i.e. octal
> escapes whose values are above 255 decimal? Are they errors to be
> signaled about?
This question is about how to write raw bytes in a string's printed
representation, which is orthogonal: we already have escape sequences
for that and Mattias doesn't propose any changes in this respect.
Stefan
next prev parent reply other threads:[~2019-06-28 15:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 9:56 bug#3687: 23.1.50; inconsistency in multibyte eight-bit regexps YAMAMOTO Mitsuharu
2009-06-26 13:43 ` Eli Zaretskii
2009-06-27 1:30 ` YAMAMOTO Mitsuharu
2009-06-27 9:36 ` Eli Zaretskii
2009-06-29 3:02 ` YAMAMOTO Mitsuharu
2009-06-29 8:47 ` Stefan Monnier
2009-07-24 1:08 ` YAMAMOTO Mitsuharu
2019-06-28 12:41 ` bug#3687: 23.1.50; inconsistency in multibyte eight-bit regexps [PATCH] Mattias Engdegård
2019-06-28 13:03 ` Eli Zaretskii
2019-06-28 14:05 ` Mattias Engdegård
2019-06-28 14:40 ` Eli Zaretskii
2019-06-28 15:00 ` Mattias Engdegård
2019-06-28 16:20 ` Eli Zaretskii
2019-06-28 16:47 ` Mattias Engdegård
2019-06-28 14:56 ` Eli Zaretskii
2019-06-28 15:18 ` Stefan Monnier [this message]
2019-06-28 15:34 ` Mattias Engdegård
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=jwvzhm1pwo3.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=3687@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mattiase@acm.org \
/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).