Skip to content
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

Open
karlicoss opened this issue Jul 2, 2016 · 5 comments
Open

Visual feedback on task adding #88

karlicoss opened this issue Jul 2, 2016 · 5 comments

Comments

@karlicoss
Copy link

Right now, if you don't specify any task title or, use tasks options incorrectly, e.g.

wunderline add
wunderline add --due whatever

, 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 in wunderline 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

test task  Tue 5 July   ★

(same format wunderline inbox uses).

What do you think? I would be happy to contribute if you think any of this is good idea.

@karlicoss
Copy link
Author

Hey @wayneashleyberry do you have any thoughts on that? :)

@Thor77
Copy link
Collaborator

Thor77 commented Sep 28, 2016

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.

Thor77 added a commit to Thor77/wunderline that referenced this issue Sep 28, 2016
@Thor77 Thor77 closed this as completed in f168d51 Sep 28, 2016
@Thor77
Copy link
Collaborator

Thor77 commented Sep 28, 2016

Reopen for general visual feedback, not just on errors.

@Thor77 Thor77 reopened this Sep 28, 2016
@wayneashleyberry
Copy link
Owner

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?

@alexandrebarbaruiva
Copy link
Contributor

alexandrebarbaruiva commented Feb 22, 2018

How's progress on this task? I'd like to work on it if there's anything to work on

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants