On 14 Jan 2009, Matthew Lundin wrote:
> Hope this helps,
It does. Note to self: I should spend more time with the
manual.
Thanks! (you all!)
--
Dyslexics have more fnu.
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to
Gijs Hillenius writes:
>
> Thanks! But I thought the +0d in "SCHEDULED: <2009-01-15 Thu +0d>"
> means that I would be warned about this TODO item not 14 days or less
> before the date, but only on the date itself. Maybe I should have
> written +0, as per http://orgmode.org/org.html#Timestamps
>
>
On 14 Jan 2009, Matthew Lundin wrote:
> Gijs Hillenius writes:
>
>> Say, in one of my files, I had a
>>
>> ** TODO Pay taxes
>> SCHEDULED: <2009-01-15 Thu +0d>
>>
>> which the last few days (?) has been causing an
>>
>> org-closest-date: Arithmetic error
(snip and undo the top-quote)
> Hi Gij
Wow, that puts a really new spin on finding a 'zero-day' ... :-)
Dennis
On 14 Jan 2009, at 10:16, Gijs Hillenius wrote:
Hello,
To all readers, an inspiring 2009.
Say, in one of my files, I had a
** TODO Pay taxes
SCHEDULED: <2009-01-15 Thu +0d>
which the last few days (?) has been causi
Hi Gijs,
While you can use +0 to schedule an event for today after typing C-c
C-s on a headline, I don't believe you can use +0d for a repeating
timestamp. If it did work, it would cause a task to repeat forever on
the same day - so that's probably why it isn't supported. To create a
task that re
Hello,
To all readers, an inspiring 2009.
Say, in one of my files, I had a
** TODO Pay taxes
SCHEDULED: <2009-01-15 Thu +0d>
which the last few days (?) has been causing an
org-closest-date: Arithmetic error
I decided to investigate this today. I actually first noticed the error
this we