From: Alan Mackenzie<none@example.invalid>
Subject: Re: Problem with re-search-backward and "\\="
Date: Wed, 17 Sep 2003 08:13:55 +0000 [thread overview]
Message-ID: <3459kb.h6.ln@acm.acm> (raw)
In-Reply-To: mailman.313.1063738732.21628.help-gnu-emacs@gnu.org
Greg Hill <ghill@synergymicro.com> wrote on Tue, 16 Sep 2003 11:57:03
-0700:
>>GNU Emacs 21.1
>>Suppose I have this in a buffer:
>>foo bar
>>With point immediately before bar (re-search-backward " *\\=") fails.
>>I would have expected this search to have succeeded, leaving point just
>>after foo.
>>Is this a bug, or have I misunderstood something?
> Alan,
> You have misunderstood the nature of the "greediness" of the '*' --
> and probably also the '+' -- postfix operator when applied to
> backward searches. It is not "symmetrical" with its effect on
> forward searches. I suggest you do some experimentation with these
> operators, never minding the "\\=" for the moment, to better
> understand the way these postfix operators work.
OK, I think I've got it now. It finds the _minimum_ match it can. With
my expression, it matches on zero spaces. It's even documented in the
elisp info pages: "A true mirror-image of `re-search-forward' would
require a special feature for matching regular expressions from end to
beginning. It's not worth the trouble of implementing that." ;-(
> I may not have this completely right, but this is the way I
> conceptualize it. When searching forward, the match-beginning
> advances forward from point until the first possible match is found;
> then match-beginning is fixed and match-end advances until going any
> farther would break the rule or exceed the specified limit. In
> searching backward, the match-beginning moves backward until the
> first possible match is found; then match-beginning is fixed and the
> match-end advances forward until going any farther would break the
> rule, using the initial value of point as the limit to how far the
> match-end is allowed to advance.
> I have never experimented with the "non-greedy" postfix operators
> '*?' '+?' and '??', so I can't tell you how using them effects the
> conceptualization described above.
I wasn't aware these existed. Thanks for the tip!
> I hope this helps.
Very much so. For what I actually need to do (moving back any
combination of whitespace and a few things like "//." as the first
non-space stuff on a line), I can do it easily enough by hand.
Many thanks.
> --Greg
--
Alan Mackenzie (Munich, Germany)
Email: aacm@muuc.dee; to decode, wherever there is a repeated letter
(like "aa"), remove half of them (leaving, say, "a").
next parent reply other threads:[~2003-09-17 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.313.1063738732.21628.help-gnu-emacs@gnu.org>
2003-09-17 8:13 ` Alan Mackenzie [this message]
2003-09-17 17:39 ` Problem with re-search-backward and "\\=" Greg Hill
2003-09-16 18:57 Greg Hill
-- strict thread matches above, loose matches on Subject: below --
2003-09-16 16:44 Alan Mackenzie
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=3459kb.h6.ln@acm.acm \
--to=none@example.invalid \
/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.