zagortenay333

If a client didn't update to a new version of the spec, then they support version 1 by default.

I meant that it shouldn't be part of the specification that version 1 is assumed if a comment is missing, so that a user can just tell the client to...

How is the positioning of the comments gonna be handled by clients? When the tasks get sorted, where do you put the comments?

The issues is that if the user specifies a particular sort order _(e.g., by priority)_ and adds a task via the client, then how am I supposed to write that...

For example using the syntax I proposed for multi-line tasks: ``` --- Triple `-` followed by some text starts a section (A) asdf (A) asdf (A) asdf --- Section 2...

This group syntax would only exist to allow for the natural comment sections that anybody would want to create when editing the todo file in an editor.

The way I see it, the todo.txt file is a document first and a database second. That's the whole point of the todo.txt spec; you have a _human readable and...

No, ofc the same task can't appear twice. I don't understand why you're talking about a particular sort mechanism? No matter what the sorting mechanism is, there will be issues...

Since filters don't have a standard format in todo.txt, they should be saved in a cache file by a client anyway. Projects and contexts can already be saved in the...

Where is multiline support? That's about the only thing that would truly make todo.txt more usable, everything else looks like cosmetics to me.