From: Michael Heerdegen <michael_heerdegen@web.de>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>, 31584@debbugs.gnu.org
Subject: bug#31584: 27.0.50; Document again what match re-search-backward finds
Date: Fri, 25 May 2018 00:47:49 +0200 [thread overview]
Message-ID: <87po1kekmi.fsf@web.de> (raw)
In-Reply-To: <87wovsg0q3.fsf@gmail.com> (Noam Postavsky's message of "Thu, 24 May 2018 18:14:44 -0400")
Noam Postavsky <npostavs@gmail.com> writes:
> The docstring should definitely be clarified, but technically it can
> still be answered, if you read very carefully:
>
> (re-search-backward REGEXP &optional BOUND NOERROR COUNT)
>
> Search backward from point for regular expression REGEXP.
> This function is almost identical to ‘re-search-forward’, except that
> by default it searches backward instead of forward, and the sign of
> COUNT also indicates exactly the opposite searching direction.
>
> (re-search-forward REGEXP &optional BOUND NOERROR COUNT)
>
> [...]
> With COUNT positive/negative, the match found is [...] located
> entirely after/before the origin of the search.
You mean the sentence about the COUNT arg? Yes, _very_ carefully.
> It is greedy:
>
> (with-temp-buffer
> (insert "xxxxyyyy")
> (and (re-search-backward "x+y*" nil t)
> (match-string 0))) ;=> "xyyyy"
>
> Non-greedy wouldn't match any "y"s. It's a bit tricky to explain both
> correctly and clearly...
Ok, good example. You convinced me that the sentence we once had was
actually quite good.
Michael.
next prev parent reply other threads:[~2018-05-24 22:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 21:31 bug#31584: 27.0.50; Document again what match re-search-backward finds Michael Heerdegen
2018-05-24 21:42 ` Eric Abrahamsen
2018-05-24 21:59 ` Michael Heerdegen
2018-05-24 22:10 ` Eric Abrahamsen
2018-05-24 22:14 ` Noam Postavsky
2018-05-24 22:47 ` Eric Abrahamsen
2018-05-24 22:47 ` Michael Heerdegen [this message]
2018-05-24 23:55 ` Noam Postavsky
2018-05-25 0:22 ` Michael Heerdegen
2018-05-25 0:31 ` Noam Postavsky
2018-05-25 0:36 ` Eric Abrahamsen
2018-05-25 1:10 ` Michael Heerdegen
2018-05-25 1:27 ` Noam Postavsky
2018-05-25 1:48 ` Michael Heerdegen
2018-05-25 6:23 ` Eli Zaretskii
2018-05-25 11:59 ` Noam Postavsky
2018-05-25 0:28 ` Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87po1kekmi.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=31584@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=npostavs@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.