From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Unable to use M-Ret from line-wrapped relative time items Date: Sat, 16 Apr 2011 09:28:47 +0200 Message-ID: <874o5yu028.fsf@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:44161) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QAzw5-0000aP-3S for emacs-orgmode@gnu.org; Sat, 16 Apr 2011 03:28:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QAzw4-0002Cx-8O for emacs-orgmode@gnu.org; Sat, 16 Apr 2011 03:28:53 -0400 Received: from mail-ww0-f49.google.com ([74.125.82.49]:37765) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QAzw4-0002Cn-4G for emacs-orgmode@gnu.org; Sat, 16 Apr 2011 03:28:52 -0400 Received: by wwb39 with SMTP id 39so3385895wwb.30 for ; Sat, 16 Apr 2011 00:28:51 -0700 (PDT) In-Reply-To: (Tomer Altman's message of "Wed, 13 Apr 2011 10:59:08 -0700") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: Tomer Altman Cc: emacs-orgmode@gnu.org Hello, Tomer Altman writes: > When I am using a relative timer, I can usually hit M-Ret at the end > of the current item, to create a new time-stamped item (I'm using [X] > for point): > > - 0:02:04 :: foo[X] > > This leads to a new timestamp item: > > - 0:02:04 :: foo > - 0:02:06 :: > > But when the text of the second note gets to be too long, Emacs wraps > the text to the next line (I have the Fill minor mode active). Trying > to use M-Ret from the end of the second line of the second item leads > to the attached break/backtrace: > > - 0:02:04 :: foo > - 0:02:06 :: bar bar bar bar bar bar bar bar bar bar bar bar bar bar > bar[X] > > Any ideas on how to fix this bug/break? Do I merely need to upgrade my > version of GNU Emacs? This bug has been fixed some weeks ago. You may upgrade to git latest, or wait for 7.5.1 release. Regards, -- Nicolas Goaziou