From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Bug: org-time-stamp loses repeater interval Date: Wed, 29 Jun 2011 01:02:38 +0200 Message-ID: <874o39v9td.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> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([140.186.70.92]:51099) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QbhIR-0002XF-8J for emacs-orgmode@gnu.org; Tue, 28 Jun 2011 19:02:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QbhIJ-0004bR-LI for emacs-orgmode@gnu.org; Tue, 28 Jun 2011 19:02:19 -0400 Received: from mail-ww0-f49.google.com ([74.125.82.49]:53293) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QbhIJ-0004b8-1s for emacs-orgmode@gnu.org; Tue, 28 Jun 2011 19:02:11 -0400 Received: by wwf22 with SMTP id 22so575981wwf.30 for ; Tue, 28 Jun 2011 16:02:09 -0700 (PDT) In-Reply-To: <2011-06-28T20-40-40@devnull.Karl-Voit.at> (Karl Voit's message of "Tue, 28 Jun 2011 20:43:12 +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 Hello Karl, Karl Voit writes: > Sorry when I disagree for one case: > > When I change each entry in my test data using «C-c .» and clicking > on 1st of July ... > > ,----[ test data ] > | <2011-06-28 Tue> > | <2011-06-28 Tue +1w> > | <2011-06-28 Tue -1d> > | <2011-06-28 Tue +1w -1d> > `---- > > ... I end up having this: > > ,----[ result ] > | <2011-07-01 Fri> > | <2011-07-01 Fri +1w> > | <2011-07-01 Fri -1d> > | <2011-07-01 Fri -1d> > `---- > > In the last case, the repeater gets lost :-( I cannot reproduce this. Note that if you use the warning _before_ the repeater, then it gets losts: <2011-06-28 Tue -1d +1w> That because the warning should always be _after_ the repeater: See section 8.3.2 "Repeated tasks" in the manual "the repeater should come first and the warning period last: `DEADLINE: <2005-10-01 Sat +1m -3d>'." HTH, -- Bastien