As I understand org - at least as of v7.4, the numeric values of priorities as calculated in org-get-priority, are variable and based on multiplying things by 1000. I can understand why this is done this way, but it is a little restrictive.
I would like to suggest that the numeric values of priorities be fixed between 0 and some value that can be user-defined, and that org-get-priority be tweaked to return a value between 0 and the max value, based on the range of priorities (i.e. from org-lowest-priority to org-highest-priority). So, for instance if you set the max numeric priority to 10, it wouldn't matter if you had 3 priority levels or 100, they'd all range between 0 and 10. In my case, I'm asking for this because I'm writing a user-defined comparator function that combines a number of features into a single measure of 'importance' (toodledo does something similar), and having the ability to essentially 'weight' the priority with respect to other values would be very useful. I'd try to do the changes myself, but I'm just not up to the task these days. Thoughts? Cheers. Fil Salustri -- \V/_ Filippo A. Salustri, Ph.D., P.Eng. Mechanical and Industrial Engineering Ryerson University 350 Victoria St, Toronto, ON M5B 2K3, Canada Tel: 416/979-5000 ext 7749 Fax: 416/979-5265 Email: salus...@ryerson.ca http://deseng.ryerson.ca/~fil/
