Jshint is not working for me on Windows XP but working fine from CLI?

[denica]

Hi, I followed all the intructions to get ready for using jshint on sublime.
When I use Ctrl-J, it does't throw me an error but whatever bad sintax I used on a javascript file it always shows me a [Finished] label with no errors at all. If I run the same file from jshint on the command line it gives me the sintax errors I expected.

Aparently the sublime console is telling me that everything is working fine.
Running jshint.cmd C:\Documents and Settings\denica\My Documents\Themeforest\Templates\HTML\js\script.js --reporter C:\Documents and Settings\denica\Application Data\Sublime Text 2\Packages\JSHint\reporter.js

I have installed node via the windows msi installer, and I have installed jshint just as the instructions says via "npm install -g jshint"

Is it a bug on my current stack or is it something that I'm doing wrong?

Best,
Demian.

[denica]

Updated extra info:

I also try to run the same command that the build is running with the --reporter modifier pointing to the reporter.js file and it works fine. I mean it gives me the errors I expected. Could it be a bug from Sublime?

[denica]

I just try to build a node.sublime-build just to test if the call to console.log was executing well from node and it was.

This is the small node.sublime-build that I created.
{
"cmd": ["node", "$file"]
}

And I build it (Ctrl+B) over a file that just have one test line - console.log ("Hello") -

I get the Hello message in the console as I expected.

Best!
Demian

[uipoet]

@denica I'm sorry but you are correct in that this is a bug in Sublime Text 2 for Windows. Please see #23.

You could help be adding your experience to the bug on the Sublime Text forums. I'm going to close this specific issue since it is redundant.