Open taskwarrior opened 6 years ago
Migrated metadata:
Created: 2010-11-13T20:55:02Z
Modified: 2017-01-16T16:27:56Z
Paul Beckingham on 2011-07-10T05:54:32Z says:
Deferring for now. This turns out to be a big change that has a measurable impact on performance. Not good.
Waiting until later, to allow time to come up with a better solution.
Max Muller on 2012-08-11T19:37:33Z says:
I've encountered occasions when I'd like to not just create aliases for attribute, but to rename them entirely.
For example, I'd like to try out a way of using taskwarrior where instead of using one-dimensional concept of "priority",I use the two dimentional concept of "importance" and "urgency" (that's a user defined attribute "urgency," not the auto-calculated built in attribute). To implement, I'd like to rename "priority" to "importance" and rename the built in urgency to something else, so I could re-use the name "urgency" for a uda.
So maybe a way think about this feature request is not as having aliases for attributes, but a way for users to rename them?
Paul Beckingham on 2014-04-18T22:40:04Z says:
This has to be simply aliases for attributes. Renaming an attribute is going to break 3rd party tools and scripts.
Jeremy John Reeder on 2014-08-26T22:04:30Z says:
Another reason why attribute aliases would be nice is that it would allow for further localization. For example, I'd like to be able to include ~/.task/french
to provide French translations for all of the built-in commands and attributes. Right now I can only achieve the commands portion.
Paul Beckingham on 2014-08-26T22:09:13Z says:
Right. We would never want to localize a command name or an attribute name, because that would break scripts and extensions. We might want to create local aliases though.
Max Muller on 2010-11-13T20:55:02Z says:
I love the ability of TaskWarrior to accept abbreviated commands and attributes. Typing the first few letters of a command is sufficient to invoke it as long as the abbreviation uniquely identifies a single command or attribute.
But here's a problem: "project" and "priority" start with the same few letter. To uniquely specify them, you have to spell out at least the first three letters, plus a colon: "pro:" or "pri:"
So first, could Task Warrior allows users to specify aliases for attributes, similar to the way it accepts aliases for command names?