unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Diogo F. S. Ramos" <dfsr@riseup.net>
To: guile-devel@gnu.org
Subject: [PATCH 1/2] Remove link to Emacs' regexp syntax
Date: Wed, 26 Mar 2014 00:27:20 -0300	[thread overview]
Message-ID: <1395804441-29214-1-git-send-email-dfsr@riseup.net> (raw)

Linking to Emacs' regexps as an example of regexp syntax gives the
wrong impression that Guile supports it, which is not true.

* doc/ref/api-regex.texi: Remove link to Emacs' regexp syntax
---
 doc/ref/api-regex.texi | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/doc/ref/api-regex.texi b/doc/ref/api-regex.texi
index 082fb87..f95eddb 100644
--- a/doc/ref/api-regex.texi
+++ b/doc/ref/api-regex.texi
@@ -14,10 +14,7 @@
 
 A @dfn{regular expression} (or @dfn{regexp}) is a pattern that
 describes a whole class of strings.  A full description of regular
-expressions and their syntax is beyond the scope of this manual;
-an introduction can be found in the Emacs manual (@pxref{Regexps,
-, Syntax of Regular Expressions, emacs, The GNU Emacs Manual}), or
-in many general Unix reference books.
+expressions and their syntax is beyond the scope of this manual.
 
 If your system does not include a POSIX regular expression library,
 and you have not linked Guile with a third-party regexp library such
-- 
1.9.1




             reply	other threads:[~2014-03-26  3:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26  3:27 Diogo F. S. Ramos [this message]
2014-03-26  3:27 ` [PATCH 2/2] Add reference to the lack of "non-greedy" variants Diogo F. S. Ramos
2014-03-26 21:08   ` Taylan Ulrich Bayırlı/Kammer
2014-03-27  3:46     ` Diogo F. S. Ramos
2014-03-28 19:25       ` Taylan Ulrich Bayırlı/Kammer
2014-04-15 11:38         ` Diogo F. S. Ramos
2016-06-19 15:41   ` Andy Wingo

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=1395804441-29214-1-git-send-email-dfsr@riseup.net \
    --to=dfsr@riseup.net \
    --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).