From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Daniel Clemente" Subject: Re: Invalid search bound (wrong side of point) using Remember Date: Fri, 16 Nov 2007 18:18:38 +0100 Message-ID: References: <2c75873c0711160614y736c62a0i71451703d71e503e@mail.gmail.com> <87ejeq6v45.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1It4q8-0007Mx-3J for emacs-orgmode@gnu.org; Fri, 16 Nov 2007 12:18:48 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1It4q6-0007Lo-FN for emacs-orgmode@gnu.org; Fri, 16 Nov 2007 12:18:47 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1It4q6-0007Lc-Br for emacs-orgmode@gnu.org; Fri, 16 Nov 2007 12:18:46 -0500 Received: from fk-out-0910.google.com ([209.85.128.189]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1It4q5-0001tG-BU for emacs-orgmode@gnu.org; Fri, 16 Nov 2007 12:18:46 -0500 Received: by fk-out-0910.google.com with SMTP id 19so13288fkr for ; Fri, 16 Nov 2007 09:18:43 -0800 (PST) In-Reply-To: <87ejeq6v45.fsf@bzg.ath.cx> Content-Disposition: inline List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: emacs-orgmode@gnu.org > > Thanks for the information. I tried to dig this a bit, and found out > that `org-remember-handler' was confused by the target file not being > in org-mode, even if it is an org file. Not sure this is relevant here > though. > What do you mean with =84not being in org-mode"? The error appears even if the file is open at that time. The file I'm trying to use is even part of the agenda. > > ** My configuration > > GNU Emacs 23.0.50.1 (i686-pc-linux-gnu, multi-tty) of 2007-09-05 > > > > org 5.11 > > Would you mind testing if this error occurs in latest Org? > It appears also with 5.13i, with the same backtrace.