all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: "Nelson H. F. Beebe" <beebe@math.utah.edu>, 5700@debbugs.gnu.org
Subject: bug#5700: emacs-23 and 8-bit characters in 128..255
Date: Wed, 06 Jul 2016 19:52:16 -0400	[thread overview]
Message-ID: <87h9c2cojz.fsf@users.sourceforge.net> (raw)
In-Reply-To: <jwvy6i19n4v.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 09 Mar 2010 17:02:14 -0500")

tags 5700 notabug
quit

With Emacs 24/25, using "\u00FF" works:

(string-equal (buffer-substring (point) (1+ (point))) "\u00FF")
(looking-at "\u00FF")

Seems to be another instance of the unibyte vs multibyte string escape syntax thing:

       You can also use hexadecimal escape sequences (‘\xN’) and octal
    escape sequences (‘\N’) in string constants.  *But beware:* If a
    string constant contains hexadecimal or octal escape sequences, and
    these escape sequences all specify unibyte characters (i.e., less
    than 256), and there are no other literal non-ASCII characters or
    Unicode-style escape sequences in the string, then Emacs
    automatically assumes that it is a unibyte string.  That is to say,
    it assumes that all non-ASCII characters occurring in the string are
    8-bit raw bytes.

Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
> which seems acceptable, whereas under Emacs-23 we have:
>
[...]
>   (multibyte-string-p "\377")   prints as    "\377"

In 23.4 it returns returns nil





  reply	other threads:[~2016-07-06 23:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-09 19:51 bug#5700: emacs-23 and 8-bit characters in 128..255 Nelson H. F. Beebe
2010-03-09 22:02 ` Stefan Monnier
2016-07-06 23:52   ` npostavs [this message]
2016-07-07 16:21     ` Eli Zaretskii

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=87h9c2cojz.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=5700@debbugs.gnu.org \
    --cc=beebe@math.utah.edu \
    --cc=monnier@IRO.UMontreal.CA \
    /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.