I have a few Text Filters that use node, so I don't think finding node is
the problem, assuming your #! path is correct. None of them will do
anything from the #! menu, however, because they rely on stdin and stdout
to receive input from BBEdit and return the result, and they're written in
JavaScript.
Have you tried something simple in JavaScript to test your installation? If
you've installed node in the usual location and haven't changed your script
output in BBEdit from the default setting, this should write "Hello,
world." to the script output window:
#!/usr/local/bin/node
process.stdout.write("Hello, world.");
On Friday, September 14, 2012 5:37:09 PM UTC-4, John Maxwell wrote:
>
> Syntax highlighting seems to work great, but the shebang "run" menu
> doesn't work with coffeescript. I put a #! path at the top of my
> coffeescript to get it to execute, but BBEdit fails when I run the script
> (env error) because it can't find node (which is in my shell path, but...)
>
> Is this misconfiguration on my part, or am I asking too much of BBEdit?
> That is, maybe BBEdit can't access the shell variables to make coffeescript
> work this way?
>
> Anyone with a different experience?
>
> Thx,
>
> -JMax
>
--
--
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>
