Headup h:{days} syntax, usage and date error handling

[bernhardbrunner]

Hi,
Your futureTasks extension is indispensible for me. I have added a possibility to specify headup time using h:{days}. Also, added a usage and error handling. This time, I took care to leave the tabs in ;)
Thanks for your work!
Bernhard

[FND]

Thanks for this.

I had a few minutes and was curious, so tried to refamiliarize myself with this script by tweaking the code in c1dde36 (compared to your version: bernhardbrunner/todo.txt-cli@extensions...FND:headsup - YMMV on whether that constitutes an improvement).

However, as stated in #13, while I do think this is a neat idea, I'm uncomfortable taking on maintainership for it - especially because, tragically, I don't currently use todo.txt myself. Is there a compelling reason that this should live within my own repo here instead of under your own name?

[bernhardbrunner]

I just think this is a generally useful extension of your work and did not want to just fork and thus publish your work with some minor additions by me. I completely understand that you do not want to take over responsibility for maintaining more code than necessary. I'll just leave the fork as is and we will see. Cheers and take care.

[FND]

Just for the record, I'm more than fine with people building upon my code; I'm glad and surprised it's proving that useful.

Out of curiosity: I assume you came up with this heads-up period so the threshold reflects the actual deadline, i.e. you didn't wanna directly adjust that date?

(I'll leave this PR open for visibility.)

[bernhardbrunner]

Exactly. I put all the finale deadlines into todo.txt as a thresold and add the headup time so that I have enough time to finish in time. It integrates nicely with repeating events, which makes it even more useful.