Hello,
justus-b...@piater.name writes:
My current solution (see the patch) involves some minor refactoring at
the price of an extra (if ds ...) that I don't see a way to get rid of,
but I find the result quite readable.
It looks good. I would have integrated the (if ds ...) within the cond
Nicolas Goaziou n.goaz...@gmail.com wrote on Sun, 28 Oct 2012 11:20:15
+0100:
I would have integrated the (if ds ...) within the cond (i.e (cond
((not ds) nil) ...))
Oh yes! Please do :-)
Justus
Hello,
Nicolas Goaziou n.goaz...@gmail.com wrote on Wed, 17 Oct 2012 15:07:23
+0200:
Since you provide both the patch and the commit message, what about
providing it completely as an attachement (with i.e. git format-patch)?
I attach a patch against the current git master.
- d2 diff
Hello,
justus-...@piater.name writes:
But first one more request for comments that I forgot to include in my
original message:
Computing the difference between two dates in the presence of repeating
dates is a subtle affair. Here, in computing the difference between
deadline (d2) and
Hi,
I have scratched an itch:
I would like not to be bothered with TODOs that have a scheduled date in
the future. However, as of that scheduled date I would like their
deadline prewarnings to appear in the agenda, just like non-scheduled
TODOs. I do not see how to achieve this behavior using
Hello,
justus-...@piater.name writes:
I would like not to be bothered with TODOs that have a scheduled date in
the future. However, as of that scheduled date I would like their
deadline prewarnings to appear in the agenda, just like non-scheduled
TODOs. I do not see how to achieve this
Nicolas,
Many thanks for your comments, I will heed them all.
But first one more request for comments that I forgot to include in my
original message:
Computing the difference between two dates in the presence of repeating
dates is a subtle affair. Here, in computing the difference between
