From mboxrd@z Thu Jan  1 00:00:00 1970
From: Eli Zaretskii <eliz@gnu.org>
Subject: bug#16265: 24.3.50; re-search-forward (error "Invalid search bound
 (wrong side of point)")
Date: Wed, 01 Jan 2014 19:50:12 +0200
Message-ID: <83ha9nzj57.fsf__42065.0540771478$1388598700$gmane$org@gnu.org>
References: <m2eh4sgbw4.wl%esq@lawlist.com>
Reply-To: Eli Zaretskii <eliz@gnu.org>
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:32999)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1VyPwj-000208-GW
	for emacs-orgmode@gnu.org; Wed, 01 Jan 2014 12:51:14 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1VyPwc-0007Yo-Uv
	for emacs-orgmode@gnu.org; Wed, 01 Jan 2014 12:51:09 -0500
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.16265.B16265.138859862410287@debbugs.gnu.org>
In-reply-to: <m2eh4sgbw4.wl%esq@lawlist.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Keith David Bershatsky <esq@lawlist.com>
Cc: theonewiththeevillook@yahoo.fr, 16265@debbugs.gnu.org

> Date: Tue, 31 Dec 2013 09:37:15 -0800
> From: Keith David Bershatsky <esq@lawlist.com>
> Cc: 16265@debbugs.gnu.org
> 
> So my recommendation would be that the Emacs team return the default value of `cache-long-scans` to `nil`

Unlikely to happen.

> or, fix it somehow so that it doesn't interfere with popular functions like `re-search-forward` and `re-search-backward` after calling `org-capture`.

I think I fixed this in trunk revision 115826, please try the latest
version of the code.  (I only verified that the simplified test case
works after the fix.)

Thanks.