lambdara / timetrack Goto Github PK

This remove command should remove a file or directory in the ~/.timetrack directory. It should have autocompletion and commit changes to Git if a repository is initialized in the ~/.timetrack directory.

The insert command should allow a user to track an event that has already passed. The insert command should take two timestamps as argument (at least unix time should be supported, but extra formats should be nice), and if valid it should add a new file (with the current unix time as filename) which contains the unix time of the start on the first line and the unix time of the end on the second line.

Autocomplete should at least do the following:

• Autocomplete the primary command, such as start, stop and summarize.
• Autocomplete the command to start and summarize to an existing entry.

It should explain usage, as well as print a copyright notice. It should also be possible to generate the message by using either the --help or the -h flag.

The current output of status is just Unix time (meaning: in seconds). This should be something which can be read by a human, like 2018-03-03 22:12:30. It would be nice but not necessary that if it's on the current day that it would omit the date.

The application should allow for version control through Git, where changes made to .timetrack through the track command are automatically committed. The repo can be kept in .timetrack/.git. The application should also allow for normal Git commands where the working directory is set to .timetrack, so that the version history can be shared between devices using such commands as track git push and track git pull, as well as track git remote add my_server:my/timetrack/repo.

Input isn't validated at all; for some commands this could have weird side-effects with improper usage.

There should be an edit command that allows one to easily change the start time or end time of a recorded event. It should warn the user when this makes the start come after the end, and it should have autocompletion.

This could be implemented in various ways, but a combination of the flags --start, --end, --earlier, --later, --hours n, --minutes n, --seconds n and a path to the file to be changed could do.

The filename, even though it is a timestamp itself, should not be changed.

I should allow the start time in the file to be earlier than the current unix time. There should be a flag for this, perhaps --earlier or --has-started or --started. This could then get time in the 9001h13m37s to specify the difference, or perhaps it could allow the user to use one or more of the following flags: --hours n, --minutes n, --seconds n.