From: Noam Postavsky <npostavs@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
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: Thu, 24 May 2018 20:31:09 -0400 [thread overview]
Message-ID: <87lgc8fueq.fsf@gmail.com> (raw)
In-Reply-To: <87in7ceg7z.fsf@web.de> (Michael Heerdegen's message of "Fri, 25 May 2018 02:22:56 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
>> +Note that searching backwards may give a shorter match than expected,
>> +because the matching still happens in the forward direction. See Info
>> +anchor `(elisp) re-search-backward' for details. */)
> Too bad that the anchor is located after the relevant description.
I don't understand what you mean.
> FWIW; I still prefer the original sentence, I find it describes the
> behavior best, and short (which is good for a docstring). It is also
> good to have an alternative and more verbose explanation in the manual.
I find the original sentence kind of cryptic, but I'm okay to be
outvoted on this.
next prev parent reply other threads:[~2018-05-25 0:31 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
2018-05-24 23:55 ` Noam Postavsky
2018-05-25 0:22 ` Michael Heerdegen
2018-05-25 0:31 ` Noam Postavsky [this message]
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=87lgc8fueq.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=31584@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=michael_heerdegen@web.de \
/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.