From: Andy Wingo <wingo@pobox.com>
To: Matt Wette <matthew.wette@verizon.net>
Cc: 22601@debbugs.gnu.org
Subject: bug#22601: guile.texi section on ice-9 match
Date: Tue, 28 Feb 2017 15:50:40 +0100 [thread overview]
Message-ID: <87y3wql67z.fsf@pobox.com> (raw)
In-Reply-To: <87h9awq04z.fsf@pobox.com> (Andy Wingo's message of "Sun, 07 Aug 2016 13:38:52 +0200")
On Sun 07 Aug 2016 13:38, Andy Wingo <wingo@pobox.com> writes:
> On Mon 08 Feb 2016 22:04, Matt Wette <matthew.wette@verizon.net> writes:
>
>> One problem I have with the ref’ manual is the section on (ice-9
>> match). The grammar has terms like “string” where I don’t know if
>> this means the literal term “string” or a string literal. It would be
>> nicer to have a grammar where the literal term “string” is in
>> code-case and a string literal is described by “string” in italics. I
>> have worked on rewriting the match match grammar as @example and as
>> @table.
>>
>> Does either of these look better to you? See the PDF attached. I am
>> willing to complete the whole mess in another format, but I need to
>> know which one is preferred, if any, and someone has to verify that
>> the new grammar specification is accurate.
>
> Would you mind attaching a .texi diff? I am having trouble getting
> context here. Thanks :)
Ping :)
Cheers,
Andy
next prev parent reply other threads:[~2017-02-28 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+tCiVbOjcjdK8_GYHUkEiq+5ZSsZiCjEO+1e0kwccsJ8BNWNw@mail.gmail.com>
[not found] ` <87twlno63d.fsf@gnu.org>
[not found] ` <CA+tCiVZ0F-T1Xtjo-FLpwjN7shUr28rpT2W_kYCpcfX26ibDiw@mail.gmail.com>
[not found] ` <877figyxb2.fsf@dustycloud.org>
[not found] ` <87si13k4nn.fsf@gnu.org>
[not found] ` <87twljxbuq.fsf@dustycloud.org>
[not found] ` <87io1zueog.fsf@gnu.org>
2016-02-08 21:04 ` bug#22601: guile.texi section on ice-9 match Matt Wette
2016-08-07 11:38 ` Andy Wingo
2017-02-28 14:50 ` Andy Wingo [this message]
2017-03-19 23:00 ` Matt Wette
2017-03-19 23:42 ` Matt Wette
2017-03-20 1:56 ` Matt Wette
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=87y3wql67z.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=22601@debbugs.gnu.org \
--cc=matthew.wette@verizon.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).