From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martin Pohlack Subject: Re: Re: Problem with recurring timestamps Date: Mon, 06 Jul 2009 12:19:38 +0200 Message-ID: <4A51CFBA.7070803@os.inf.tu-dresden.de> References: <4A51BFD7.2040804@os.inf.tu-dresden.de> <874otqrvpj.fsf@thinkpad.tsdh.de> <4A51C9AD.9050003@os.inf.tu-dresden.de> <92E7088C-D80E-4B68-BDBB-2099335FFFB7@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MNlIa-00052Z-Je for emacs-orgmode@gnu.org; Mon, 06 Jul 2009 06:19:48 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MNlIV-0004yZ-Hr for emacs-orgmode@gnu.org; Mon, 06 Jul 2009 06:19:48 -0400 Received: from [199.232.76.173] (port=48568 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MNlIV-0004yK-9L for emacs-orgmode@gnu.org; Mon, 06 Jul 2009 06:19:43 -0400 Received: from os.inf.tu-dresden.de ([141.76.48.99]:46326) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MNlIU-0007XN-PP for emacs-orgmode@gnu.org; Mon, 06 Jul 2009 06:19:43 -0400 In-Reply-To: <92E7088C-D80E-4B68-BDBB-2099335FFFB7@gmail.com> 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: Carsten Dominik Cc: Tassilo Horn , emacs-orgmode@gnu.org Carsten Dominik wrote: > On Jul 6, 2009, at 11:53 AM, Martin Pohlack wrote: > >> Tassilo Horn wrote: >>> Martin Pohlack writes: >>> >>> Hi Martin, >>> >>>> I have problems with the following recurring timestamp: >>>> ---------------------------------------------------------------------- >>>> * TODO test3 >>>> DEADLINE: <2009-07-07 Di 15:00 +1w -1h> >>>> ---------------------------------------------------------------------- >>>> >>>> When I mark the item as done, it loses the warning period (-1h) and >>>> the recurrence markup (+1w). Marking it as done again, will finally >>>> mark it as done. >>>> >>>> Org-version reports "6.21b". >>> I can confirm that with 6.28trans. When removing the warning >>> period, it >>> works as expected. Also, when removing the recurrence markup, >>> changing >>> the item to DONE keeps the -1h intact. >> The problem seems to be that [+-]xh is not yet supported. > > yes, prewarning periods for deadlines have to de d, w, m, or y. > Hours and minutes are not supported. How are you planing to use this? I have a weekly recurring event which is due Friday 17:00, but I can only start working on it shortly before, say 2 h. I would like it not to appear in the agenda until 15:00 at Friday, or it could appear at Friday's agenda, with an extended timestamp (15:00), so I know it has to be done later. I could also be handled like this item: ---------------------------------------------------------------------- * TODO test4 DEADLINE: <2009-07-06 Mo 14:00> SCHEDULED: <2009-07-06 Mo 13:00> ---------------------------------------------------------------------- In the agenda: Monday 6 July 2009 W28 8:00...... ---------------- 10:00...... ---------------- 12:00...... ---------------- file.org:13:00...... Scheduled: TODO test4 file.org:14:00...... Deadline: TODO test4 14:00...... ---------------- 16:00...... ---------------- 18:00...... ---------------- 20:00...... ---------------- Cheers, Martin Pohlack