From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: delete text block with regexp
Date: Sun, 16 Nov 2003 23:42:37 GMT [thread overview]
Message-ID: <jwvd6brubk3.fsf-monnier+gnu.emacs.help@vor.iro.umontreal.ca> (raw)
In-Reply-To: 873ccogor2.fsf@emacswiki.org
> The critical part is that "." matches anything but a newline.
> Therefore use "\(.\|\n\)" for any character or a newline.
Beware: such a regexp tends to suffer from the "regexp stack overflow"
problem. Better use \(.*\n\)*.* which is equivalent but uses a lot
less stack space.
Sadly, to understand why you need to understand details of how the regexp
matching happens to be implemented in Emacs.
Stefan
next prev parent reply other threads:[~2003-11-16 23:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-16 9:14 delete text block with regexp Herbert Fritsch
2003-11-16 10:19 ` Oliver Scholz
2003-11-16 18:19 ` Alex Schroeder
2003-11-16 23:42 ` Stefan Monnier [this message]
2003-11-17 0:32 ` Edi Weitz
2003-11-17 5:53 ` Stefan Monnier
2003-11-17 10:31 ` Edi Weitz
2003-11-17 15:23 ` Stefan Monnier
2003-11-17 15:42 ` Oliver Scholz
2003-11-17 16:23 ` Edi Weitz
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=jwvd6brubk3.fsf-monnier+gnu.emacs.help@vor.iro.umontreal.ca \
--to=monnier@iro.umontreal.ca \
/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).