Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.
9 check-ins using file README.markdown version 83a46f77db
Had to hlint on another computer... cannot get it to install on NetBSDLeaf check-in: 9a429ebc79 user: atomicules tags: origin/issue1, trunk, master
Handle any case of short day: Mon, mon, MON, etc.
Just because it'll be easier for me to use lowercase.check-in: 386fcc875a user: atomicules tags: origin/issue1, trunk, master
Support using "Mon", "Tue", etc aswell as "today", "tomorrow"
Works well, but not having hlint means my code is messy. Could do with a
Add `nextweek` command to move todos to "next" Monday
I.e. whatever day of the week the todo is on it'll be moved to the next Monday.
Follow-up to previous commit - remove all trailing slashes from apiurls
And add to the put and delete where needed.
This is better and more consistent. Also works. Odd that things magically broke
Always reference cookie files from home dir; API url changes
I forgot to commit the cookie changes awhile back so they've got caught up in a commit fixing the API urls.
The cookie stuff just makes sense. Previously the cookie files were stored in the same directory we were running haskerdeux from, which could lead to multiple files. Makes sense to reference one location (home directory).
The API changes I found when this stopped working: https://atomicules.co.uk/2017/08/27/Remind-to-Teuxdeux.html
Which is friggin' annoying as I almost forgot about Mothering Sunday.
Anyway, it seems some of the URLs haven't so much changed, but now don't like trailing slashes in some cases.
- new, post, can't have trailing slash
Yay for consistency!
Hmm... actually I might tweak this further on a following commit as the puts don't make sense to me.check-in: 4af11b69a0 user: atomicules tags: origin/issue1, trunk, master
|12:52||Add comment for future list usage support check-in: 0fe877fd3b user: atomicules tags: origin/issue1, trunk, master|
Handle automatic re-login on each separate curl call
I.e. rather than check the validity of the token each time by making a
It's still messy, but I think this approach is right - it'll just be my
|10:56||Sort out markup in README check-in: a393b4c91b user: firstname.lastname@example.org tags: origin/issue1, trunk, master|