permit|assume a default priority level

[JeffreyBenjaminBrown]

My code has a number of tasks that are currently extremely low priority, but I've kept them around in case that eventually changes, which is conceivable. To try to get them out of the way, I've marked them with a (-10) value for priority. But because they have a priority value, they now appear above all the things without one. I'd like to be able to specify in the .yaml file (or, if everyone works like this, just have it hard-coded) that if it is unspecified, a task's priority is zero.

[aviaviavi]

So this behavior was on purpose, but maybe it was flawed? How I expected this to be used was that a priority would be ascending ie, p=1 shows up first and is the "highest" priority, and higher numbers might show up later, which is consistent with business jargon I often hear (so you'd actually want to mark those TODO's you mentioned as 10, not -10).

The frontend treats an empty priority as essentially p=INFINITY, as to get those entries out of the way, unless you specify otherwise. But I think it's very reasonable to want to configure this behavior. We could simply add a default_priority value in the config, which defaults to infinity. And maybe don't show that default in the UI unless it has been set via the config.

[JeffreyBenjaminBrown]

That sounds great to me.

…

On Mon, Oct 29, 2018 at 7:54 PM Avi Press ***@***.***> wrote: So this behavior was on purpose, but maybe it was flawed? How I expected this to be used was that a priority would be ascending ie, p=1 shows up first and is the "highest" priority, and higher numbers might show up later, which is consistent with business jargon I often hear (so you'd actually want to mark those TODO's you mentioned as 10, not -10). The frontend treats an empty priority as essentially p=INFINITY, as to get *those* entries out of the way, unless you specify otherwise. But I think it's very reasonable to want to configure this behavior. We could simply add a default_priority value in the config, which defaults to infinity. And maybe don't show that default in the UI unless it has been set via the config. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#34 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIfQTzEqa4NIjxFXEO9WwkwUR-G3ZLQPks5up6NQgaJpZM4YAx6H> .

-- Jeff Brown | Jeffrey Benjamin Brown Website <https://msu.edu/~brown202/> | Facebook <https://www.facebook.com/mejeff.younotjeff> | LinkedIn <https://www.linkedin.com/in/jeffreybenjaminbrown>(spammy, so I often miss messages here) | Github <https://github.com/jeffreybenjaminbrown>