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

Separate sorting rules by file #556

Open
swantzter opened this issue Oct 30, 2023 · 1 comment
Open

Separate sorting rules by file #556

swantzter opened this issue Oct 30, 2023 · 1 comment

Comments

@swantzter
Copy link

Feature Request

Description:
I work with a system of two todo.txt files: todo.txt and detailed-todo.txt.
My todo.txt contains somewhat more high-level tasks sorted by priority and generally has 1-3 tasks at A priority at a time - those I'm currently working on.
My detailed-todo.txt then has smaller tasks for those "A" priority tasks in case it grew larger than anticipated, and I would much rather have those sorted/grouped by project. However, if I change the sorting order in sleek today it changes globally for all files.

Implementation Details:
I'd envision this could be done in a couple different ways, it seems todotxt/todo.txt#1 on adding comments to the file format, which would allow something like a vim modeline, has stalled. Some clients (as seen in the referenced issue) has implemented support for comments with # anyway.

A more compliant alternative would probably be to store in sleek a mapping from filepath => sorting+filters config.

I would also envision that you'd maybe add a "override defaults for this file" toggle, so by default changing sorting order and filters would be global. But enabling that switch would create a per-file config that applies to only the current file. And switching it off would reset it to the globals (likely by removing the override filename=>settings mapping in storage)

Copy link

This is an automated response. We acknowledge your report, and we appreciate your engagement. However, as there has been no recent activity in this thread, it has been marked as stale. If you have any further feedback or if the matter is still relevant, please do not hesitate to respond. Otherwise, this thread will be automatically closed in 15 days from now.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 14, 2024
@ransome1 ransome1 reopened this Feb 14, 2024
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

2 participants