From: ludo@gnu.org (Ludovic Courtès)
To: "Andy Wingo" <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: [Guile-commits] GNU Guile branch, master, updated. release_1-9-11-112-g37620f3
Date: Sun, 20 Jun 2010 15:56:50 +0200 [thread overview]
Message-ID: <87lja93izh.fsf@gnu.org> (raw)
In-Reply-To: <E1OPwwX-0003WJ-Vc@vcs-noshell.in.savannah.gnu.org> (Andy Wingo's message of "Sat, 19 Jun 2010 12:14:37 +0000")
Hi Andy,
One small remark regarding the manual:
"Andy Wingo" <wingo@pobox.com> writes:
> +A @code{set!} to a variable transformer may only expand to an expression, not a
> +definition -- even if the original @code{set!} expression was in definition
> +context.
This should read (in Texinfo) “not a definition---even if the original”,
because the end result should be an em dash (info "(texinfo)
Conventions").
Nitpicking, but Brian Gough would probably nitpick similarly before
clicking on “print”. ;-)
Thanks,
Ludo’.
parent reply other threads:[~2010-06-20 13:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E1OPwwX-0003WJ-Vc@vcs-noshell.in.savannah.gnu.org>]
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=87lja93izh.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/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).