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

Add setting "Position for new recurring tasks in todo.txt" #704

Open
amariusz opened this issue May 6, 2024 · 1 comment
Open

Add setting "Position for new recurring tasks in todo.txt" #704

amariusz opened this issue May 6, 2024 · 1 comment

Comments

@amariusz
Copy link
Collaborator

amariusz commented May 6, 2024

Feature Request

What problem does it solve?

I'm using Sleek along with text editor. Sometimes I'd like to be able to split the file into sections for example:

# group 1 h:1
2024-05-01 task 1 t:2024-05-06 rec:7d
# group 2 h:1
2024-05-01 task 2 t:2024-05-06 rec:7d
# inbox h:1

Upon completion of task 1 I'd like to have following result.

# group 1 h:1
x 2024-05-06 2024-05-01 task 1 t:2024-05-06 rec:7d
2024-05-06 task 1 t:2024-05-13 rec:7d
# group 2 h:1
2024-05-06 task 1 t:2024-05-06 rec:7d
# inbox h:1

Inbox section is defined at the end of file and all new tasks created explicitly in Sleek UI goes here. I can visit this section in text editor and dispatch those tasks into groups.

Current Sleek's behaviour is adding new todos (created explicitly) and todos spawned from recurring tasks at the end of file:

# group 1 h:1
x 2024-05-06 2024-05-01 task 1 t:2024-05-06 rec:7d    
# group 2 h:1
2024-05-06 task 1 t:2024-05-06 rec:7d
# inbox h:1
2024-05-06 task 1 t:2024-05-13 rec:7d

With this option on, only new tasks added explicity via Sleek UI would be placed at the end of file and respawned tasks would be placed under or above completed ones.

How does the user interface change to accommodate this request?

Add dropdown in settings with label "Position for new recurring tasks in todo.txt" with options

  • End of file
  • Above completed
  • Below completed
@amariusz
Copy link
Collaborator Author

amariusz commented May 6, 2024

If this setting seems too niche to clutter the UI, I wouldn't mind just config.json option :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

1 participant