From: Kevin Ryde <user42@zip.com.au>
Subject: elisp manual format cross references
Date: Tue, 19 Apr 2005 11:05:15 +1000 [thread overview]
Message-ID: <87ekd71sqc.fsf@zip.com.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 462 bytes --]
I noticed two spots where cross references for the format function
point to the wrong node.
The one in prin1-to-string is outright wrong. The second at the top
of the String Conversion node reads like format and prin1-to-string
are both in Output Functions (which is not the case).
2005-04-19 Kevin Ryde <user42@zip.com.au>
* streams.texi (Output Functions), strings.texi (String Conversion):
Correction to `format' node cross references.
[-- Attachment #2: streams.texi.format.diff --]
[-- Type: text/plain, Size: 525 bytes --]
*** streams.texi.~1.27.~ 2005-04-19 09:59:07.000000000 +1000
--- streams.texi 2005-04-19 10:55:14.458615904 +1000
***************
*** 659,665 ****
@end group
@end example
! See @code{format}, in @ref{String Conversion}, for other ways to obtain
the printed representation of a Lisp object as a string.
@end defun
--- 659,665 ----
@end group
@end example
! See @code{format}, in @ref{Formatting Strings}, for other ways to obtain
the printed representation of a Lisp object as a string.
@end defun
[-- Attachment #3: strings.texi.format.diff --]
[-- Type: text/plain, Size: 973 bytes --]
*** strings.texi.~1.38.~ 2005-04-19 09:59:07.000000000 +1000
--- strings.texi 2005-04-19 10:57:13.493519848 +1000
***************
*** 549,555 ****
@cindex conversion of strings
This section describes functions for conversions between characters,
! strings and integers. @code{format} and @code{prin1-to-string}
(@pxref{Output Functions}) can also convert Lisp objects into strings.
@code{read-from-string} (@pxref{Input Functions}) can ``convert'' a
string representation of a Lisp object into an object. The functions
--- 549,556 ----
@cindex conversion of strings
This section describes functions for conversions between characters,
! strings and integers. @code{format} (@pxref{Formatting Strings}) and
! @code{prin1-to-string}
(@pxref{Output Functions}) can also convert Lisp objects into strings.
@code{read-from-string} (@pxref{Input Functions}) can ``convert'' a
string representation of a Lisp object into an object. The functions
[-- Attachment #4: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next reply other threads:[~2005-04-19 1:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 1:05 Kevin Ryde [this message]
2005-05-04 1:17 ` elisp manual format cross references Kevin Ryde
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=87ekd71sqc.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).