Taskwarrior

Assigned to Federico, along with any other date/duration work.

Also unassigned issue from 1.8.0, as date/duration overhaul is a very big deal.

Relative date references will be the wiki page where we collect information regarding date handling. I will update it with the relevant starting points for a discussion.

Discovered a simple hack to make this work. A date is now either a parseable date, or the the date/time 'now' added to a parseable duration.

does this mean that

$ task 101 wait:-2w

will work ?

(hint; the net result of this should be that wait:date is calculated as <due:date> - 2 weeks)
whereas

$ task 101 wait:+2w

means 2 weeks from now.
In most cases a negative relative date value is sanest calculated against due:date, not against now:date, unlike positive relative dates, which are sanest calculated against <now>, after all, how often do you enter a schedule note for the past, except to "log" the event, and how often would you want to wait:+2w after something is due ?

For the time being it is <now> the all the rel dates are calculated against.

The major rel dates re-implementation is still in the brainstorming phase.

well wait:-x, as calculated from due:date, will be a powerful tool for keeping things out of the way till needed, without forcing the user to back-time things manually., and otherwise negative relative dates will be of little practical use.

takes you two hours to pay a bill ?

wait:-1d

packing for your camping trip next summer ?

wait:-1m

etc.

There is a another practical use for negative relative dates - if they are referring to the current set date, you can change that one, without doing calculations in your head - it always depends on the reference point which doesn't have to be the due date. A relative date can refer to itself.

wait:20100901 -> wait:.-3 becomes wait:20100829

Please note the syntax is just hypothetical out of the blue.

As mentioned I am in the process (long and slow) of writing a RFC on this.