valeratrades/todo

Cli Todo App

All notes, todos and life stats tracking in one place; organised with nothing but markdown and nvim

Note to self

I am not going to make cli commands for special cases I am not going to make cli commands for special cases I am not going to make cli commands for special cases I am not going to make cli commands for special cases I am not going to make cli commands for special cases I am not going to make cli commands for special cases I am not going to make cli commands for special cases I am not going to make cli commands for special cases I am not going to make cli commands for special cases I am not going to make cli commands for special cases I am not going to make cli commands for special cases

^{This repository follows my best practices.}

License

^{Licensed under either of Apache License, Version 2.0 or MIT license at your option.}
_{Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this crate by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.}

todo's Issues

API do

do, -> to start { [EXPECTED_TIME] -> [CATEGORY] -> [DESCRIPTION] } : to end { -d:done or -f:failed } : to edit -e:edit

make day end not at 00:00 utc, but at bedtime + 6h

document it

# API ev

ev -> day (-y:yesterday or -t:today, which is default) -> -o if open

Time to complete instead of diffiuculty

In the task name, could put estimated completion time, (in Binance Tf format), in the second position, instead of 0-9 difficulty.

Otherwise could come up with a definitive exponential difficulty scoring table, but that could be an unnecessary abstraction.

---

On the other hand:

• importance is not that linear
• how to express tightness of the certanty range?

check correctness of naming of tasks in todos on entry not when compiling quickfix

Doesn't write to pbs

could it be because of this weird truncate(true) option?

pull git commits per day

API monitor

monitor subcommand

git sync on open and close

append it to the crate::utils::open; should be straightforward