feat: shortcut to set priority are now hardcoded #533
Conversation
katekorsaro
force-pushed
the
feat-priority-shortcuts
branch
from
9b54b8d to
37b9e5b
Compare
|
Thanks for a PR! Good job digging through my code and figuring this out, I know it is a mess and I appreciate you looking into it! I like this functionality! But I'd like to make it work slightly different. First, I think there shouldn't be a key defined by default, and the user would manually have to add key shortcuts to the config file. Because my understanding is that priorities in taskwarrior can be any string, right? So we'd want to configure any number of keys for any number of priorities. I can imagine this being implemented as a "increment priority" and "decrement priority". But I'll need to do the refactor first to get there unfortunately. That said, I think I'd be okay to merge this as an undocumented unstable feature :) Can you remove the documentation for it? And I'll experiment with it locally and get back to you! |
By pressing H, M, L and N now the user has the possibility to set priority to selected task(s). No custom script is needed.
katekorsaro
force-pushed
the
feat-priority-shortcuts
branch
from
37b9e5b to
9158d00
Compare
|
Ok, I amended the last commit reverting the documentation! You're right, taskwarrior lets you state your priority strings and a full rework might be needed. In the meantime, this would be enough for a "default" behaviour. |
|
Awesome! Thank you! |
By pressing H, M, L and N now the user has the possibility to set priority to selected task(s). No custom script is needed.
@kdheepak, I took the liberty of implementing some hardcoded shortcuts. I've searched through the issues but this doesn't seem to be mentioned. Though I find it useful (at least for my workflow).☺️
I don't know if this will be broken by your refactor, but you can think of it as a temp unstable feat
I've also updated the help page with the new bindings.