| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
`CompletedDate` will save a timestamp in ISO8601 format (Internet date/
time format to preserve timezone information)
Added a new `Complete` and `Uncomplete` method for todo_item.
Currently a todo has a boolean flag and the timestamp to indicate that
the item is completed. The boolean flag could be kept for backward
compatibility (reading the json into memory), but should be omitted for
files being written.
|
| | |
|
| | |
|
| |\
| |
| | |
Show the id after creating a todo
|
| |/ |
|
| |\
| |
| | |
Adds support to projects with hyphen
|
| |/ |
|
| | |
|
| |\
| |
| | |
Global repo as the back-up plan
|
| |/
|
|
|
|
|
| |
This patch implements the logic discussed at #31, in which
the program still tries to find a repo file in the working directory
first, and it tries the global one in the home directory if no one
is found.
|
| | |
|
| |\
| |
| | |
Revert "Global repo file as the default"
|
| |/ |
|
| | |
|
| |\
| |
| | |
Fix spacing bug when adding todos
|
| | |
| |
| |
| | |
All new todos would have a space in them. This fixes that.
|
| |\ \
| |/
|/| |
Add garbage collection feature
|
| | |\
| |/
|/| |
|
| |\ \
| | |
| | | |
Remove github.com/jinzhu/now.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| |\ \ \
| | | |
| | | | |
Fix agenda bug
|
| | |/ /
| | |
| | |
| | | |
Previously, running `todo agenda` was also listing todos with no due date. Now, it won't do that.
|
| |\ \ \
| | | |
| | | | |
Add priority feature
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
Now, todos have a priority flag. When listed, these todos will be
bolded and italic.
You can list todos by priority by running `todolist l p`.
|
| |\ \ \
| |/ /
|/| | |
Global repo file as the default
|
| | | | |
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This patch implments the new workflow mentioned in #31, in which
the program still tries to find a repo file in the working directory
first, and it tries the global one in the home directory if no one
is found.
In this patch, the condition check of the existence of the repo file
is done in `todolist/file_store.go` at the very early step before
the input routing.
|
| | | |
|
| |/
|
|
|
| |
* Add `todo gc`, which will delete all archived todos.
* `NextId` will now take the first available id, rather than just the MaxId + 1.
|
| |\
| |
| | |
Correct message on "todo ac"
|
| | | |
|
| | | |
|
| |\ \
| | |
| | | |
Support UTF-8 strings as contexts and projects
|
| |/ / |
|
| |\ \
| |/
|/| |
New Feature: Expanding existing todos
|
| | | |
|
| | | |
|
| |\ \
| |/
|/| |
Dockerize this project
|
| |/ |
|
| |\
| |
| | |
Reduce the duplication during ID checking
|
| | | |
|
| | |\ |
|
| | |\ \ |
|
| | | | | |
|
| |\ \ \ \
| |_|_|/
|/| | | |
Makes all output messages consistent
|
| | | | | |
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| |\ \ \
| | | |
| | | | |
Fix delete subcommand to match website
|
| | | | | |
|