On Saturday, August 4, 2012 12:41:21 AM UTC-7, Terje Bless wrote:
>
> That sounds like the environment for GUI apps has trouble finding node 
> itself (and since I'm guessing node is the "shell", the interpreter, 
> for the jshint script, that would prevent jshint from executing). This 
> is usually fixed by logging out and loging back in again (a reboot is 
> not necessary, but should have the same effect if you're uncertain). 
>

Logging out/in didn't fix things, but...
 

> If that doesn't work then you need to take a look at the #! line at 
> the top of jshint and try to work out from there where the problem 
> lies. Possibly node is incorrectly installed, or it expects a 
> particular directory (possibly a node-specific per-user configuration 
> or scripts directory) that isn't there, or something along those 
> lines. 
>

This seems to be the root of the issue. The !# line for hint:

#!/usr/bin/env node
 
Changing that to:

#!/usr/local/bin/node

Allows the script to run. Hacky, but working now.

As a general rule of thumb, when using commandline utilities and 
> scripts of various stripes that depend on the shell search path and 
> environment variables, and there is a difference (works/fails) between 
> the shell and GUI apps, then you've either forgotten to log out and in 
> again, or the "rc-file" (.bashrc and similar) that sets these 
> environment variables is not being run by the OS X GUI environment. 
>


Yes, something is screwy there. What I don't get though is how I can 
successfully run jshint /path/to/fil.js from a BBEdit Worksheet, but it 
fails when invoking a script.

Thanks for the reply,

-S

-- 
-- 
You received this message because you are subscribed to the 
"BBEdit Talk" discussion group on Google Groups.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
<http://groups.google.com/group/bbedit?hl=en>
If you have a feature request or would like to report a problem, 
please email "[email protected]" rather than posting to the group.
Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>



Reply via email to