From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Bug: org-time-stamp loses repeater interval Date: Sat, 02 Jul 2011 15:29:14 +0200 Message-ID: <878vsgq09h.fsf@gnu.org> References: <2011-06-24T16-30-43@devnull.Karl-Voit.at> <8772.1308931315@alphaville.dokosmarshall.org> <2011-06-26T13-23-38@devnull.Karl-Voit.at> <8739ivw8e8.fsf@gnu.org> <2011-06-28T15-28-18@devnull.Karl-Voit.at> <2011-06-28T18-04-12@devnull.Karl-Voit.at> <87sjqt6f3i.fsf@gnu.org> <2011-06-28T20-40-40@devnull.Karl-Voit.at> <874o39v9td.fsf@gnu.org> <24271.1309302652@alphaville.americas.hpqcorp.net> <87pqlxjyp9.fsf@gnu.org> <5383.1309311845@alphaville.dokosmarshall.org> <80sjqtdrl3.fsf@somewhere.org> <11081.1309358042@alphaville.dokosmarshall.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:35132) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qd0Fc-00018B-Pk for emacs-orgmode@gnu.org; Sat, 02 Jul 2011 09:28:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qd0Fa-00075D-Oe for emacs-orgmode@gnu.org; Sat, 02 Jul 2011 09:28:48 -0400 Received: from mail-fx0-f52.google.com ([209.85.161.52]:37243) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qd0Fa-000757-B7 for emacs-orgmode@gnu.org; Sat, 02 Jul 2011 09:28:46 -0400 Received: by fxd18 with SMTP id 18so3582677fxd.39 for ; Sat, 02 Jul 2011 06:28:45 -0700 (PDT) In-Reply-To: <11081.1309358042@alphaville.dokosmarshall.org> (Nick Dokos's message of "Wed, 29 Jun 2011 10:34:02 -0400") 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: nicholas.dokos@hp.com Cc: Sebastien Vauban , emacs-orgmode@gnu.org Hi Nick, Nick Dokos writes: > The other thing that I *think* I ran into is that occasionally, with a > DEADLINE and SCHEDULED on the same line, changing one would change the > *order*. I did wonder whether org was chronologically ordering them, but > that was not the case. It is now -- most recent timestamp being put first, on the front of the line. Of course, I hope one day DEADLINE and SCHEDULED will just be ordinary properties... so that we can use the org-set-property API instead of going down all the hassle of positioning things "manually" (please don't look at the code of `org-add-planning-info'!!) Best, -- Bastien