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.

Sign up for GitHub

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

Jump to bottom

Use --no-wait as default #2

Closed
SamVerschueren opened this issue Jan 17, 2016 · 3 comments
Closed

Use --no-wait as default #2

SamVerschueren opened this issue Jan 17, 2016 · 3 comments

Comments

@SamVerschueren
Copy link
Contributor

I actually always use opn-cli with the --no-wait flag. For instance for opening the finder at certain locations. I don't want to wait untill I close the process. Wouldn't --no-wait as default make more sense? Just something I want to discuss :).

// @sindresorhus @kevva
@sindresorhus
Copy link
Owner

Hah, I was thinking about that too yesterday when manually testing this before publishing. Let's do it.

@kevva
Copy link

kevva commented Jan 17, 2016

Agree. I usually dislike this option ( --wait that is) even though it has its use cases.

@SamVerschueren
Copy link
Contributor Author

Alright, will do a PR!

@SamVerschueren SamVerschueren mentioned this issue Jan 17, 2016
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sindresorhus @kevva @SamVerschueren