all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tyler Spivey <tspivey@pcdesk.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Making re-search-forward search for \377
Date: Sun, 02 Nov 2008 01:12:10 -0800	[thread overview]
Message-ID: <87prlepk45.fsf@pcdesk.net> (raw)
In-Reply-To: c6f94cfe-dae3-4983-b3e9-e5e4a281d3f1@g17g2000prg.googlegroups.com

Xah <xahlee@gmail.com> writes:

> what's the C-q 377 char?
>
> if i press Ctrl+q 377 Enter, i get this char: ÿ, which is LATIN SMALL
> LETTER Y WITH DIAERESIS (unicode U+00FF).
>
> Then if i do:
>
> (re-search-forward "ÿ")
>
> it works perfectly.
>
> as far as my experience goes, the ease of programing with unicode in
> elisp beats Perl and Python hands down...

I'm probably going to end up working with binary data in a temp
buffer. Doing more research, I want enable-multibyte-characters to be
off. Given that, if we go to *scratch*
and run M-X toggle-enable-multibyte-characters until that variable
becomes nil, doing C-Q 377 RET gives 0xff, which is what I want
(according to C-x =, C-u C-x = and M-x describe-char). Now to
match it, I try:

(re-search-forward "\xff") - no luck

What did you use to figure out that the multibyte version of that
character was 0x00FF? I found it out accidentally as a lisp error, but
none of the previously described commands (C-X =, M-X describe-char or
C-u C-x =) will show that it is 0x00ff, they just show FF.


  reply	other threads:[~2008-11-02  9:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-02  7:31 Making re-search-forward search for \377 Tyler Spivey
2008-11-02  8:45 ` Xah
2008-11-02  9:12   ` Tyler Spivey [this message]
2008-11-02 18:10     ` Kevin Rodgers
2008-11-02 20:32     ` Xah
2008-11-02 22:35       ` Tyler Spivey
2008-11-03  4:21     ` Eli Zaretskii
     [not found]     ` <mailman.2743.1225686066.25473.help-gnu-emacs@gnu.org>
2008-11-03  4:54       ` Tyler Spivey
2008-11-03 19:42         ` 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=87prlepk45.fsf@pcdesk.net \
    --to=tspivey@pcdesk.net \
    --cc=help-gnu-emacs@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.