From: Mark H Weaver <mhw@netris.org>
To: Matt Wette <matt.wette@gmail.com>
Cc: 30276-done@debbugs.gnu.org
Subject: bug#30276: typos in the manual (api-macros, vm)
Date: Fri, 16 Mar 2018 00:13:49 -0400 [thread overview]
Message-ID: <87po444pz6.fsf@netris.org> (raw)
In-Reply-To: <78e822a3-a2d1-9d56-311a-3b32c1a1f8b7@gmail.com> (Matt Wette's message of "Sun, 28 Jan 2018 13:26:02 -0800")
Matt Wette <matt.wette@gmail.com> writes:
> A couple typos in the maual
>
> --- api-macros.texi-fix 2018-01-28 13:22:52.305712852 -0800
> +++ api-macros.texi 2017-11-19 11:22:01.000000000 -0800
> @@ -1280,7 +1280,7 @@
> In this way @code{(macroexpand @var{foo})} is equivalent to
> @code{(macroexpand @var{foo} 'e '(eval))}. The second argument is the
> -mode (@code{'e} for ``eval'') and the third is the
> +mode (@code{'e} for ``eval'') and the second is the
> eval-syntax-expanders-when parameter (only @code{eval} in this default
> setting).
> --- vm.texi 2017-05-13 09:41:37.000000000 -0700
> +++ vm.texi-fix 2018-01-28 13:21:31.621618026 -0800
> @@ -719,7 +719,7 @@
> For calls, both in tail position and in non-tail position, we require
> that the procedure and the arguments already be shuffled into place
> -befor the call instruction. ``Into place'' for a tail call means that
> +before the call instruction. ``Into place'' for a tail call means that
> the procedure should be in slot 0, relative to the @code{fp}, and the
> arguments should follow. For a non-tail call, if the procedure is in
> @code{fp}-relative slot @var{n}, the arguments should follow from slot
Applied in commit 6d9c6833e78e560420a7805bf73a9dfbaa4b0cbb on the
stable-2.2 branch.
Thanks!
Mark
prev parent reply other threads:[~2018-03-16 4:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-28 21:26 bug#30276: typos in the manual (api-macros, vm) Matt Wette
2018-03-16 4:13 ` Mark H Weaver [this message]
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=87po444pz6.fsf@netris.org \
--to=mhw@netris.org \
--cc=30276-done@debbugs.gnu.org \
--cc=matt.wette@gmail.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).