From: Kevin Ryde <user42@zip.com.au>
Subject: Re: Functions in libguile vs SRFIs
Date: Fri, 18 Jul 2003 08:39:35 +1000 [thread overview]
Message-ID: <87n0fc3hi0.fsf@zip.com.au> (raw)
In-Reply-To: <87u19nzb5a.fsf@tapsellferrier.co.uk> (nferrier@tapsellferrier.co.uk's message of "15 Jul 2003 23:18:57 +0100")
Nic <nferrier@tapsellferrier.co.uk> writes:
>
> On this note: is the guile team interested in getting documentation
> patches which merge the doc of srfi's into the body of the doc?
I'd expect they ought to remain separate while the functions are in a
separate module. Hopefully good index entries will make it easy to
find the two places.
(Incomplete indexing is a pet peeve of mine, so sing out if anyone has
looked under some topic and wasn't taken to the desired place.)
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2003-07-17 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 22:05 Functions in libguile vs SRFIs Stephen Compall
2003-07-15 22:18 ` Nic
2003-07-17 22:39 ` 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=87n0fc3hi0.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).