On 2012-01-16 11:07-0700 Maurice LeBrun wrote:
> I looked into this the other day, last chance before upgrading to CentOS 6.x.
> Turns out the cmake configuration selects /usr/bin/gfortran under CentOS 5.7,
> so it seems no need to support g77 on that platform any more.
Good to know.
The rest of
On 2012-01-16 14:46-0700 Orion Poplawski wrote:
> - split has now be removed from octave in favor of strsplit:
>
> 6: error: `split' undefined near line 3 column 5
>
> I believe this has been raised before but was decided to stay with split at
> the time for octave 3.0 support.
Thanks for bringi
Two issues arose trying to build plplot with octave 3.6.0:
- octave needs to be passed "--no-window-system" if DISPLAY is not set, which
I need to due when building the fedora package. The attached patch allows me
to set the $otaveopts variable to do this.
- split has now be removed from oct
On 2012-01-16 11:37- Andrew Ross wrote:
> Alan,
>
> Many thanks for this! I've been slightly worried about this for some time
> so it's nice that you've found a neater solution.
>
> Your documentation changes missed out a tag though which caused octave
> documentation builds to fail. I've fixe
Not a bug at least according to original design. cmap1 is intended for
representing "continuous" data variation through a mapping of value to color,
cmap0 for more fixed elements like labels and axes. OTOH given a compelling
example of why/when/how you'd want to use cmap1 instead it might be wort
In the better late than never category..
On Sunday, November 6, 2011 at 18:40:01 (-0800) Alan W. Irwin writes:
> [snip]
> Which Fortran compiler (g77 or gfortran) do you use to build PLplot on
> CentOS 5.x? (Both the cmake output and output from "make VERBOSE=1"
> should tell you that.) I be
Is this actually a bug? Example 12 uses plcol1 to set the colour for the
boxes in a box chart, then plots text. The text comes out in the same
(cmap0) colour even though the boxes change colour. I've checked with
xwin / psc / wxwidgets / qt and cairo drivers and all seem to do the
same thing.
On Sat, Jan 14, 2012 at 04:04:52PM -0800, Alan Irwin wrote:
> On 2012-01-12 21:39-0800 Alan W. Irwin wrote:
>
> > However, I will change my mind if that swig idiosyncrasy ever
> > disappears so swig just deploys code fragments in the wrapper code in
> > the exact order of the argument list. In th
