-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Visual feedback on task adding #88
Comments
Hey @wayneashleyberry do you have any thoughts on that? :) |
I have a patch ready for the first part of your issue. |
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.
The text was updated successfully, but these errors were encountered: