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" <d...@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