unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 30703-done@debbugs.gnu.org
Subject: bug#30703: [PATCH] Fix minor typo in PEG documentation.
Date: Fri, 16 Mar 2018 00:16:29 -0400	[thread overview]
Message-ID: <87lges4puq.fsf@netris.org> (raw)
In-Reply-To: <20180304210230.21501-1-arunisaac@systemreboot.net> (Arun Isaac's message of "Mon, 5 Mar 2018 02:32:30 +0530")

Arun Isaac <arunisaac@systemreboot.net> writes:

> * doc/ref/api-peg.texi (PEG Internals): Fix minor typo.
> ---
>  doc/ref/api-peg.texi | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/ref/api-peg.texi b/doc/ref/api-peg.texi
> index cbe3edd34..82e2758b4 100644
> --- a/doc/ref/api-peg.texi
> +++ b/doc/ref/api-peg.texi
> @@ -1012,7 +1012,7 @@ interpreted internally in two steps.
>  First, any string PEG is expanded into an s-expression PEG by the code
>  in the @code{(ice-9 peg string-peg)} module.
>  
> -Then, then s-expression PEG that results is compiled into a parsing
> +Then, the s-expression PEG that results is compiled into a parsing
>  function by the @code{(ice-9 peg codegen)} module. In particular, the
>  function @code{compile-peg-pattern} is called on the s-expression. It then
>  decides what to do based on the form it is passed.

Applied in commit 01f97cfc0a2621f664202e6b19f79cf138869a3d of the
stable-2.2 branch.

    Thanks!
      Mark





      reply	other threads:[~2018-03-16  4:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-04 21:02 bug#30703: [PATCH] Fix minor typo in PEG documentation Arun Isaac
2018-03-16  4:16 ` 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=87lges4puq.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=30703-done@debbugs.gnu.org \
    --cc=arunisaac@systemreboot.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).