Maybe that's my problem. I'm using Octave Forge for Windows, which, as I
understand, implements Octave 3.2.4. Maybe in the next release this problem
will be fixed.
Thanks
-Original Message-
From: Juan Pablo Carbajal
Sent: Friday, March 04, 2011 1:42 PM
To: Hector Villa
Cc: octave-dev
On 4 Mar 2011, at 18:02, Philip Nienhuis wrote:
> Anyway, done, just posted the stuff to the package release forum.
> Hopefully all is OK now.
I update the web docs for io, thanks!
c.
--
What You Don't Know About Data C
On Fri, Mar 4, 2011 at 7:55 PM, Hector Villa wrote:
> Hi there,
> I'm new to Octave Forge so if this question has been answered before just
> point me to the right post. I did a quick search and could not find
> anything.
> My question is about the "filled" option to the scatter command.
> If I ty
Hi there,
I'm new to Octave Forge so if this question has been answered before just point
me to the right post. I did a quick search and could not find anything.
My question is about the "filled" option to the scatter command.
If I type
scatter ([1 2 3], [2 4 6], 12, [0 0 0])
There are no problem
Carlo:
c. wrote:
>
> On 3 Mar 2011, at 20:30, Philip Nienhuis wrote:
>
>> Sorry; but this ... (installing before generating the docs) isn't
>> mentioned in the developer's page on the octave-forge website.
>>
>> IMO perhaps it would be less confusing if generate_html.m could be pointed
>> t
On 03/03/2011 09:21 PM, Orion Poplawski wrote:
It has been suggested that the binary components of octave packages be
installed in /usr/lib{,64}/octave rather than /usr/libexec/octave.
This is what happens now for rpm installed Octave on my Fedora 14 x86_64
system:
[root@pbds ~]# ls -l /usr/li
