From: "Jose A. Ortega Ruiz" <jao@gnu.org>
To: guile-devel@gnu.org
Subject: Re: Publishing the manual...
Date: Mon, 01 Jun 2009 23:47:39 +0200 [thread overview]
Message-ID: <87d49nr5hg.fsf@mithrandir.homeunix.net> (raw)
In-Reply-To: 87skimqgg5.fsf@arudy.ossau.uklinux.net
Hi Neal. This sounds neat. I was thinking that, by the time the manual
hits the bookshelves, Geiser will probably have matured to the point of
having documentation: if you and/or the editors think it'd be worth it,
count on me to contribute (or help with) a short chapter on Geiser (i'll
understand it if you think it's out of scope; after all, although
Guile is its best supported Scheme, Geiser is not Guile-specific).
I'm not very familiar with Guile's documentation, or with its
implementation. On top of that, English is not my mother tongue. Despite
of that, if you think i can be of any help during the edition process,
feel free to drop me a line--i think writing about Guile would be fun.
Cheers,
jao
next prev parent reply other threads:[~2009-06-01 21:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-31 0:11 Publishing the manual Neil Jerram
2009-05-31 11:38 ` Ludovic Courtès
2009-06-02 21:44 ` Neil Jerram
2009-06-01 20:05 ` Andy Wingo
2009-06-02 21:43 ` Neil Jerram
2009-06-01 21:47 ` Jose A. Ortega Ruiz [this message]
2009-06-02 21:29 ` 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=87d49nr5hg.fsf@mithrandir.homeunix.net \
--to=jao@gnu.org \
--cc=guile-devel@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).