search

AtomLinter / linter-cpplint

Linter plugin for c++, using cpplint
https://atom.io/packages/linter-cpplint
MIT License
6 stars 5 forks source link

plugin absolutely doing nothing #52

Closed biosmanager closed 8 years ago

biosmanager commented 8 years ago

I try to use this plugin but the problem is that it doesn't do anything, not linting, no output, no error on the debug console. When I run cpplint manually it works. I don't know what the problem is. I'm using Atom 1.7.4 with the latest version of the linter and linter-cpplint plugin.

Arcanemagus commented 8 years ago

If you place a breakpoint here is it ever being triggered?

biosmanager commented 8 years ago

I think the problem is that the script doesn't work with python3, only python2, but my default system python is python3. Could you add an option to configure the path to the python executable?

biosmanager commented 8 years ago

fixed it by linking python2 to the default python on my system

Arcanemagus commented 8 years ago

I'm not sure how an option for that would even be implemented anyway, all this package does is call cpplint, it's up to the user to make sure that cpplint itself works on the system.

Glad you got a solution figured out!

biosmanager commented 8 years ago

well i looked at init.coffee and made it work with python 2, all i needed to do is call exec with /usr/bin/python2 and the cpplint with it's parameters as argument (updateParameters pushes the cpplintPath in the array)

so i think if you would add an option to specify the python path it should work

Limero commented 8 years ago

I have the exact same problem, that nothing happens. @biosmanager are you also running Arch Linux? Or are there other distros that treats "python" as "python3"?

If this is an Arch Linux specific problem, maybe something could be done to check if the user is on Arch.

biosmanager commented 8 years ago

Yep, also Arch. But AFAIK there are other distros that have the same python problem. For now the best you can do is to edit the init.coffee script manually. I will post mine soon.

biosmanager commented 8 years ago

That's what I have in my init.coffee script:

http://pastebin.com/sgnjkaPN

An easy way for the package itself would be to give the user an option to specify the python binary manually. In my script I simply hard-coded python2 as the script interpreter.