unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Noah Lavine <noah.b.lavine@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Turn on more documentation
Date: Tue, 15 May 2012 20:19:59 -0400	[thread overview]
Message-ID: <CA+U71=NHZWsPdA+zT2KpwzfEQB_VdLX3BikSANU=+gjOReQjJQ@mail.gmail.com> (raw)
In-Reply-To: <8762bx2l24.fsf@gnu.org>

Hi,

On Tue, May 15, 2012 at 5:25 PM, Ludovic Courtès <ludo@gnu.org> wrote:
> Hi,
>
> Andy Wingo <wingo@pobox.com> skribis:
>
>> What if we merge "Guile Modules" and "Standard Library" into one
>> "Standard Library" node, and keep "API Reference" as it is?
>
> Sounds good to me.  Perhaps “Standard Library” could have sub-sections,
> like “Data Structures”, “Web”, “XML”, “Texinfo”, etc.

Yes, that sounds good to me too. However,

On Tue, May 15, 2012 at 4:24 PM, Andy Wingo <wingo@pobox.com> wrote:
> For me the difference is that nodes of "API reference" describe
> functionality that is often not segregated in modules, whereas "Guile
> Modules" has nodes that describe modules.

this distinction makes sense to me, but is not actually what is in
place. For example, "LALR parsing", "Line Oriented and Delimited
Text", "Block reading and writing", and "Local evaluation". How about
having "API Reference" be the core module, and "Guile Modules" have
everything else?

I'm still not sure that's the right distinction though.

Noah



  reply	other threads:[~2012-05-16  0:19 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
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 [this message]
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='CA+U71=NHZWsPdA+zT2KpwzfEQB_VdLX3BikSANU=+gjOReQjJQ@mail.gmail.com' \
    --to=noah.b.lavine@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).