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

"google-chrome --incognito" won't open, opens normally without flag. #4

Closed
guifromrio opened this issue Nov 25, 2014 · 2 comments
Closed

Comments

@guifromrio
Copy link

I caught some very strange behaviour and could not think of any possibility on how to solve it.

In grunt-contrib-connect v0.8, I used "google-chrome --incognito" to develop in incognito mode.

Now that opn has been introduced in v0.9, chrome is not launched with this flag.

If I use simply google-chrome or firefox, it works perfectly.

I logged the cmd variable before execFile and it seems OK.

Any ideas?

@sindresorhus
Copy link
Owner

There's no support for app arguments currently. See #5.

The reason is that this module uses execFile instead of exec, which is safer and fixes a lot of the problems with open, but it doesn't directly support app arguments as open does.

@guifromrio
Copy link
Author

Oh, ok. nice. Didn't knew the difference between execFile and exec but now it's obvious :) Thanks

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

2 participants