Hi all, 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". Cheers, Martin Pohlack
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.
Bye,
Tassilo
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.
Given that timestamps can have an hour and minute component, the h
syntax seems logical, right?
Cheers,
Martin Pohlack
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
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>
----------------------------------------------------------------------
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
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
Carsten Dominik wrote:
[...]
>> 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.
Ahh, this solves my problem, thanks. I didn't know they were completed
in one step.
Cheers,
Martin Pohlack
PS.: There is only this little "symmetry itching" thing left ;-).