I think I did initially implement these things in a case insensitive way, but then it was requested to make them case sensitive. I think I’ll keep as it is now. My logic being:
First it’s how things work currently, so requires no change of behavior.
Second it’s the most strait forward option and should make TaskPaper documents generally more consistent and easy to understand. For example if you see
@DONE tags all in the same document then there becomes a question… are they the same or not.
With all the various scripts and such that run through TaskPaper files I’m sure some script writers will come to one conclusion and other’s to another conclusion. Creating a mess. I think better to force case sensitive inside TaskPaper so that people keep the case consistent in tags that they expect to be equal. Then no question comes up if they are already all the same case.
So that’s all for how TaskPaper evaluates tags in searches and such.
I do think it’s OK to make autocomplete of tags case insensitive (maybe that’s all you were asking for in the first place) and I will add that to the next release.