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

Failed to activate #229

Closed
nwhite89 opened this issue Sep 30, 2014 · 5 comments
Closed

Failed to activate #229

nwhite89 opened this issue Sep 30, 2014 · 5 comments

Comments

@nwhite89
Copy link

I'm getting an error since the new update of not being able to run the linter and it's constantly causing my web console to pop up which is very irritating. Any ideas?

Failed to activate package named 'linter' TypeError: undefined is not a function
  at InlineView.render (/home/nwhite/Dropbox/Atom/packages/linter/lib/inline-view.coffee:14:26)
  at LinterView.updateViews (/home/nwhite/Dropbox/Atom/packages/linter/lib/linter-view.coffee:201:19)
  at LinterView.display (/home/nwhite/Dropbox/Atom/packages/linter/lib/linter-view.coffee:189:6)
  at /home/nwhite/Dropbox/Atom/packages/linter/lib/linter-view.coffee:85:10
  at Config.module.exports.Config.observe (/usr/local/share/atom/resources/app/src/config.js:229:9)
  at LinterView.handleConfigChanges (/home/nwhite/Dropbox/Atom/packages/linter/lib/linter-view.coffee:82:37)
  at new LinterView (/home/nwhite/Dropbox/Atom/packages/linter/lib/linter-view.coffee:47:6)
  at LinterInitializer.injectLinterViewIntoEditorView (/home/nwhite/Dropbox/Atom/packages/linter/lib/init.coffee:49:22)
  at /home/nwhite/Dropbox/Atom/packages/linter/lib/init.coffee:37:21
  at WorkspaceView.module.exports.WorkspaceView.eachEditorView (/usr/local/share/atom/resources/app/src/workspace-view.js:485:9)
  at LinterInitializer.activate (/home/nwhite/Dropbox/Atom/packages/linter/lib/init.coffee:36:50)
  at Package.module.exports.Package.activateNow (/usr/local/share/atom/resources/app/src/package.js:163:27)
  at /usr/local/share/atom/resources/app/src/package.js:149:28
  at Package.module.exports.Package.measure (/usr/local/share/atom/resources/app/src/package.js:95:15)
  at Package.module.exports.Package.activate (/usr/local/share/atom/resources/app/src/package.js:143:14)
  at PackageManager.module.exports.PackageManager.activatePackage (/usr/local/share/atom/resources/app/src/package-manager.js:109:21)
  at PackageManager.module.exports.PackageManager.activatePackages (/usr/local/share/atom/resources/app/src/package-manager.js:98:14)
  at PackageManager.module.exports.PackageManager.activate (/usr/local/share/atom/resources/app/src/package-manager.js:85:19)
  at Atom.module.exports.Atom.startEditorWindow (/usr/local/share/atom/resources/app/src/atom.js:369:21)
  at Object.<anonymous> (/usr/local/share/atom/resources/app/src/window-bootstrap.js:14:8)
  at Object.<anonymous> (/usr/local/share/atom/resources/app/src/window-bootstrap.js:20:4)
  at Module._compile (module.js:455:26)
  at Object.Module._extensions..js (module.js:473:10)
  at Module.load (/usr/local/share/atom/resources/app/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
  at Function.Module._load (module.js:311:12)
  at Module.require (module.js:363:17)
  at require (module.js:379:17)
  at window.onload (file:///usr/local/share/atom/resources/app/static/index.js:20:25)

Currently using linter-jscs & linter-jshint
Running on Ubuntu

@nwhite89
Copy link
Author

nwhite89 commented Oct 7, 2014

Any ideas?

@shawnacscott
Copy link

From the README:

spawn ENOENT or spawn ENOTDIR - A linter can't find a path to the executable. Try starting Atom from a shell via atom to make sure it gets your PATH. See also #102, #150.

That being said, I'm having a similar problem on save for css.scss files, as noted here

@nwhite89
Copy link
Author

nwhite89 commented Oct 7, 2014

I've done that multiple times, I always open atom from command line, I've tried it with no .jshintrc files as well. The error seems to be specific to linter rather than linter add-ons?

@postcasio
Copy link

The error line is:

if editorView.editor.getLastCursor()

Which sounds like the editor view doesn't have an editor instance. Which is weird. Could this be related to #224 maybe?

@nwhite89
Copy link
Author

It actually looks like my version of atom had got messed up

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