unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Blake Shaw <blake@reproduciblemedia.com>
To: guile-devel@gnu.org
Cc: Blake Shaw <blake@reproduciblemedia.com>
Subject: [PATCH v1 5/6] docs/fixup: @cindex was in the wrong place
Date: Fri, 27 Jan 2023 01:58:00 +0700	[thread overview]
Message-ID: <20230126185801.19064-5-blake@reproduciblemedia.com> (raw)
In-Reply-To: <20230126185801.19064-1-blake@reproduciblemedia.com>

---
 doc/ref/match.texi | 13 ++++++++++---
 1 file changed, 10 insertions(+), 3 deletions(-)

diff --git a/doc/ref/match.texi b/doc/ref/match.texi
index 4f3dc86fc..5512103c4 100644
--- a/doc/ref/match.texi
+++ b/doc/ref/match.texi
@@ -23,11 +23,11 @@ The @code{(ice-9 match)} module provides a @dfn{pattern matcher},
 written by Alex Shinn, and compatible with Andrew K. Wright's pattern
 matcher found in many Scheme implementations.
 
-@cindex pattern variable
 A pattern matcher does precisely what the name implies: it matches
 some arbitrary pattern, and returns some result accordingly.
 
-@example
+@lisp
+
 (define (english-base-ten->number name)
   (match name
     ('zero   0)
@@ -40,14 +40,21 @@ some arbitrary pattern, and returns some result accordingly.
     ('seven  7)
     ('eight  8)
     ('nine   9)))
+
+@end lisp
       
+@lisp
 (english-base-ten->number 'six)
+
 @result{} 6
+@end lisp
 
+@lisp
 (apply + (map english-base-ten->number '(one two three four)))
 @result{} 10 
-@end example
+@end lisp 
 
+@cindex pattern variable
 Pattern matchers may contain @dfn{pattern variables}, local bindings
 to all elements that match a pattern.
 
-- 
2.39.1




  parent reply	other threads:[~2023-01-26 18:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26 18:57 [PATCH v1 1/6] docs/match: add pattern matching examples Blake Shaw
2023-01-26 18:57 ` [PATCH v1 2/6] docs/match: rm unquote-splicing as it interferes with textinfo Blake Shaw
2023-01-27 16:27   ` Maxime Devos
2023-01-28  9:14     ` Blake Shaw
2023-01-28 13:08       ` Maxime Devos
2023-01-29  3:09         ` Blake Shaw
2023-01-26 18:57 ` [PATCH v1 3/6] docs/match: add reverse nested list example Blake Shaw
2023-01-26 18:57 ` [PATCH v1 4/6] docs/match: match-let* unwrap example Blake Shaw
2023-01-26 18:58 ` Blake Shaw [this message]
2023-01-26 18:58 ` [PATCH v1 6/6] docs/match:style reviewing with pdf, adding newlines Blake Shaw
2023-01-28 13:18 ` [PATCH v1 1/6] docs/match: add pattern matching examples Maxime Devos
2023-01-28 19:10   ` randomlooser
2023-01-28 19:23     ` randomlooser
     [not found]   ` <CAKjmbcA9TeuC0HWE53cG4EfautTcW5s9tyh0tCXUvicAQiBFKQ@mail.gmail.com>
2023-01-29 14:23     ` Maxime Devos
2023-01-28 13:48 ` Maxime Devos
     [not found]   ` <CAKjmbcAucYA9j7suY1gEAO512pn+90ED33Wq5Z7CjrBsqxgrbw@mail.gmail.com>
2023-01-29 15:30     ` Maxime Devos
2023-01-30  0:49       ` Blake Shaw
2023-01-30 19:56         ` Aleix Conchillo Flaqué
2023-01-30 19:57           ` Aleix Conchillo Flaqué
2023-01-31  2:53           ` Maxime Devos
2023-01-31  3:59             ` Aleix Conchillo Flaqué
2023-01-31  2:28         ` [PATCH v1 1/6] docs/match: add pattern matching examples + CoC Maxime Devos

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=20230126185801.19064-5-blake@reproduciblemedia.com \
    --to=blake@reproduciblemedia.com \
    --cc=guile-devel@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).