From: Eli Zaretskii <eliz@gnu.org>
To: MON KEY <monkey@sandpframing.com>
Cc: 6283@debbugs.gnu.org
Subject: bug#6283: doc/lispref/searching.texi reference to octal code `0377' correct?
Date: Thu, 27 May 2010 21:10:46 +0300 [thread overview]
Message-ID: <83vda9md09.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTimxocCwSwup6COdhYZy6E7minAtJc_ec1yNCxOG@mail.gmail.com>
> Date: Thu, 27 May 2010 13:28:16 -0400
> From: MON KEY <monkey@sandpframing.com>
> Cc:
>
> In doc/lispref/searching.texi is the following reference to octal code
> `0377' correct?
>
> ,----
> | You cannot always match all non-@acronym{ASCII} characters with the
> | regular expression @code{"[\200-\377]"}. This works when searching a
> | unibyte buffer or string (@pxref{Text Representations}), but not in a
> | multibyte buffer or string, because many non-@acronym{ASCII}
> | characters have codes above octal 0377. {....}
> `---- :FILE doc/lispref/searching.texi (info "(elisp)Regexp Special")
>
> Shouldn't that be:
>
> "characters have codes above octal #o377"
What's the difference between what's written and what you suggest?
next prev parent reply other threads:[~2010-05-27 18:10 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 [this message]
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
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=83vda9md09.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=6283@debbugs.gnu.org \
--cc=monkey@sandpframing.com \
/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).