From: Andy Wingo <wingo@pobox.com>
To: b3timmons@speedymail.org
Cc: 9973@debbugs.gnu.org
Subject: bug#9973: Inconsistent documentation of repeated arguments
Date: Wed, 16 Nov 2011 19:46:10 +0100 [thread overview]
Message-ID: <87hb23lxcd.fsf@pobox.com> (raw)
In-Reply-To: <87obwpawy1.fsf@goof.bjgalaxy> (42toes@gmail.com's message of "Sun, 06 Nov 2011 14:10:46 -0500")
On Sun 06 Nov 2011 20:10, 42toes@gmail.com writes:
> Before making some changes to the docs, I just wanted to give a heads
> up. Recall the motivation behind Scheme
>
> "It was designed to have an exceptionally clear and simple semantics and
> few different ways to form expressions."
>
> Why not tighten up notation in the docs as well as in the language? My
> hunch is that in the long run doing so will help those learning Guile.
Sounds great to me. Care to submit a patch? :)
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-11-16 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 19:10 bug#9973: Inconsistent documentation of repeated arguments 42toes
2011-11-16 18:46 ` Andy Wingo [this message]
2013-03-10 20:20 ` 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=87hb23lxcd.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=9973@debbugs.gnu.org \
--cc=b3timmons@speedymail.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).