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:26:52 +0200 Message-ID: <87d3hsq0df.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> <2011-06-29T14-40-11@devnull.Karl-Voit.at> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:35015) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qd0DK-0000rt-AV for emacs-orgmode@gnu.org; Sat, 02 Jul 2011 09:26:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qd0DI-0006kX-M0 for emacs-orgmode@gnu.org; Sat, 02 Jul 2011 09:26:26 -0400 Received: from mail-fx0-f52.google.com ([209.85.161.52]:33679) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qd0DI-0006kR-2D for emacs-orgmode@gnu.org; Sat, 02 Jul 2011 09:26:24 -0400 Received: by fxd18 with SMTP id 18so3581604fxd.39 for ; Sat, 02 Jul 2011 06:26:23 -0700 (PDT) In-Reply-To: <2011-06-29T14-40-11@devnull.Karl-Voit.at> (Karl Voit's message of "Wed, 29 Jun 2011 14:47:22 +0200") 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: news1142@Karl-Voit.at Cc: emacs-orgmode@gnu.org Hi Karl, Karl Voit writes: > Remark regarding the order of the two entries: the last thing that > gets added/modified is always the last one in this line. So if I > create SCHEDULED and DEADLINE, DEADLINE is the second (last) in the > line. When I modify SCHEDULED afterwards, it is SCHEDULED that gets > positioned at the end of the line. Same for modifications of > DEADLINE. I've pushed fixes so that org-time-stamp, org-scheduled and org-deadline put timestamps in a more stable way. Please check against the latest git repo and report any problem. Thanks! -- Bastien