InValidFire/todo
1
1
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

update README.md and todo.md

Browse source
This commit is contained in:
riley 2021-09-25 18:35:46 -04:00
parent 6a1ac46b59
commit cb322bd0d4
2 changed files with 1 additions and 23 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
README.md
View file

@ -15,25 +15,3 @@ todo.py is my attempt to organize myself and get things straight. I disliked the
### Sub-Section ### Sub-Section
- [ ] here's another task with a due date |Oct 13 2021 - [ ] here's another task with a due date |Oct 13 2021
``` ```
## TODO
kinda funny how a todo tool has a todo list, anyways here's what I've got to do to finish this thing:
```md
# todo.md
## Features
- [ ] add recurring tasks
- thinking about having the following section for spec
- [ ] add subtasks
- [ ] add notes
## RECURRING
- some recurring task |how often it should repeat |the last time completed
- possible values for repeat time:
- daily
- weekly - mon
- biweekly - wed
- monthly - 15
- yearly - jan - 17
```

2
todo.md
View file

@ -8,7 +8,7 @@ this is the to-do list for the `todo.md` project. *woah*.
- category headers can go as many levels as necessary. - category headers can go as many levels as necessary.
- tasks can have due-dates, and they can either be complete, or incomplete. - tasks can have due-dates, and they can either be complete, or incomplete.
- [ ] this is an incomplete task. - [ ] this is an incomplete task.
- [x] this is a complete task with a due date |Sep 30 2021. - [x] this is a complete task with a due date |Sep 30 2021
- [x] tasks can be nested on other tasks or notes. - [x] tasks can be nested on other tasks or notes.
- [ ] or they can be on the root of the category. - [ ] or they can be on the root of the category.
- all tasks must belong under a category though. - all tasks must belong under a category though.