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:32:03 +0200 [thread overview]
Message-ID: <B2A11896-28A3-4A9C-B4CB-A08C8ACBED95@gmail.com> (raw)
In-Reply-To: <4A51CFBA.7070803@os.inf.tu-dresden.de>
On Jul 6, 2009, at 12:19 PM, Martin Pohlack wrote:
> Carsten Dominik wrote:
>> 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?
>
> 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>
> ----------------------------------------------------------------------
This looks like a very good way to handle this use case.
The daily agenda is really about "what is up today", and it
should tell you in the morning what stuff is waiting for you
instead of giving you nasty surprises at 3 in the afternoon.
You can add a repeater to both the deadline and the
scheduled item, they will both be kicked forward when
you mark the entry done.
HTH
- Carsten
>
> 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
next prev parent reply other threads:[~2009-07-06 10:32 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
2009-07-06 10:19 ` Martin Pohlack
2009-07-06 10:32 ` Carsten Dominik [this message]
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=B2A11896-28A3-4A9C-B4CB-A08C8ACBED95@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).