-
Notifications
You must be signed in to change notification settings - Fork 106
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
List of "Special tag / Additional Definitions" #8
Comments
@heX16 there is no full list since each person can use their own set of special tags. The ones I've seen used across tools have been
Maybe it's time we set a few that are part of the standards, such as Thoughts @todotxt/core |
What's threshold date? Anecdotally, and historically, due date has by far been the most-requested addition to the standard. I've pushed back on it for lots of reasons (I'm sure there are ancient discussion threads about this on the mailing list), but I'm fine with revisiting. |
The Example
While the task is due on May 5, 2017, I don't want to see it on my list (via a tool) until April 20, 2017. Moreover, some tools allow customizing how far ahead you want to see a task. Such as, show me tasks that have thresholds X days in the future. |
Ah okay, thanks for explaining. My general view has been: as soon as more dates get involved things get pretty complex pretty fast. To me, todo.txt is a task list, not a reminder tool, or a calendar, so these two dates feel outside of the scope of the spirit of the app. Not to mention what a significant burden it would put on client developers to accommodate a not-small amount of date math and other complexity (like hiding tasks that aren't complete but haven't hit their threshold date yet -- that would confuse me if I opened the file in a text editor, and the point of the format is to offer a human-readable text file that can easily be manipulated in any editor). Anyway, as always, open to dissenting opinions, but if we go back to guiding principles, I think something like threshold date is too much. There's probably a case to be made for due date, though. |
I don't think we should enforce certain tags in the standard, but rather as a recommendation / common practice. Some tools share the same semantics, but that's about it. Perhaps we could maintain a table of known todo.txt tools (perhaps a public Google sheet) with the tags that they use (syntax, semantics, and whether the tag name for that semantic is configurable). |
Oh, I think this is a good idea. Documenting the additional tags various clients have landed on as guidance for the community would be great. |
I second this. If you look at the original task, @heX16 just wants a list of what's possible. Moreover, it would really help get the tool developers in sync. |
I made a brief start at https://docs.google.com/spreadsheets/d/11nqV2j8qc_O5SVsvkZ2JGZP98CABLQ6EwBxAQQi7Huc/edit?usp=drivesdk Feel free to extend it with other clients. |
This is a great idea. I added the |
One that seems to be the most obvious missing to me is a dependency tag. I would think dependency and due date tags should even be considered officially supported per the format definition as those are pretty much universally supported in just about every task management tool ever built... |
So seems the most used tages are threshold, recurring, & hide.
I was thinking of using 'less than' & 'greater than' symbols: |
@farvardin Just to throw an alternative approach out there: All chapters for a book is a rather big task, so maybe it could be a subproject instead, consisting of tasks like "Write chapter 1" etc. (and further broken down, if you so desire). Then it should be relatively straightforward to ask the software what percentage of chapters are done, instead of you having to calculate it manually. In fact, I think that's exactly what the birdseye extension does for you... |
Android SimpleTask, from https://github.com/mpcjanssen/simpletask-android/blob/master/app/src/main/assets/index.en.md#extensions (as of 2022-09-11): Simpletask supports the following todo.txt extensions:
Simple task also has option |
Seen ttps://gitter.im/todotxt/Lobby?at=6284470aeaf3267f8566d9e3:
I've also seen |
Just realized spec has another one listed https://github.com/todotxt/todo.txt#rule-2-the-date-of-completion-appears-directly-after-the-x-separated-by-a-space as part of priority for completed tasks:
|
wait: https://lwn.net/Articles/824608/ Hide until wait date, essentially an expected start date |
https://github.com/todotxt/todotxt#additional-file-format-definitions
due:2017-01-01
hide:1
Where can I find the full list? (And add to it)
The text was updated successfully, but these errors were encountered: