From: Barry Margolin <barmar@alum.mit.edu>
To: help-gnu-emacs@gnu.org
Subject: Re: Question on re-search-forward and infinite loop
Date: Thu, 26 Nov 2009 18:17:16 -0500 [thread overview]
Message-ID: <barmar-EAB185.18171626112009@news.eternal-september.org> (raw)
In-Reply-To: mailman.11588.1259269277.2239.help-gnu-emacs@gnu.org
In article <mailman.11588.1259269277.2239.help-gnu-emacs@gnu.org>,
David Maus <maus.david@gmail.com> wrote:
> Hi,
>
> By accident I stumpled on a way to force Emacs in a infinite loop with
> `re-search-forward'.
>
> If I create a shiny new buffer, insert something like this:
>
> ,----
> | (while (re-search-forward "^[ \t]*"))
> | Something else
> `----
>
> -- go back beyond the while-clause and evaluate it, Emacs enters an
> infinite loop. As far as I was able to find out
> `re-search-forward' with this regexp moves point to the beginning
> of the next line above the "S" of "Something else" and stays there
> forever so it never reaches end-of-buffer.
>
> As I dunno much (or better: anything) on Emacs' interiors my question
> is: Why does this happen?
Your regexp matches zero or more whitespace characters at the beginning
of a line. If there's an empty line at the end of the buffer, it will
match that. But since it's a zero-length match, point is left at that
position, and the next time around it again matches it.
In general, whenever a regexp can match a zero-length string, I think
that type of loop will go infinitely.
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***
next parent reply other threads:[~2009-11-26 23:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.11588.1259269277.2239.help-gnu-emacs@gnu.org>
2009-11-26 23:17 ` Barry Margolin [this message]
2009-11-30 8:24 ` Question on re-search-forward and infinite loop David Maus
2009-11-26 21:01 David Maus
2009-11-26 21:11 ` Lennart Borgman
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=barmar-EAB185.18171626112009@news.eternal-september.org \
--to=barmar@alum.mit.edu \
--cc=help-gnu-emacs@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.
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).