The manual (pdf page 304) says
Additionally, to execute scripts anywhere outside of BBEdit (e.g. in the
Terminal), the system requires that the script file have ‘execute’
permissions set. Thus, when you first save any script file which contains a
shebang (#!) line, BBEdit will
I don't know if this will fix your issue, since I haven't used Lion or BBE10
yet, but when I want to make a file executable, I have to remove the string
'TEXT' from the file type field. (I use Path Finder to do this—I don't
remember how you'd do this in the Finder or Terminal.) Give it a try.
At 23:26 -0700 7/20/11, TJ Luoma wrote:
The manual (pdf page 304) says
Additionally, to execute scripts anywhere outside of BBEdit (e.g. in the
Terminal), the system requires that the script file have 'execute'
permissions set. Thus, when you first save any script file which contains a
On 21 Jul 2011, at 7:10 AM, Doug McNutt wrote:
But what's worse: Try making a BBEdit worksheet executable the way I do it
with MPW.
Eh? Worksheet documents are XML, and must be expected to interleave commands
with their results. Why would you want/expect to execute them?
— F
--
At 08:44 -0500 7/21/11, Fritz Anderson wrote:
On 21 Jul 2011, at 7:10 AM, Doug McNutt wrote:
But what's worse: Try making a BBEdit worksheet executable the way I do it
with MPW.
Eh? Worksheet documents are XML, and must be expected to interleave commands
with their results. Why would you
On 21 Jul 2011, at 11:49 AM, Doug McNutt wrote:
I do it regularly here on OS 9. Interleaving occurs on the worksheet that
called the other worksheet to be executed in full. Of course OS 9 doesn't
have an executable bit. All text files are executable in MPW. One thing I
like to do is to
