unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: [Guile-commits] GNU Guile branch, wip-manual-2, updated. release_1-9-9-85-g0a864be
Date: Mon, 12 Apr 2010 10:23:01 +0200	[thread overview]
Message-ID: <87aat9f5ay.fsf@gnu.org> (raw)
In-Reply-To: <87iq7xpluz.fsf@ossau.uklinux.net> (Neil Jerram's message of "Mon, 12 Apr 2010 01:15:16 +0100")

Hello Neil!

Neil Jerram <neil@ossau.uklinux.net> writes:

> I'm not sure if I raised it on the list, but for a while I was worried
> about the manual being so big, and I wasn't sure about how to form its
> contents into a coherent narrative - or about the extent to which that
> matters.
>
> My eventual conclusion from that was that what's really important is to
> have a good Introduction chapter.  If the Introduction does a good
> enough job of laying out the Big Picture, I think that effectively
> _creates_ the narrative for the whole manual, and the job for the rest
> of the manual is simplified to making sure that it is complete and
> technically correct (and has pleasant smaller-scale structure, of
> course).

Indeed, that makes a lot of sense to me.

> Hence, that's what I've been focussing on recently in the wip-manual-2
> branch.  I'm sure I'm still not getting everything perfect, though, so
> please do keep an occasional eye on that branch, and let me know if you
> have any developing concerns.  I will merge from master regularly so as
> not to miss stuff that's added there, and to avoid building up a
> conflict backlog.  Then, hopefully, at a point in the not too distant
> future, the manual in wip-manual-2 will be ready for pulling back into
> master, and publishing.

Sounds like a nice plan!

> <tongue slightly in cheek>
>
> The trouble is, though, when the ground keeps shifting under one's
> feet.  Now that multiple language support is really starting to take
> off, last night I was thinking that the first sentence "Guile is an
> implementation of the Scheme programming language." is probably not the
> right first sentence any more...

Well, I think it’s still too early to say it’s taking off, especially
since it already took off to a similar extent back in the day, e.g.,
when you were working on elisp in the 1.6 era.  Notably the ES compiler
has yet to be fixed, the elisp one isn’t actually used yet, and
Brainfuck, well...  ;-)

Just to say that we should be careful not to make too broad promises, IMO.

> Me too, and that reminds me that I need to get in touch with Brian to
> discuss a new realistic schedule.

Yes.

Speaking of this, the “standard library” section needs to be improved,
particularly the SXML sections, which look poor to me.

Thanks,
Ludo’.




  reply	other threads:[~2010-04-12  8:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1O0l18-0003HJ-PM@vcs-noshell.in.savannah.gnu.org>
2010-04-11 23:13 ` [Guile-commits] GNU Guile branch, wip-manual-2, updated. release_1-9-9-85-g0a864be Ludovic Courtès
2010-04-12  0:15   ` Neil Jerram
2010-04-12  8:23     ` Ludovic Courtès [this message]
2010-04-15 19:40     ` Andy Wingo
2010-04-16 21:18       ` Neil Jerram

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=87aat9f5ay.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=neil@ossau.uklinux.net \
    /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).