Crates.io | tutel |
lib.rs | tutel |
version | 0.2.10 |
source | src |
created_at | 2022-08-03 22:51:30.970799 |
updated_at | 2023-03-26 00:54:14.85198 |
description | a minimalistic todo app for terminal enthusiasts |
homepage | https://www.github.com/0x5a4/tutel |
repository | https://www.github.com/0x5a4/tutel |
max_upload_size | |
id | 638382 |
size | 37,352 |
a minimalistic todo app trying to integrate with your existing workflow.
tutel
is built upon a simple principle: One Todo-List per directory.
Why? Because you (probably) already have some kind of directory based
organization, so there really is no need for your todo app to redo it.
Run it and tutel
will either use the todo list(saved in a .tutel.toml
file) from
your current directory or search upwards until one is found.
cargo install tutel
My overlay contains an ebuild.
A Linux-binary is provided in the Release-Tab.
// Create a list within the current directory
tutel new
// Add a todo to the list
tutel add really important thing // Everything after the subcommand is merged, no quotes necessary
// Print the todo list
tutel
Output:
[X] list with important things
001 │ [X]really important thing
// Mark the task as being completed
tutel done 0
// Edit the task, launches $EDITOR
tutel edit 0
// Remove it
tutel rm 0
// Or remove everything already completed
tutel rm --cleanup
┌─ sums up if the whole list is completed or not
│ ┌─ how many recursive steps were taken to reach this
▼ ▼
[X] [-1] project name
001 │ [X]description
▲ ▲
│ └─ the completion state of this task
└─ the index of the task, used for referencing it in commands