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 10:45:59 -0400 [thread overview]
Message-ID: <AANLkTin-prCG1AaV5qr0b8o8DhLhoL1pXPCULJFwQWi3@mail.gmail.com> (raw)
In-Reply-To: <83sk5btdcu.fsf@gnu.org>
On Sat, May 29, 2010 at 2:45 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Should it be, esp. as 0377 is not a representation exposed by the
>> Emacs user level interface (at least none that that I'm aware of).
>
> Again, this part of the manual is not about how Emacs represents
> characters or reads them. It's about their codes.
>
Noticed this morning the following section of the manual which
references hex values in radian notation:
,---- (info "(elisp)Coding Systems")
|
| The result of encoding, and the input to decoding, are not ordinary
| text. They logically consist of a series of byte values; that is, a
| series of ASCII and eight-bit characters. In unibyte buffers and
| strings, these characters have codes in the range 0 through #xFF
| (255). In a multibyte buffer or string, eight-bit characters have
| character codes higher than #xFF (*note Text Representations::), but
| Emacs transparently converts them to their single-byte values when you
| encode or decode such text.
|
`----
This is, I believe an example of contradictory convention in the manual.
--
/s_P\
next prev parent reply other threads:[~2010-05-31 14:45 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
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 [this message]
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=AANLkTin-prCG1AaV5qr0b8o8DhLhoL1pXPCULJFwQWi3@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).