Open karlicoss opened 8 years ago
Hey @wayneashleyberry do you have any thoughts on that? :)
I have a patch ready for the first part of your issue. We should discuss the second part more precise before creating any patches for visual feedback, though. For example how we want it to look like and for which commands, etc.
Reopen for general visual feedback, not just on errors.
I tend to follow the Unix philosophy here, if everything worked as expected then the application should have nothing to say. Are exit codes not enough to signify success or failure?
How's progress on this task? I'd like to work on it if there's anything to work on
Right now, if you don't specify any task title or, use tasks options incorrectly, e.g.
, nothing is printed out in the terminal, and there is no visible indication of error (except for non-zero error code sometimes). IMO it would be nice to explicitly alert the user about that and maybe show command's documentation, so for instance
wunderline add
could result inwunderline help add
.Another thing is, could we show summary of the created task in case it was created successfully? E.g.
wunderline add --due 2016-07-05 "test task"
could result in(same format
wunderline inbox
uses).What do you think? I would be happy to contribute if you think any of this is good idea.