unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Turn on more documentation
Date: Mon, 14 May 2012 14:47:50 +0200	[thread overview]
Message-ID: <87k40fszd5.fsf@gnu.org> (raw)
In-Reply-To: <CA+U71=MemAWPxpUh-CTohduzvXsbKHtE_iNyj63ieKFa+TSPNw@mail.gmail.com> (Noah Lavine's message of "Sat, 12 May 2012 16:56:57 -0400")

Hi Noah!

Noah Lavine <noah.b.lavine@gmail.com> skribis:

> Okay, I can write documentation this way too. I have a question about
> this: what is the distinction between the sections "API Reference" and
> "Guile Modules"? I need to figure out where documentation for
> different modules goes.

From “Organisation of this Manual”:

  *Chapter 6: Guile API Reference*
       This part of the manual documents the Guile API in
       functionality-based groups with the Scheme and C interfaces
       presented side by side.

  *Chapter 7: Guile Modules*
       Describes some important modules, distributed as part of the Guile
       distribution, that extend the functionality provided by the Guile
       Scheme core.

So I think the idea is for core functionality to be in Chapter 6, and
“peripheral things” to be in Chapter 7.  The modules you mention would
fall in the second category, I think.

>>>> However, I believe Thien-Thi’s Guile 1.4 has good doc for at least some
>>>> of these modules, and it would be great if it could be incorporated.
>>>>
>>>> WDYT?
>>>
>>> That would be ideal, but I was concerned that the documentation wasn't
>>> copyrighted by the FSF. Unless Thien-Thi is interested in contributing
>>> it, of course.
>>
>> Yes, I was hoping he would be reading us, let’s see.  ;-)
>
> After almost a week, I think I'll plan on writing it myself.

One week is not a lot.  ;-)

Thanks,
Ludo’.



  reply	other threads:[~2012-05-14 12:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03  3:20 [PATCH] Turn on more documentation Noah Lavine
2012-05-03 22:07 ` Noah Lavine
2012-05-06 10:14 ` Ludovic Courtès
2012-05-07 12:30   ` Noah Lavine
2012-05-07 14:31     ` Ludovic Courtès
2012-05-12 20:56       ` Noah Lavine
2012-05-14 12:47         ` Ludovic Courtès [this message]
2012-05-14 14:05           ` Noah Lavine
2012-05-14 15:00             ` Ludovic Courtès
2012-05-14 15:14               ` Noah Lavine
2012-05-15 20:24                 ` Andy Wingo
2012-05-15 21:25                   ` Ludovic Courtès
2012-05-16  0:19                     ` Noah Lavine
2012-05-14 21:26             ` dsmich
2012-05-15 20:19   ` Andy Wingo

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=87k40fszd5.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=noah.b.lavine@gmail.com \
    /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).