Hello,
> #! /Applications/Octave.app/Contents/Resources/bin/octave
> disp('hello');
Is it just the space between #! and /App...? I know it shouldn't be, but
shells are sometimes quirky. On my Linux box, it works with or without
space, but I'm suspicious because Thomas' workaround do
Thanks Thomas -- works great.
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/
Rob Nicholas schrieb:
> Hello all,
>
> I'm in the process of trying to convert some of the Octave (and
> Matlab) scripts that I use on a regular basis into stand-alone
> executables, but I've been unable to get my scripts to run. For
> example, if I run the simple two-line script
>
> #! /
Hello all,
I'm in the process of trying to convert some of the Octave (and
Matlab) scripts that I use on a regular basis into stand-alone
executables, but I've been unable to get my scripts to run. For
example, if I run the simple two-line script
#! /Applications/Octave.app/Contents/Resou
tor, 10 04 2008 kl. 11:26 +0200, skrev Michael Goffioul:
> I committed small MSVC compilation fixes to the image package. Normally
> it should be equivalent to the previous code. As I don't understand the
> functionalitites, could anybody with some knowledge check I didn't
> screw up the functional
Hi,
I committed small MSVC compilation fixes to the image package. Normally
it should be equivalent to the previous code. As I don't understand the
functionalitites, could anybody with some knowledge check I didn't
screw up the functionality?
The modified files are __bilateral__.cc and __cordfltn
Just a further question, if the documentation is distributed as part of
the package itself under a GPL license then the only issue is the
inclusion of the fixed.texi and/or fixed.txi file within the package
tar-ball. The documentation is delivered with the source files where the
help strings ar
Rafael Laboissiere wrote:
>>> Also, the TeXinfo source file contains scraps that are extracted from other
>>> files (*.cc) distributed in the tarball. These files are released under
>>> GPL-2+. Does that constitute a violation of the GPL?
>>>
>> I can't identify which scraps were copied in
* MJ Ray <[EMAIL PROTECTED]> [2008-04-09 10:20]:
> Rafael Laboissiere <[EMAIL PROTECTED]> wrote:
> > [Please respect the M-F-T header when replying]
>
> Not visible on this client. Guessing. Please state wishes in body.
It was:
Mail-Followup-To: octave-dev@lists.sourceforge.net, [EMAIL PROTEC
