Closed andreineculau closed 10 years ago
Hi!
Thanks for the interesting feedback. I'm planning a release with a "due date" feature, maybe I could address this issues in this same release, unless you would prefer to send the fix in a pull request?
Cheers, Rogério
I have forked this morning, and planned for a patch these days.
FYI, I also noticed another thing, which I might have in the pull request:
nodo show <task_id>
// if I make this change, it is non-backward-compatible change, unless you check if task_id is a number, or if it is not and treat it as a list (don't want to go that path)
nodo ls <list_name
I'll have to check that with more attention, but being non-backward-compatible it's not a big issue, although it would be better to avoid it.
BTW, the nodo delete <task_id>
is already implemented, I just forgot to document it in showOverview()
:)
closing due to inactivity
1 enhancement
nodo alias [list] default
ORnodo default [list]
// set a list as default (save in nodorc?)aliases + more uniform
nodo add [task]
// add task to default listnodo ls
// list tasksnodo ls lists
// list listsnodo delete [task_id]
// you have this for restore, why not for delete?!nodo rm [task_id]
nodo rm list [list_name]
more uniform help
nodo
should show all commands prioritized by command and then target type: task and list Seeingnodo delete list
beforenodo delete task
, butnodo restore task
beforenodo restore list
... can be annoying.