unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Ethan Stefan Day <esday@ethan-stefan.net>
Cc: 22889@debbugs.gnu.org
Subject: bug#22889: small fixes to guile manual
Date: Sun, 07 Aug 2016 23:40:54 +0200	[thread overview]
Message-ID: <87lh08ntp5.fsf@pobox.com> (raw)
In-Reply-To: <56D7A4CF.4050209@ethan-stefan.net> (Ethan Stefan Day's message of "Wed, 2 Mar 2016 21:43:27 -0500")

On Thu 03 Mar 2016 03:43, Ethan Stefan Day <esday@ethan-stefan.net> writes:

> I fixed a few small problems I found in the Guile manual as I was
> reading it.  I edited against the version I found here
> https://www.gnu.org/software/guile/manual/guile.texi.tar.gz
> at about 7pm EST on March 2, 2016.  Most of the fixes are very small,
> but the thing with car in api-data.texi could really confuse someone
> learning scheme as one of their first programming languages.

Thanks for the patches; applied.  Cheers :-)

Andy





  reply	other threads:[~2016-08-07 21:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03  2:43 bug#22889: small fixes to guile manual Ethan Stefan Day
2016-08-07 21:40 ` Andy Wingo [this message]
2016-08-07 21:41 ` 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=87lh08ntp5.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=22889@debbugs.gnu.org \
    --cc=esday@ethan-stefan.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).