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

Package Spawning Process problem #72

Closed
lseongjoo opened this issue Jul 2, 2015 · 5 comments
Closed

Package Spawning Process problem #72

lseongjoo opened this issue Jul 2, 2015 · 5 comments

Comments

@lseongjoo
Copy link

How can I properly report this problem?

2015-07-02 2 12 23

@willwhitney
Copy link
Collaborator

Did you kill all Atom processes and start it from the command line?

On Thu, Jul 2, 2015, 1:13 AM Lee Seongjoo notifications@github.com wrote:

How can I properly report this problem?

[image: 2015-07-02 2 12 23]
https://cloud.githubusercontent.com/assets/444818/8470333/685e69ae-20c4-11e5-9139-e0c613d467b8.png


Reply to this email directly or view it on GitHub
#72.

@lseongjoo
Copy link
Author

I hope not. IPython is in PATH and I install the package. Then, reload Atom. That's all I did.

      1. 오전 1:11 Will Whitney notifications@github.com 작성:

Did you kill all Atom processes and start it from the command line?

On Thu, Jul 2, 2015, 1:13 AM Lee Seongjoo notifications@github.com wrote:

How can I properly report this problem?

[image: 2015-07-02 2 12 23]
https://cloud.githubusercontent.com/assets/444818/8470333/685e69ae-20c4-11e5-9139-e0c613d467b8.png


Reply to this email directly or view it on GitHub
#72.


Reply to this email directly or view it on GitHub.

@willwhitney
Copy link
Collaborator

You'll need to close Atom completely and then start it from the terminal (using the atom command). See Jank for more info.

@ryanpavlick
Copy link

@willwhitney This 'jank' could be avoided by using 'shell-environment'.

https://www.npmjs.com/package/shell-environment

atom-community/atom-script#98 (comment)

@willwhitney
Copy link
Collaborator

Yes, we've discussed doing something similar before: #34

I have similar reservations for using this path as that one. I've also written this behavior up as a bug on Atom: atom/atom#6956

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

3 participants