alexander-bauer/tasktogo

Command line task and todo list manager

tasktogo

tasktogo is a command-line todo list manager designed for both interactive and script-based use. It has support for due dates and varying priorities of tasks, and is capable of ranking tasks by urgency, (which is calculated considering both the nearness of due date and priority). For those who like rainbows, it can also colorize output.

Primarily, it is designed for single users, rather than teams. Tasks are represented in a simple JSON format, and can be accessed either directly (as a text file) or via tasktogo's interfaces, which are suitable for scripting.

It is written in pure Go.

Install

tasktogo is not yet packaged for any operating system or distribution, but should be capable of functioning on any UNIX-alike, and maybe even Windows.

If you have Go installed already, then you can do either of the following. If not, you will need to install it first.

For a full installation with manpage on UNIX-alikes:

git clone https://github.com/SashaCrofter/tasktogo.git
cd tasktogo
go get
make
sudo make install

For a source and binary-only install on any system with Go:

go install github.com/SashaCrofter/tasktogo.git

Options

Changing install location

By default, the included Makefile installs tasktogo and its resources (such as the manpage) to /usr/local, but this can be changed by prepending prefix=/usr (for example) to the make install command. In this case, then, the executable will go to /usr/bin and so on.

It is worth nothing that one should not invoke with prefix= with no argument, because then resources will not go to the correct directory.

Using a different compiler

The default compile command used is go build, with some flags used to set the version automatically. If one wants to use a different compiler or set of flags, one can prepend GOCOMPILER=gccgo (for example) to the make command.

Note that in the compiled binary, the version number will only reflect the lated tagged commit, rather than a verbose descriptor including the current commit ID.

Instructions

See the man page (if installed) via man tasktogo, or otherwise, tasktogo -h will provide some help.

Reporting bugs

tasktogo is hopelessly early-stage software, made primarily for its author's use. Bug reports and feature requests are greatly appreciated, and should both be made to the issues page, or to the author, Alexander Bauer [email protected].

When filing a bug report, please include the first line of output of tasktogo help, containing the version number.

License

tasktogo copyright © 2013 Alexander Bauer

License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html.
This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.

tasktogo's Issues

Clean up help text

Improve documentation

• Write a README
• Improve the helptext(s)
• Compose a manpage

Use a channel to report errors and severity

This would allow for simpler logging and for graceful emergency exits, such as if data can't be read from the database.

tasktogo needs the configuration file to already be there or it doesn't save anything.

If there is no ~/.tasktogo file, you get this error:

E1022 11:56:00.639680 04222 tasktogo.go:100] Could not read task list: open /home/luke/.tasktogo: no such file or directory
Could not read task list: open /home/luke/.tasktogo: no such file or directory

You can run echo '[]' > ~/.tasktogo and it will work properly, but you should not have to do that.

When there is only one task, it is not listed properly

Panics in interactive mode if no command is given

Display nearby due dates as relative time

For example, if the current date is 2013-10-30, and there is a task due on 2013-10-31, it should be shown as Tomorrow, Oct 31, rather than Thursday, Oct 31.

Events with due dates in the past are always sorted first

This is because their nice values are negative, and therefore less, even, than tasks of priority 0. What exactly to do in this case is unclear, because items with past due dates could be either extremely important (extended assignment?), not at all (forgot to mark the task done), or moderate (flexible due date).

As a compromise, they should perhaps get some boost to up them in the list, but not enough to force them to the absolute top.

Tasks are always assumed to be in the current calendar year

TaskToGo should assume that a date given without a year refers to the next occurrence of that date, rather than the one in the current calendar year. This could get very annoying, come December. See 563477e.

Add non-urgent tasks that remain at a constant nice value

Add an "exit"/"quit" command

Thanks for pointing that out, @inhies.

Mark tasks done

This requires being able to refer to the tasks in some concrete way. Perhaps a number, or just a string match?

Show only n issues at a time unless specified otherwise

Modify individual tasks

Use templates to format the list view

No error is reported when trying to list tasks on an empty file

List display has too many newlines

Suggested by @dylwhich.

Accept arguments from the command line

Implement optional color-coding for task priorities

Task name is not lowercased when trying to mark a task done

Make Task a Stringer

Strictly speaking, the Task type should probably implement the Stringer interface, using the format already in command.go.

fmt.Sprintf(
    "%s - %s (%d)\n\t%s\n",
    task.Name, task.DueBy.Format("Monday, Jan 02, 15:04"),
    task.Priority, task.Description)

Touch up Makefile and include install target

Distinguish items that are past due