From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kevin Rodgers Newsgroups: gmane.emacs.help Subject: Re: Making re-search-forward search for \377 Date: Sun, 02 Nov 2008 11:10:18 -0700 Message-ID: References: <87tzaqporw.fsf@pcdesk.net> <87prlepk45.fsf@pcdesk.net> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1225649456 19936 80.91.229.12 (2 Nov 2008 18:10:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 2 Nov 2008 18:10:56 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Nov 02 19:11:58 2008 connect(): Connection refused Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KwhQb-0005f0-5s for geh-help-gnu-emacs@m.gmane.org; Sun, 02 Nov 2008 19:11:57 +0100 Original-Received: from localhost ([127.0.0.1]:41015 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KwhPS-0006EH-7l for geh-help-gnu-emacs@m.gmane.org; Sun, 02 Nov 2008 13:10:46 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KwhP8-0006EA-Mg for help-gnu-emacs@gnu.org; Sun, 02 Nov 2008 13:10:26 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KwhP6-0006Dv-Bp for help-gnu-emacs@gnu.org; Sun, 02 Nov 2008 13:10:25 -0500 Original-Received: from [199.232.76.173] (port=51568 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KwhP6-0006Ds-68 for help-gnu-emacs@gnu.org; Sun, 02 Nov 2008 13:10:24 -0500 Original-Received: from main.gmane.org ([80.91.229.2]:60065 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KwhP5-0005ls-Oc for help-gnu-emacs@gnu.org; Sun, 02 Nov 2008 13:10:23 -0500 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KwhP0-00056c-4A for help-gnu-emacs@gnu.org; Sun, 02 Nov 2008 18:10:18 +0000 Original-Received: from c-67-161-145-183.hsd1.co.comcast.net ([67.161.145.183]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 02 Nov 2008 18:10:18 +0000 Original-Received: from kevin.d.rodgers by c-67-161-145-183.hsd1.co.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 02 Nov 2008 18:10:18 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 39 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: c-67-161-145-183.hsd1.co.comcast.net User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914) In-Reply-To: <87prlepk45.fsf@pcdesk.net> X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:59361 Archived-At: Tyler Spivey wrote: > Xah 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. `C-u C-x =' shows this: character: ÿ (2303, #o4377, #x8ff, U+00FF) -- Kevin Rodgers Denver, Colorado, USA