You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey there,
This is definetely not a bug or feature request. Rather a question that was not clear where to ask.
Question: Is it possible to have both recurrence and dependency play together? Or would it propose unnecessary complexity?
For example
|1| this is a task that recurs id:10 rec:+1m due:2000-01-01
|2| this is a task that depends on that but recurs as well p:10 due:2000-01-03
So when I do
$ topydo do 1
Expectedly a new task is created as
|3| this is a task that recurs id:10 rec:+1m due:2000-02-01
But the task 2 becoming visible doesn't happen. It is still as this
|2| this is a task that depends ... p:10 due:2000-01-03
It only becomes available when the parent is deleted.
This is rather straightforward to understand why, and that is what I like about todo.txt (in extension topydo). Easy to understand and work with. In this case the parent entry is still incomplete so the child stays hidden.
This is a use case that I just came across and I wanted to check whether there is a workaround that I don't know.
Honestly I wouldn't change anything on topydo just to cover such a edge use-case. I really like the software, well done!
The text was updated successfully, but these errors were encountered:
Hey there,
This is definetely not a bug or feature request. Rather a question that was not clear where to ask.
Question: Is it possible to have both recurrence and dependency play together? Or would it propose unnecessary complexity?
For example
So when I do
Expectedly a new task is created as
But the task 2 becoming visible doesn't happen. It is still as this
It only becomes available when the parent is deleted.
This is rather straightforward to understand why, and that is what I like about todo.txt (in extension topydo). Easy to understand and work with. In this case the parent entry is still incomplete so the child stays hidden.
This is a use case that I just came across and I wanted to check whether there is a workaround that I don't know.
Honestly I wouldn't change anything on topydo just to cover such a edge use-case. I really like the software, well done!
The text was updated successfully, but these errors were encountered: