emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Martin Pohlack <mp26@os.inf.tu-dresden.de>
Cc: Tassilo Horn <tassilo@member.fsf.org>, emacs-orgmode@gnu.org
Subject: Re: Re: Problem with recurring timestamps
Date: Mon, 6 Jul 2009 12:02:31 +0200	[thread overview]
Message-ID: <92E7088C-D80E-4B68-BDBB-2099335FFFB7@gmail.com> (raw)
In-Reply-To: <4A51C9AD.9050003@os.inf.tu-dresden.de>


On Jul 6, 2009, at 11:53 AM, Martin Pohlack wrote:

> Tassilo Horn wrote:
>> Martin Pohlack <mp26@os.inf.tu-dresden.de> 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?

- Carsten

  reply	other threads:[~2009-07-06 10:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06  9:11 Problem with recurring timestamps Martin Pohlack
2009-07-06  9:45 ` Tassilo Horn
2009-07-06  9:53   ` Martin Pohlack
2009-07-06 10:02     ` Carsten Dominik [this message]
2009-07-06 10:19       ` Martin Pohlack
2009-07-06 10:32         ` Carsten Dominik
2009-07-06 12:00           ` Martin Pohlack

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=92E7088C-D80E-4B68-BDBB-2099335FFFB7@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mp26@os.inf.tu-dresden.de \
    --cc=tassilo@member.fsf.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).