From: Kevin Ryde <user42@zip.com.au>
Subject: doco cross references
Date: Sat, 01 Feb 2003 07:51:56 +1000 [thread overview]
Message-ID: <87y951j8cj.fsf@zip.com.au> (raw)
In the "Time" node of the guile reference manual, the cross reference
to libc strftime looks like it should be "Formatting Calendar Time"
these days (eg. Debian packaged glibc 2.3.1), rather than "Formatting
Date and Time".
In the "Macros guile-snarf recognizes" node of the reference manual,
the cross reference for goops is "(goops)GOOPS", but there seems to be
no such node. Maybe it should be something like
@pxref{Creating Generic Functions,,, goops, GOOPS}
In the "What is libguile" node of the guile tutorial, the cross
reference to the reference manual comes out as "*Note Guile Reference
Manual: (Guile Reference Manual)Scheme data representation." which
clearly isn't a correct filename, and the node name seems to be out of
date too. Perhaps,
@ref{Data representation,, Data Representation in Guile,
guile, The Guile Reference Manual}
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
reply other threads:[~2003-01-31 21:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y951j8cj.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.
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).