Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recurrence+Dependency #311

Open
octvs opened this issue Mar 29, 2023 · 0 comments
Open

Recurrence+Dependency #311

octvs opened this issue Mar 29, 2023 · 0 comments

Comments

@octvs
Copy link

octvs commented Mar 29, 2023

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant