From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Subject: Rescheduling an item works properly only if SCHEDULED is after the heading Date: Fri, 11 Jun 2010 05:54:36 +0000 (UTC) Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from [140.186.70.92] (port=33023 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OMxCa-0000nW-BO for emacs-orgmode@gnu.org; Fri, 11 Jun 2010 01:54:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OMxCZ-0006Bs-D4 for emacs-orgmode@gnu.org; Fri, 11 Jun 2010 01:54:48 -0400 Received: from lo.gmane.org ([80.91.229.12]:42225) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OMxCZ-0006BS-7W for emacs-orgmode@gnu.org; Fri, 11 Jun 2010 01:54:47 -0400 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1OMxCW-0004t2-9p for emacs-orgmode@gnu.org; Fri, 11 Jun 2010 07:54:44 +0200 Received: from 94-21-154-196.pool.digikabel.hu ([94.21.154.196]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 11 Jun 2010 07:54:44 +0200 Received: from levelhalom by 94-21-154-196.pool.digikabel.hu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 11 Jun 2010 07:54:44 +0200 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: emacs-orgmode@gnu.org I sometimes move the SCHEDULED keyword after textual content of a heading, because for me the content is more important to see than the keyword which is a technical detail of org implementation. The problem is if I use org-schedule on such a heading to reschedule the task then it inserts a new SCHEDULED keyword after the heading instead of modifying the existing keyword after the text content. Isn't it a bug? Shouldn't org always modify the existing keyword like it does when the keyword is immediately after the heading? Org-mode version 6.36