unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: "Diogo F. S. Ramos" <dfsr@riseup.net>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH 2/2] Add reference to the lack of "non-greedy" variants
Date: Sun, 19 Jun 2016 17:41:45 +0200	[thread overview]
Message-ID: <877fdlkwxy.fsf@pobox.com> (raw)
In-Reply-To: <1395804441-29214-2-git-send-email-dfsr@riseup.net> (Diogo F. S. Ramos's message of "Wed, 26 Mar 2014 00:27:21 -0300")

Oh my goodness Diogo, this patch and the one before were applied by no
one :( Our bad.  I just applied them, as they are small.  In the future
please nag over IRC, and if you have bigger patches please let's start
the copyright assignment process; find me on IRC to get that done.

We'll try to do better in the future; it would be hard to do worse.

Andy

On Wed 26 Mar 2014 04:27, "Diogo F. S. Ramos" <dfsr@riseup.net> writes:

> While describing special characters, remind the reader that
> "non-greedy" variants are not supported.  They might not be familiar
> with POSIX extended regular expression and expect it to work.
>
> * doc/ref/api-regex.texi: Add "non-greedy" observation
> ---
>  doc/ref/api-regex.texi | 9 +++++----
>  1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/doc/ref/api-regex.texi b/doc/ref/api-regex.texi
> index f95eddb..b14c2b3 100644
> --- a/doc/ref/api-regex.texi
> +++ b/doc/ref/api-regex.texi
> @@ -38,10 +38,11 @@ regex))}.
>  @node Regexp Functions
>  @subsection Regexp Functions
>  
> -By default, Guile supports POSIX extended regular expressions.
> -That means that the characters @samp{(}, @samp{)}, @samp{+} and
> -@samp{?} are special, and must be escaped if you wish to match the
> -literal characters.
> +By default, Guile supports POSIX extended regular expressions.  That
> +means that the characters @samp{(}, @samp{)}, @samp{+} and @samp{?} are
> +special, and must be escaped if you wish to match the literal characters
> +and there is no support for ``non-greedy'' variants of @samp{*},
> +@samp{+} or @samp{?}.
>  
>  This regular expression interface was modeled after that
>  implemented by SCSH, the Scheme Shell.  It is intended to be



      parent reply	other threads:[~2016-06-19 15:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26  3:27 [PATCH 1/2] Remove link to Emacs' regexp syntax Diogo F. S. Ramos
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 [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=877fdlkwxy.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=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).