Re: Mac problem with octave.app and BBEdit

[Thomas Treichl]

Vic Norton schrieb:
> I have a problem with octave.app and BBEdit that just appeared when I 
> installed the 3.0.1 version of octave.app. Here's the problem.
>
> I have a script named "newLSPortf.m". It begins with the shebang line
>    #!/Applications/Octave.app/Contents/Resources/bin/octave
> Let's say the script is open in BBEdit.
>
> If I do
>    #! > Run in Terminal
> in BBEdit, then the script runs perfectly and I get some output in a 
> Terminal window.
>
> On the other hand, if I do
>    #! > Run
> in BBEdit, then I get then same output in a "Unix Script Output" window 
> followed by a list of warnings that all say the same thing:
>    warning: load_path: 
> ./Applications/Octave.app/Contents/Resources/share/octave/site/m: No 
> such file or directory
>
> This is definitely a problem between octave.app-3.0.1 and BBEdit. I have 
> just reinstalled octave.app-3.0.0 and the warning messages no longer 
> appear. BTW I am running BBEdit 8.7.2 on Mac OS X 10.4.11 PPC G5.
>
> Does anyone have any idea what might be causing this problem?
>
> Regards,
>
> Vic

Hi Vic,

this is strange. The only thing I can see in your message above is the 'dot' 
before '/Applications/...', ie. have a look in the 'current' directory for that 
path. If you 'currently' are not working in the 'root' path of your system then 
this message would make sense.

Otherwise, when you say it is not there with 3.0 but it comes with 3.0.1 then 
what might have been changed? I don't have any knowledge about BBEdit - don't 
have it installed. And some days ago we had a discussion about shebang lines, I 
don't get any *m file to run your way, the workaround on my 10.4.9 i386 is:

  #!/bin/sh /Applications/Octave.app/Contents/Resources/bin/octave

The discussion was

http://sourceforge.net/mailarchive/forum.php?thread_name=5c0c2c290804101146u6b3a3f19s34c00bb754c2c9be%40mail.gmail.com&forum_name=octave-dev

Oh, this could be an idea, try that shebang line instead, maybe this will help 
you because it does not depend on a relative path './Applications' ...

Regards,

  Thomas