From: Arun Isaac <arunisaac@systemreboot.net>
To: 30920@debbugs.gnu.org
Subject: bug#30920: doc: Inconsistent parentheses in "(guile) sxml-match"
Date: Sat, 24 Mar 2018 10:44:46 +0530 [thread overview]
Message-ID: <cu71sgaf41l.fsf@systemreboot.net> (raw)
All examples in "(guile) sxml-match" use square parentheses around each
match clause. However, in the subsection "Guards in Patterns" alone, the
example has round parentheses. I think it would be nice to use round
parentheses consistently in all examples so that sxml-match and match
have the same syntax. But, I have no strong opinions. If you can
recommend which way to go, I can provide a patch for the same.
next reply other threads:[~2018-03-24 5:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-24 5:14 Arun Isaac [this message]
2020-03-21 21:34 ` bug#30920: doc: Inconsistent parentheses in "(guile) sxml-match" Ludovic Courtès
2020-03-23 20:30 ` Arun Isaac
2020-03-25 21:54 ` Ludovic Courtès
[not found] ` <handler.30920.D30920.15851732644863.notifdone@debbugs.gnu.org>
2020-03-26 8:20 ` bug#30920: closed (Re: bug#30920: doc: Inconsistent parentheses in "(guile) sxml-match") Arun Isaac
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=cu71sgaf41l.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=30920@debbugs.gnu.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).