From: Kevin Ryde <user42@zip.com.au>
Cc: bug-guile@gnu.org
Subject: Re: Documentation on SLIB use is inadequate
Date: Sat, 17 Sep 2005 11:11:24 +1000 [thread overview]
Message-ID: <87hdck5whv.fsf@zip.com.au> (raw)
In-Reply-To: <432AD7A6.9010508@msen.com> (Alan Grover's message of "Fri, 16 Sep 2005 10:33:10 -0400")
Alan Grover <awgrover@msen.com> writes:
>
> Summary: The documentation on SLIB use is inadequate and/or out-of-date
> Guile version 1.6.4, "edition 1.0 of the reference manual, corresponding
> to Guile version 1.6.4"
That stuff hasn't been kept up to date, and the slib manual is the
best place to look for it, so I think I'll remove it, just leaving a
pointer to slib.
> SLIB was not included with my distribution of Guile (a source package
> from gnu.org).
Yep, it's separate.
> "SLIB is no longer included with Guile distributions.
I'm not sure it ever was, or not for a long time.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
prev parent reply other threads:[~2005-09-17 1:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 14:33 Documentation on SLIB use is inadequate Alan Grover
2005-09-17 1:11 ` Kevin Ryde [this message]
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=87hdck5whv.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=bug-guile@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.
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).