From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.help Subject: Re: flush-lines and regexp problems with emacs 22.0.x Date: Wed, 17 Jan 2007 09:01:04 +0100 Message-ID: <45ADD7C0.9090509@gmx.at> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1169020846 10508 80.91.229.12 (17 Jan 2007 08:00:46 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 17 Jan 2007 08:00:46 +0000 (UTC) Cc: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Jan 17 09:00:44 2007 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1H75ir-0006Hc-Vg for geh-help-gnu-emacs@m.gmane.org; Wed, 17 Jan 2007 09:00:42 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H75is-00040C-38 for geh-help-gnu-emacs@m.gmane.org; Wed, 17 Jan 2007 03:00:42 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H75if-0003zL-KY for help-gnu-emacs@gnu.org; Wed, 17 Jan 2007 03:00:29 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H75ie-0003yH-0x for help-gnu-emacs@gnu.org; Wed, 17 Jan 2007 03:00:29 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H75id-0003yE-Up for help-gnu-emacs@gnu.org; Wed, 17 Jan 2007 03:00:27 -0500 Original-Received: from [213.165.64.20] (helo=mail.gmx.net) by monty-python.gnu.org with smtp (Exim 4.52) id 1H75ic-0005CN-RH for help-gnu-emacs@gnu.org; Wed, 17 Jan 2007 03:00:27 -0500 Original-Received: (qmail invoked by alias); 17 Jan 2007 08:00:25 -0000 Original-Received: from N863P019.adsl.highway.telekom.at (EHLO [62.47.51.211]) [62.47.51.211] by mail.gmx.net (mp036) with SMTP; 17 Jan 2007 09:00:25 +0100 X-Authenticated: #14592706 User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: de-DE, de, en-us, en Original-To: vincent@vinc17.org X-Y-GMX-Trusted: 0 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:40389 Archived-At: > I'd say that the blank line shouldn't be deleted because nothing is > matched on it. But the end point is on this line, so I'm not sure. > The flush-lines documentation is not clear about that. `flush-lines' deletes everything from the beginning of the line where the match starts to the beginning of the line following the end of the match. I think the documentation of `flush-lines' should be improved in this regard. > (flush-lines "^\\(> \n\\)*> foo$\\(\n> .*\\)*") has no effect on it. This is explained in the manuals: For historical compatibility reasons, `$' can be used only at the end of the regular expression, or before `\)' or `\|'. > (flush-lines "^\\(> \n\\)*> foo\\($\\|\\(\n> .*\\)+\\)") doesn't have > any effect either, This is strange, it does match > foo on my system, hence it should flush that line. Please recheck.