On Sat, Aug 4, 2012 at 6:59 AM, steveax <[email protected]> wrote:
> I'm trying to get jshint to work in BBEdit via a script. I've got node
> installed via Homebrew and have installed jshint via npm. […]
>
> But when I execute the script, I get:
>
> env: node: No such file or directory

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).

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.

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.

Cheers,
Terje

-- 
-- 
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