From: Arni Magnusson <arnima@hafro.is>
To: 8262@debbugs.gnu.org
Subject: bug#8262: string-make-*byte in elisp manual
Date: Tue, 15 Mar 2011 21:36:09 +0000 (UTC) [thread overview]
Message-ID: <alpine.LFD.2.02.1103152005570.4213@hafstormur.hafro.is> (raw)
The elisp manual mentions the functions `string-make-multibyte' and
`string-make-unibyte' in two places (Sections 4.6 and 22.15), indicating
that these functions are defined in greater detail in Section 33.2.
This is not the case, however. Shouldn't these functions be defined in
Section 33.2?
Thanks,
Arni
---
GNU Emacs Lisp Reference Manual for Emacs version 23.3 (Rev 3.0, July
2009)
next reply other threads:[~2011-03-15 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 21:36 Arni Magnusson [this message]
2011-03-16 17:40 ` bug#8262: string-make-*byte in elisp manual Stefan Monnier
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=alpine.LFD.2.02.1103152005570.4213@hafstormur.hafro.is \
--to=arnima@hafro.is \
--cc=8262@debbugs.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).