xaizek / dit (License: GPLv3+) (since 2018-12-07)
Command-line task keeper that remembers all old values and is meant to combine several orthogonal features to be rather flexible in managing items.
<root> / README.md (1bd0f7aedc5eb04b5952d5f7b6de8985ff889d40) (2,378B) (mode 100644) [raw]
**dit**, _v0.11_, _2015 - 2019_

_This file last updated on 9 January, 2019_

### Brief Description ###

This is a task management application for command-line oriented people.

The idea is to provide a relatively simple tool for managing software
development tasks that is more sophisticated than simple TODO lists, but simpler
than overly complicated task management software out there.  One can spot some
similarities with git.

_NOTE_: It somewhat resembles [TaskWarrior][1] by accident, didn't see it before
starting writing this application, but TaskWarrior seems to be very powerful and
should be more popular than it is, it's just that lists or search results didn't
include it.  So the reader might want to use TaskWarrior, which seems to be more
oriented on GTD and similar techniques.

### Status ###

This is quite close to 1.0 version, although it might see some changes for the
sake of improvement, but the code itself is stable.

### Features ###

* Non-numeric identifiers (non-decimal [Grey code][2]);
* Never forgets data (new values override the old ones, items are not removed);
* Isolated projects with local configuration;
* Aliases with argument substitution;
* Composition of aliases and commands.

### Usage ###

The out of the box setup is minimal.  One is likely to want to change some
settings add define convenient aliases.  There are no assumptions on the
workflow, which are expected to be defined by the user.

### Example ###

Commands look like:

```
d.d add title: Add install target. type: addition category: code status: in progress
```

Example of entry listing:

![Entry listing](data/dit.png)

See [docs](docs/08-example.md) for more detailed example.

### Supported Environment ###

Expected to work in \*nix like environments.

### Prerequisites ###

* [GNU Make][3];
* C++11 compatible compiler (e.g. GCC 4.9.3);
* [Boost][4], tested with 1.54, 1.58 and 1.59;
* (optional) [pandoc][5] for regenerating man page.

### Interaction with Environment ###

* A bash completion script simplifies interaction with the application in a
  shell.
* The application can spawn an editor to allow easier editing.

### License ###

GNU General Public License, version 3 or later.


[1]: https://taskwarrior.org/
[2]: https://en.wikipedia.org/wiki/Grey_code
[3]: https://www.gnu.org/software/make/
[4]: https://www.boost.org/
[5]: https://pandoc.org/
Hints

Before first commit, do not forget to setup your git environment:
git config --global user.name "your_name_here"
git config --global user.email "your@email_here"

Clone this repository using HTTP(S):
git clone https://code.reversed.top/user/xaizek/dit

Clone this repository using ssh (do not forget to upload a key first):
git clone ssh://rocketgit@code.reversed.top/user/xaizek/dit

You are allowed to anonymously push to this repository.
This means that your pushed commits will automatically be transformed into a pull request:
... clone the repository ...
... make some changes and some commits ...
git push origin master