From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Eli Zaretskii <eliz@gnu.org>
Cc: cyd@gnu.org, 12054@debbugs.gnu.org
Subject: bug#12054: 24.1; regression? font-lock no-break-space with nil nobreak-char-display
Date: Sat, 03 Nov 2012 15:50:19 -0400 [thread overview]
Message-ID: <jwvsj8qtr1f.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83vcdm4oby.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 03 Nov 2012 18:56:49 +0200")
> Because, for histerical reasons, 'insert' treats strings such as
> "\nnn" as unibyte strings.
Actually, this has nothing to do with `insert', right?
It's the reader that interprets the \240 in "[\240]+" as a byte rather
than a char.
>> Why should a character-alternative expression care whether the
>> representation is unibyte or multibyte? Isn't that a bug?
There are many different ways to interpret this, and I can give you one
where the behavior is explained without paying attention to
multibyte/unibyte differences.
\240 in your string means "the byte with octal number 0240".
Stefan
next prev parent reply other threads:[~2012-11-03 19:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 5:43 bug#12054: 24.1; regression? font-lock no-break-space with nil nobreak-char-display Drew Adams
2012-09-16 23:40 ` Drew Adams
2012-11-03 10:50 ` Chong Yidong
2012-11-03 11:03 ` Chong Yidong
2012-11-03 16:25 ` Drew Adams
2012-11-03 16:56 ` Eli Zaretskii
2012-11-03 17:22 ` Drew Adams
2012-11-03 20:57 ` Eli Zaretskii
2012-11-03 19:50 ` Stefan Monnier [this message]
2012-11-03 20:02 ` Drew Adams
2012-11-03 20:36 ` Stefan Monnier
2012-11-03 20:42 ` Drew Adams
2012-11-03 17:06 ` Chong Yidong
2012-11-03 17:32 ` Drew Adams
2012-11-03 18:00 ` Chong Yidong
2012-11-03 18:04 ` Drew Adams
2012-11-03 21:00 ` Eli Zaretskii
2012-11-03 19:01 ` Drew Adams
2012-11-03 21:13 ` Eli Zaretskii
2012-11-04 23:34 ` Drew Adams
2012-11-03 16:37 ` Andreas Schwab
2012-11-03 17:05 ` Drew Adams
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=jwvsj8qtr1f.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=12054@debbugs.gnu.org \
--cc=cyd@gnu.org \
--cc=eliz@gnu.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 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.