From: MON KEY <monkey@sandpframing.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 6283@debbugs.gnu.org
Subject: bug#6283: doc/lispref/searching.texi reference to octal code `0377' correct?
Date: Mon, 31 May 2010 20:24:00 -0400 [thread overview]
Message-ID: <AANLkTinnkWK1YEK5NyDkpvUemykStbN0_Vw64jPURfrJ@mail.gmail.com> (raw)
In-Reply-To: <836323ucry.fsf@gnu.org>
On Mon, May 31, 2010 at 2:49 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> > In Unicode, it's a codepoint of LATIN SMALL LETTER Y WITH DIAERESIS.
>>
>> I don't understand this.
>
> I don't know how to express this more clearly. Perhaps you could ask
> specific questions.
>
If you step through the Emacs Lisp example I sent along previously you
may notice that the search doesn't match either of the `ÿ's.
It does however match the character with numeric notations:
4194303, #o17777777, #x3fffff
4194221, #o17777655, #x3fffad
E.g. These rawbytes as presented by Emacs as characters:
(insert-byte (multibyte-char-to-unibyte 4194221) 1)
(insert-byte (multibyte-char-to-unibyte 4194303) 1)
This is what I don't understand.
If I evauate the following:
(progn
(save-excursion
(insert-byte (multibyte-char-to-unibyte 4194221) 1)
(insert-byte (multibyte-char-to-unibyte 4194303) 1))
(search-forward-regexp "ÿ" nil t))
I don't match.
Whereas if I evaluate:
(progn
(save-excursion (insert 10 #o377))
(search-forward-regexp "ÿ" nil t))
I get a match.
Likewise, if I evaluate
(progn (save-excursion (insert 10 4194303))
(search-forward-regexp "\377" nil t))
I get a match.
Which is to say, given the example regexp from the manual, i.e:
,----
| You cannot always match all non-ASCII characters with the regular
| expression `"[\200-\377]"'
`----
I am unable to locate the character: ÿ (255, #o377, #xff) e.g.
LATIN SMALL LETTER Y WITH DIAERESIS
To be clear, my issue isn't that I am not able to match `ÿ' but rather
that I am able to match the raw-byte character representation with a
visual appearance which coincides with the octal value for the `ÿ'
character code i.e. #o377 this being otherwise widely understood as
`octal 0377'.
I hope this is more clear than the previous mail. I apologize if it is not.
--
/s_P]
next prev parent reply other threads:[~2010-06-01 0:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 17:28 bug#6283: doc/lispref/searching.texi reference to octal code `0377' correct? MON KEY
2010-05-27 18:10 ` Eli Zaretskii
2010-05-27 22:59 ` MON KEY
2010-05-29 14:28 ` Kevin Rodgers
[not found] ` <AANLkTikjCByug1U69tbhsnmS4c1VXSNzoqAOAxmbt3bI@mail.gmail.com>
2010-05-28 7:15 ` Eli Zaretskii
2010-05-28 23:20 ` MON KEY
2010-05-29 6:45 ` Eli Zaretskii
2010-05-31 5:35 ` MON KEY
2010-05-31 18:49 ` Eli Zaretskii
2010-06-01 0:24 ` MON KEY [this message]
2010-06-01 18:38 ` Eli Zaretskii
2010-06-02 19:41 ` MON KEY
2010-06-03 14:39 ` Kevin Rodgers
2010-05-31 14:45 ` MON KEY
2010-05-31 18:51 ` Eli Zaretskii
2010-05-31 23:44 ` MON KEY
2010-06-02 16:06 ` MON KEY
2010-06-02 17:30 ` Chong Yidong
2010-06-02 17:46 ` 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
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=AANLkTinnkWK1YEK5NyDkpvUemykStbN0_Vw64jPURfrJ@mail.gmail.com \
--to=monkey@sandpframing.com \
--cc=6283@debbugs.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 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).