Open NKjoep opened 8 years ago
I just realised you already closed a similar issue some months ago, but I still have this problem
it happened when you were editing Python file, right?
Do you have Python interpreter installed on your system? (and what operating system you're working on?)
No, it didn't. I was editing a normal js file.
And yes, I do have a python interpreter since I am running Mac OS X 10.12.1 as you can see from the bug report.
I am running Mac OS X 10.12.1 as you can see from the bug report.
yes, I overlooked this fact.
No, it didn't. I was editing a normal js file.
strange, because in theory python module of Lupa shouldn't be active in other files than *py. I will have to look on it.
I've discovered that script which analyses Python* runs always (even with JavaScript files). This can affects performance ( #36 ) but it shouldn't trigger errors (at least I cannot reproduce this bug - it works on my version of Atom 1.12.5, and it works in CLI on Node 6.0 and on Node 4.6).
I thought first maybe stdio
streams are not configured properly in child_process.spawn
I will examine that further, but if it works when I run this... I don't know.
Second thing is I've found this StackOverflow thread:
http://stackoverflow.com/questions/16170375/nodejs-not-spawning-child-process-except-in-tests
kierans (one of StackOverflow users) wrote there:
The problem was that the spawn method created on the Object prototype (see this article on Protypical inheritance) was causing the child_process.spawn function to be replaced, so the wrong function was being called.
Maybe that's the case? Maybe some package you've installed replace spawn
function on Object.prototype
?
I will examine that further.
[Enter steps to reproduce below:]
Atom Version: 1.12.2 Electron Version: 1.3.6 System: Mac OS X 10.12.1 Thrown From: atom-lupa package, v0.7.26
Stack Trace
Uncaught TypeError: Cannot read property 'on' of undefined
Commands
Config
Installed Packages