my example may be more closer to gtd, but the idea of having more than 1 context prefixes beyond @ increases the ways it can be used, like the one my example above.
Ali Karbassi
@karbassi
@kaushiknfs couldn't you do @work/sub1 @work/sub2, etc?
Bram Schoenmakers
@bram85
Exactly my suggestion, to use 'folders'
Ali Karbassi
@karbassi
Yea, the spec already supports this and I believe people do this with their own workflows.
Kaushik
@kaushiknfs
I didnt know that!, my question is if @work indicated a place and @adam indicated a person, there is no way to differentiate that the tag is a person or place than your understanding of the keyword ? also can you point to part of spec that defines folders please.
if i had to type @person/adam , i would have to type all the way till @person/ to kick in the auto suggest to list all persons , right?
was always curious , why the "@" , why only "@" :)
@karbassi I'll ask "Todo.txt for Chrome" to join, had been interacting with him.
Ali Karbassi
@karbassi
@kaushiknfs it's all flexible that way. You could do @p/adam or @_adam or @-adam
@kaushiknfs thanks
I use the @-personpattern, personally because then I do do todo.sh ls @- to find all the tasks that involve people
Kaushik
@kaushiknfs
@karbassi thats exactly what am doing now @&adam , like me and adam, would have been simpler with &adam, but this is just my thought, i'm quite sure people behind todo.txt and its tools would have definitely given this a thought over last 11 years.
Ali Karbassi
@karbassi
@kaushiknfs I think the thought is, if you introduce a new "keyword", like &, it should be different than the other available ones.
Kaushik
@kaushiknfs
all contexts arent equal, why should their prefix be?
Bram Schoenmakers
@bram85
I see some interesting test cases scrolling by here, curious how clients (including mine) handles these special character contexts...
Kaushik
@kaushiknfs
it would be great if the client treats prefixes + - @ # & $ , lets say a limited restricted set - uniformly as contexts and leave it to the imagination of the user to let him build context types / classes. or simply stick with + @.
Mark Janssen
@mpcjanssen
@bram85 got the gitter message. I have some ideas about the todo.txt format.
More freedom in choosing projects and contexts is one.
Some way of signifying task identity is another
I think contexts and projects should be whitespace terminated only (and maybe , and . : and ; )
A task identity is essential for any reliable syncing solution.
Bram Schoenmakers
@bram85
Identities would be a useful addition, in topydo it would've been useful in many occasions. Right now topydo maintains an id tag for those items that require an ID
Mark Janssen
@mpcjanssen
I have a change on simpletask that add a uuid for any task not having one
It looks ugly in text though
_
Rene Vergara
@ravl1084
hi, I just downloaded the latest master for todo.txt-cli and the coloring of projects and contexts is not working right. some lines are colored, some are not
Rene Vergara
@ravl1084
Found the problem, I had a ^M character at the end of some lines in my file. I think they were added by Simpletask on my phone.
Mark Janssen
@mpcjanssen
@ravl1084 simpletask should always leave the todo file with consistent line endings.
Rene Vergara
@ravl1084
@mpcjanssen Simpletask had the "use Windows-friendly line breaks" setting on by default, I cleaned up my file and turned that off and the issue was resolved