| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows a unified edit functionality that supports the following:
**`t e 25 due tom`**
* Edits the due date
* Leaves subject, projects and contexts unchanged
**`t e 25 take out the trash with @bob`
* Updates the subject, projects and contexts
* Leaves the due date unchanged
**`t e 25 take out the trash with @bob due tom`
* Updates the subject, projects and contexts
* Updates the due date
**What's missing**
* Tests that exercise this functionality
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This is useful for those who need a report of entries from last week.
|
| | |
|
| |
|
|
| |
All new todos would have a space in them. This fixes that.
|
| |
|
|
|
|
|
|
|
| |
github.com/jinzhu/now has numerous errors handling date and time. The example's of them are:
1. Incorrect handling of DST (https://github.com/jinzhu/now/issues/13).
2. 24 Hour long days (https://stackoverflow.com/questions/25254443/return-local-beginning-of-day-time-object-in-go) Chicago has 23, 24, or 25 hours in a day.
3. Incorrect usage of time.Truncate which can return time with a non-zero minute, depending on the time's Location. (https://github.com/golang/go/issues/16647).
There are other issues as well, including getting incorrect beginning and end of the month.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since the panic() function provides overwhelming messages available
for developers but meaningless to users, the way to deal with error
output is simplified.
There are two panic()'s that are fixed:
* The one in parseArbitraryDateWithYear() function.
This function is the possible endpoint of adding a todo or editing
dues. Instead of calling panic(), now it outputs the specific
parsing error, and then terminate itself by os.Exit().
* The one in formatDue() function
This function is responsible for parsing the due information of a
given todo. If the todos being added previously have passed the
checking, then there is no reason that a due fails the format
check here, except for the corruption of the todo file.
|
| |\
| |
| | |
Bugfix: "todo a" no longer adds an empty todo
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will parse out dates in the format of "mon dd", the month being a 3
letter month, and the date being just the day.
due mar 10
due sep 25
due oct 2
it will also "intelligently" guess the year, based upon which is the
shorter duration from time.Now(). for instance, if today's date is dec
25 and you schedule an event for jan 2, it will schedule it for the
following year.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
