update todo
parent
71c03f3ef5
commit
7f611e67bc
34
todo.yaml
34
todo.yaml
|
|
@ -1,20 +1,11 @@
|
||||||
todo:
|
todo:
|
||||||
- when merging, check for complete/incomplete and cross reference todo vs scheduled
|
- when merging, check for complete/incomplete and cross reference todo vs scheduled
|
||||||
vs done
|
vs done
|
||||||
- how to defer a scheduled task?
|
|
||||||
- merge multi todo files for 'inbox' style with some dedupe (probably best to just
|
|
||||||
do this via calling pttodo-cli from script or somethin) (probably at an off hour
|
|
||||||
so no collisions from live editing)
|
|
||||||
- click on links when dumped via cli
|
- click on links when dumped via cli
|
||||||
- what do about todo-now vs todo vs watch vs later... could do many files and manage
|
scheduled: []
|
||||||
outside binary, but search would suck. Good would be vendor lockin, and that's UI
|
done:
|
||||||
problem
|
- xactions emails extend ledger,todo-server with pttodo - schedule merge inbox style
|
||||||
- todo: when to run scheduled modifier? like, syncthing could have conflicts if I
|
- xactions emails extend ledger,todo-server with pttodo
|
||||||
modify only file on remote
|
|
||||||
details: |
|
|
||||||
- if it's a web ui hook or somethin, then it'd only have file conflict if I modify without waiting
|
|
||||||
- but thats a step back from current todo solution
|
|
||||||
tags: stuffToTry,secondTag
|
|
||||||
- todo: ez edit on many platforms, even offline and mobile
|
- todo: ez edit on many platforms, even offline and mobile
|
||||||
details: |
|
details: |
|
||||||
mobile view + complete method
|
mobile view + complete method
|
||||||
|
|
@ -23,10 +14,19 @@ todo:
|
||||||
web server access to ops
|
web server access to ops
|
||||||
is a web ui for mobile best solution?
|
is a web ui for mobile best solution?
|
||||||
let git be smart-ish and keep latest? would provide versioning OOTB without touching raw
|
let git be smart-ish and keep latest? would provide versioning OOTB without touching raw
|
||||||
- xactions emails extend ledger,todo-server with pttodo
|
- todo: when to run scheduled modifier? like, syncthing could have conflicts if I
|
||||||
- xactions emails extend ledger,todo-server with pttodo - schedule merge inbox style
|
modify only file on remote
|
||||||
scheduled: []
|
details: |
|
||||||
done:
|
- if it's a web ui hook or somethin, then it'd only have file conflict if I modify without waiting
|
||||||
|
- but thats a step back from current todo solution
|
||||||
|
tags: stuffToTry,secondTag
|
||||||
|
- what do about todo-now vs todo vs watch vs later... could do many files and manage
|
||||||
|
outside binary, but search would suck. Good would be vendor lockin, and that's UI
|
||||||
|
problem
|
||||||
|
- merge multi todo files for 'inbox' style with some dedupe (probably best to just
|
||||||
|
do this via calling pttodo-cli from script or somethin) (probably at an off hour
|
||||||
|
so no collisions from live editing)
|
||||||
|
- how to defer a scheduled task?
|
||||||
- todo: add tag anti-search, like -tag=-notMe
|
- todo: add tag anti-search, like -tag=-notMe
|
||||||
ts: Tue Jan 4 06:56:03 EST 2022
|
ts: Tue Jan 4 06:56:03 EST 2022
|
||||||
- todo: if in todo, then omit ts field
|
- todo: if in todo, then omit ts field
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue