On Wed, Oct 26, 2011 at 12:36 PM, Demian Gemperli <[email protected]> wrote: > Hi, > > For tracks 2.1 there is an open ticket dealing with the case sensitivity of > a context. > > Suppose that you have a context called "Errands" and you start adding a new > todo and write in the context field "errands", so should... > > a) the context be added to the existing context "Errands"? > b) or should a new context being created "errands"? > > For me it makes sense that tracks reacts here case insensitive, but maybe > there are cases where this is a desirable behavior?
The UNIX guy in me says "CAse Sensitive MattERS!" but the normal user who just wants to get stuff into getontracks quickly says "just lower case it all and be happy". What is the down side of case sensitivity? Well lots of redundant entries (capitalized and all lower case most likely). What is the upside of case sensitivity? Not really sure. acronyms? Short names? But when does something with caps vs no caps matter much? I can't think of any cases for myself where I would use the same word with different capitalization for some reason. Can anyone think of a good and at least semi common (or very common) example of this? > I would be grateful if you could write a short feedback (here on the mailing > list or in the corresponding ticket on assembla[1]). > > [1] http://www.assembla.com/spaces/tracks-tickets/tickets/1059 > > Thanks, > > Demian > -- https://github.com/u2ix > > _______________________________________________ > Tracks-discuss mailing list > [email protected] > http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss > > -- Kurt Seifried [email protected] skype: (206) 905-9462 _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
