unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: 31584@debbugs.gnu.org
Subject: bug#31584: 27.0.50; Document again what match re-search-backward finds
Date: Thu, 24 May 2018 14:42:44 -0700	[thread overview]
Message-ID: <87wovsg27f.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87in7cg2qw.fsf@web.de>

Michael Heidegger <michael_heerdegen@web.de> writes:

> Hello,
>
> a user asked in emacs-help why
>
>    (re-search-backward "a*")
>
> at the end of a line consisting only "a"s didn't move point.  With
> today's documentation, that question can't be answered.
>
> Some time ago, we had this sentence in the docstring:
>
>    The match found is the one starting last in the buffer
>    and yet ending before the origin of the search.
>
> but it has been removed.  I think we need to say something like that,
> otherwise the semantics of backward re search is unclear.

I've been bitten by this before. I'm sure the sentence you cite is
correct, but I would suggest something more explicit about backwards
searches. The most useful thing I could have read when I was wondering
why this didn't work would be something like: "re-search-backward always
behaves "non-greedily", i.e., it will find the shortest match before
point".

That might not be technically correct, but those are the terms that
would have made sense to me: in particular, the "*" token is supposed to
be "greedy", so why isn't it greedy backwards? This doesn't explain why
it isn't, but it would have explicitly told me that it wouldn't be.

Eric






  reply	other threads:[~2018-05-24 21:42 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 [this message]
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
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wovsg27f.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=31584@debbugs.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).