gnuplot-beta — Developers and beta testers of new gnuplot code

plot using cbticlabels: an unfinished and undocumented feature

[Juhász P. <pet...@gm...>]

Hello,

I wanted to create a graph where tics on the colorbox are dynamically
generated from data. I vaguely recalled that there was a feature for
that, and it seemed logical that if there is {x|y}[2]ticlabels() to
place tics on the main axes, there should be a cbticlabels to do the
same for the colorbox.

It seems that this is valid syntax, as the parser accepts it, and I've
found the code responsible for it in the source, but it appears to be
undocumented, and there are no demos for it either.

It also appears to be either half-finished or buggy. A straightforward
invocation of `plot fn u 1:2:3:cbticlabels(4)` doesn't work, all tics
are placed at position 0 (so in effect there is only one tic label, the
last placed). I have to write `plot fn u 1:2:3:3:cbticlabels(4)`,
because the tic positions come from the 4th column specification. I see
in the source that this is hardcoded with a FIXME comment.

This behavior is problematic because it's confusing and goes against
expectations, and it produces incorrect results when there are multiple
variable specifications in the plot command (`ps var pt var lc pal`),
or with plot styles that reserve the fourth column for something else
already.
See the attached data file and gnuplot script for a self-contained
example.

The fix, at least from the user's perspective, seems simple: make
cbticlabels use the same column that is used for the color data itself.
>From the developer's perspective, I realize that this might be hard,
because we don't yet know which column to use at the time of parsing
the using spec, because an unknown number of `xxx variable` statements
may come later.

Or - `help pointsize variable` states that variable color is alwasy
taken from the last additional column. That we do know.

Best regards,
Peter Juhasz

Re: Plotting contours together with 'with image' data

[Dima K. <gn...@di...>]

sfeam <sf...@us...> writes:

> I think you are mis-interpreting the normal operation of PM3D as
> interpolation.  PM3D operates on quadrangles.  Each quadrangle has
> four corners.  Each corner has a color.   What color should be used for
> the quadrangle?   There are many choices and the command that selects one
> of the options is
>
>     set pm3d corners2color
> 		{ mean|geomean|harmean|rms|median|min|max|c1|c2|c3|c4 }
>
> The default option is "mean", and I guess that is what you are calling
> interpolation.  If you want each grid point in your original data to
> be the sole color source for a pm3d quadrangle ("pixel" if you are
> thinking of this as an image) then you want
>    set pm3d corners2color c1     (or c2 or c3 or c4)

Aha. Yes. That does sorta what I want. Except it shifts the image by 0.5
pixels in each direction. I understand why, but it's not ideal.


>> >> is there overhead for using pm3d in this case? Size? Speed? If there's
>> >> no overhead, can 'splot with image' simply map to 'splot with pm3d'?
>
> Many of the output devices can handle image data as a special case.
> The corresponding gnuplot driver can define a rectangular area and then
> pass only an array of color values to the device.  This is obviously a much
> smaller output stream than if the driver must output separate coordinates
> and color information for every pixel.  So in general the size of the
> output stream increases in the order
>
>    "with image" < "with pm3d" ~= "with image pixels"

OK. I forgot "with image pixels" existed. And just found an unrelated
(likely) bug: plotting the test data in this thread "with image" and
"with image pixels" produces slightly different images: the "with image"
version has each pixel centered not-quite at the correct locations. I
bet there's an off-by-one error in the "with image" code that makes the
coordinate mapping off slightly. I'll try to look at it when I get the
chance.


> I am thinking that we could use the command
>
>     set pm3d {explicit|implicit}
>
> as a model for opt-in contours.  As it is now, "set contours" causes
> all subsequent plots to use contours unless they cannot be contoured
> or they opt out with "nocontour".  This is the equivalent of the
> state produced by "set pm3d implicit".   It might work to add a command
> "set contours explicit" as we have for pm3d, meaning that subsequent
> plots are only contoured if they use an explicit plot style "contours".
>
> I don't think such a change would allow you to create any plot that you
> cannot already create, but perhaps making "set pm3d" and "set contours"
> more similar would be easier them both easier to understand.
> What do you think?

I think that extra bit of user control would definitely be welcome.

Thanks.
dima

Re: Plotting contours together with 'with image' data

[sfeam <sf...@us...>]

On Saturday, 21 July 2018 16:49:32 sfeam via gnuplot-beta wrote:
> On Saturday, 21 July 2018 12:29:32 Dima Kogan wrote:

> > Yeah, this is an unfortunate consequence of the way we set up our
> > interface. Ideally, you'd specify the contour options per plot:
> > 
> >   splot A with lines contours, B with image contours, C with vectors
> >
> > Changing this retroactively is probably more trouble than it's worth.
> 
> Right.  The historical design for several of gnuplot's plotting modes
> was an all-or-nothing toggle.  "set hidden3d"  "set pm3d" "set contours".
> The code evolved to allow you to opt out of the global settings for
> individual plot components.  E.g.
> 
>    set hidden3d
>    splot FOO, BAZ with labels nohidden3d
> 
> guarantees that the labels in BAZ will not be obscured by the surface
> drawn for FOO.
> And for contours:
> 
>    set contour surface
>    splot  f(x,y),  g(x,y) nocontour, h(x,y) nosurface
> 
> produces a plot in which f() gets both surface and contours,
> g() gets surface only, and h() gets contours only.
> 
> pm3d evolved slightly differently. Instead of requiring a global
> setting and allowing plot components to opt out,  we now allow
> individual plot components to opt in by using the style "with pm3d".
> Yeah that's a bit inconsistent.  You might logically expect there to
> be a "nopm3d" option, but there isn't.

I am thinking that we could use the command

    set pm3d {explicit|implicit}

as a model for opt-in contours.  As it is now, "set contours" causes
all subsequent plots to use contours unless they cannot be contoured
or they opt out with "nocontour".  This is the equivalent of the 
state produced by "set pm3d implicit".   It might work to add a command
"set contours explicit" as we have for pm3d, meaning that subsequent
plots are only contoured if they use an explicit plot style "contours".

I don't think such a change would allow you to create any plot that you
cannot already create, but perhaps making "set pm3d" and "set contours"
more similar would be easier them both easier to understand.
What do you think?    

	Ethan

Re: Plotting contours together with 'with image' data

[sfeam <sf...@us...>]

On Saturday, 21 July 2018 12:29:32 Dima Kogan wrote:
> Thanks Karl-Friedrich, Ethan for the suggestions.
> 
> These both sound like they work, but they also sound like workarounds
> instead of solutions. I have already found an ugly workaround that
> works: splot the same data twice: once 'with image' (for the colormap)
> and again 'with lines nosurface' (for the contours).
> 
> Comments inline.
> 
> 
> Ethan A Merritt <sf...@us...> writes:
> 
> > On Wednesday, July 18, 2018 12:37:17 PM PDT Dima Kogan wrote:
> >> Hi. I have a matrix data set, and I'd like to plot it using colors (with
> >> image), AND I'd like to overlay contours on top. This apparently does
> >> not work.
> >>
> >> It looks like 3d 'with image' plots use the data values for colors, but
> >> NOT for z. I.e. you get a colored image at z=0. Since it looks like
> >> contours read the z coordinate to do their thing, this doesn't work.
> >
> > I will try to explain why "with image" is not a plot style that can be
> > contoured.
> >
> > Consider a typical image file: PNG or GIF or JPEG or whatever.
> > It contains red/green/blue and maybe alpha values for each pixel.
> > But no z.  Where would you get a z value from?
> >
> > <snip>
> >
> > Now it is true that gnuplot's "with image" mode can be used for
> > gridded data where the color information is generated by
> > index lookup from gnuplot's own continuous color palette.
> > I guess that's what you are doing, but it is certainly not the general case.
> 
> In all my experience, I've used 'with rgbimage' for image files (.png,
> .jpg, ...) and 'with image' for gridded data. And 'help image' describes
> the gridded data use case first, and at least this suggests that this
> isn't some sort of side-feature.

It's not a side-feature.  It is a method for plotting color-indexed
images, e.g. GIF or non-truecolor PNG.   But indexed color is not the
same thing as "z values".  There are no z values in a GIF file.


> >> pm3d is intended for irregularly-sampled data (as I understand it)
> >
> > Not really. pm3d is a coloring algorithm that can be applied to
> > anything constructured from quadrangles. Typically this is a regularly
> > gridded surface. There are also options for interpolating an
> > irregularly sampled data set to generate a regular grid that can then
> > be colored (see "help dgrid3d"). But it sounds like your case doesn't
> > need any extra step to regularize the grid.
> 
> Without extra options pm3d was re-interpolating my data in some way, so
> its results weren't the same as 'with image'. And it's doing something
> different internally, and ends up producing bigger (and presumably less
> efficient) output.

I think you are mis-interpreting the normal operation of PM3D as
interpolation.  PM3D operates on quadrangles.  Each quadrangle has
four corners.  Each corner has a color.   What color should be used for
the quadrangle?   There are many choices and the command that selects one
of the options is 

    set pm3d corners2color 
		{ mean|geomean|harmean|rms|median|min|max|c1|c2|c3|c4 }

The default option is "mean", and I guess that is what you are calling
interpolation.  If you want each grid point in your original data to
be the sole color source for a pm3d quadrangle ("pixel" if you are
thinking of this as an image) then you want
   set pm3d corners2color c1     (or c2 or c3 or c4)

  
> >> is there overhead for using pm3d in this case? Size? Speed? If there's
> >> no overhead, can 'splot with image' simply map to 'splot with pm3d'?

Many of the output devices can handle image data as a special case.
The corresponding gnuplot driver can define a rectangular area and then
pass only an array of color values to the device.  This is obviously a much
smaller output stream than if the driver must output separate coordinates
and color information for every pixel.  So in general the size of the
output stream increases in the order

   "with image" < "with pm3d" ~= "with image pixels"

> >> If nothing else, can we barf instead of silently not rendering the
> >> contours in the 'with image' case?
> >
> > The more common complaint is that too many error messages
> > are printed for things that are not fatal errors.
> > Consider a hypothetical plot that includes some contours, some image data,
> > and some other stuff:
> >
> >     set contour
> >     splot A with lines, B with image, C with vectors
> >
> > The result is a plot with contours for A and no contours for B or C.
> > What would be the benefit of spewing errors or failing just because
> > B and C are plotted using styles that cannot be contoured?
> 
> Yeah, this is an unfortunate consequence of the way we set up our
> interface. Ideally, you'd specify the contour options per plot:
> 
>   splot A with lines contours, B with image contours, C with vectors
>
> Changing this retroactively is probably more trouble than it's worth.

Right.  The historical design for several of gnuplot's plotting modes
was an all-or-nothing toggle.  "set hidden3d"  "set pm3d" "set contours".
The code evolved to allow you to opt out of the global settings for
individual plot components.  E.g.

   set hidden3d
   splot FOO, BAZ with labels nohidden3d

guarantees that the labels in BAZ will not be obscured by the surface
drawn for FOO.
And for contours:

   set contour surface
   splot  f(x,y),  g(x,y) nocontour, h(x,y) nosurface

produces a plot in which f() gets both surface and contours,
g() gets surface only, and h() gets contours only.

pm3d evolved slightly differently. Instead of requiring a global
setting and allowing plot components to opt out,  we now allow
individual plot components to opt in by using the style "with pm3d".
Yeah that's a bit inconsistent.  You might logically expect there to
be a "nopm3d" option, but there isn't.

   
> OK. Let me look at the code and see if I can make 'with image' do what I
> think it should do. Don't know when I'll get to it, but that will make
> this into a more concrete discussion.

It _cannot_ do what you want, because in general image data does not come
with z values.

	Ethan

> 
> dima

Re: Plotting contours together with 'with image' data

[Dima K. <gn...@di...>]

Thanks Karl-Friedrich, Ethan for the suggestions.

These both sound like they work, but they also sound like workarounds
instead of solutions. I have already found an ugly workaround that
works: splot the same data twice: once 'with image' (for the colormap)
and again 'with lines nosurface' (for the contours).

Comments inline.


Ethan A Merritt <sf...@us...> writes:

> On Wednesday, July 18, 2018 12:37:17 PM PDT Dima Kogan wrote:
>> Hi. I have a matrix data set, and I'd like to plot it using colors (with
>> image), AND I'd like to overlay contours on top. This apparently does
>> not work.
>>
>> It looks like 3d 'with image' plots use the data values for colors, but
>> NOT for z. I.e. you get a colored image at z=0. Since it looks like
>> contours read the z coordinate to do their thing, this doesn't work.
>
> I will try to explain why "with image" is not a plot style that can be
> contoured.
>
> Consider a typical image file: PNG or GIF or JPEG or whatever.
> It contains red/green/blue and maybe alpha values for each pixel.
> But no z.  Where would you get a z value from?
>
> <snip>
>
> Now it is true that gnuplot's "with image" mode can be used for
> gridded data where the color information is generated by
> index lookup from gnuplot's own continuous color palette.
> I guess that's what you are doing, but it is certainly not the general case.

In all my experience, I've used 'with rgbimage' for image files (.png,
.jpg, ...) and 'with image' for gridded data. And 'help image' describes
the gridded data use case first, and at least this suggests that this
isn't some sort of side-feature.


>> If I plot 'with lines', I get contours. I can also plot 'with pm3d',
>> which produces a color AND a z-coordinate, so contours work then.
>>
>> Questions:
>>
>> It makes no sense to me that 'with image' 3d plots are stuck at z=0.
>> Does ANYBODY want that?
>
> They are not stuck at z=0.  See for example plots 6-8 of the image2 demo:
>
>       http://gnuplot.sourceforge.net/demo_5.2/image2.html

All right. If I specify something like "rotate", will I get contours? If
not, then I claim that this is surprising to the user, and is thus a
bug. My fundamental complaint is this:

  splot "something" with pm3d

gives me contours. 'with lines' and 'with points' give me contours.
'with image' does NOT give me contours. Silently. To a USER who doesn't
know or care about the gnuplot internals this is a bug.


>> Can we apply the values to color AND z in this
>> case? Is this hard, or is there some specific reason we're doing it the
>> way we're doing it?
>>
>> pm3d is intended for irregularly-sampled data (as I understand it)
>
> Not really. pm3d is a coloring algorithm that can be applied to
> anything constructured from quadrangles. Typically this is a regularly
> gridded surface. There are also options for interpolating an
> irregularly sampled data set to generate a regular grid that can then
> be colored (see "help dgrid3d"). But it sounds like your case doesn't
> need any extra step to regularize the grid.

Without extra options pm3d was re-interpolating my data in some way, so
its results weren't the same as 'with image'. And it's doing something
different internally, and ends up producing bigger (and presumably less
efficient) output.


>> is there overhead for using pm3d in this case? Size? Speed? If there's
>> no overhead, can 'splot with image' simply map to 'splot with pm3d'?
>
> In gnuplot version 5 you can tell pm3d to use a pre-calculated
> RGB color for each grid point.  This RGB value must be in the form of
> a 24-bit packed RGB integer.   I don't know exactly what  the nature of
> the values in your matrix so I cannot provide exact instructions,
> but in essence the command sequence would be
>
>   set pm3d border lc rgb variable
>   set style fill solid 1.0
>   splot $DATA using 1:2:3:(rgbfunc($3)) with pm3d
>
> It is up to you to define rgbfunc() appropriately.
> Here is an example using a regularly sampled grid and a constant
> color value:
>
>   set xrange [-2:2]
>   set yrange [-2:2]
>   set sample 20
>   set isosample 20
>
>   splot '++' using 1:2:(cos(y)*sin(x)):(int(0xdd77aa)) with pm3d
>
> But your special case may not require any of that.
> If the "z" values on a regular grid are to be used also as a  palette
> index then indeed the default pm3d settings may be sufficient.

Thanks for the example. I'll keep this usage in mind for the future, but
it's not applicable to my immediate use case: I have 1-dimensional
values, so the default gnuplot colormapping is what I want.


>> If nothing else, can we barf instead of silently not rendering the
>> contours in the 'with image' case?
>
> The more common complaint is that too many error messages
> are printed for things that are not fatal errors.
> Consider a hypothetical plot that includes some contours, some image data,
> and some other stuff:
>
>     set contour
>     splot A with lines, B with image, C with vectors
>
> The result is a plot with contours for A and no contours for B or C.
> What would be the benefit of spewing errors or failing just because
> B and C are plotted using styles that cannot be contoured?

Yeah, this is an unfortunate consequence of the way we set up our
interface. Ideally, you'd specify the contour options per plot:

  splot A with lines contours, B with image contours, C with vectors

Changing this retroactively is probably more trouble than it's worth.

OK. Let me look at the code and see if I can make 'with image' do what I
think it should do. Don't know when I'll get to it, but that will make
this into a more concrete discussion.

dima

Re: Plotting contours together with 'with image' data

[Ethan A M. <sf...@us...>]

On Wednesday, July 18, 2018 12:37:17 PM PDT Dima Kogan wrote:
> Hi. I have a matrix data set, and I'd like to plot it using colors (with
> image), AND I'd like to overlay contours on top. This apparently does
> not work.
> 
> It looks like 3d 'with image' plots use the data values for colors, but
> NOT for z. I.e. you get a colored image at z=0. Since it looks like
> contours read the z coordinate to do their thing, this doesn't work.

I will try to explain why "with image" is not a plot style that can be
contoured.

Consider a typical image file: PNG or GIF or JPEG or whatever.
It contains red/green/blue and maybe alpha values for each pixel.
But no z.  Where would you get a z value from?

It is true that PNG or GIF can also encode indexed color.
But the sequentially indexed color values do not necessarily correspond
to a continuous palette like the ones that gnuplot can generate.
So the matrix of index values is not generally something that can
be meaningfully contoured. 

Now it is true that gnuplot's "with image" mode can be used for 
gridded data where the color information is generated by
index lookup from gnuplot's own continuous color palette.
I guess that's what you are doing, but it is certainly not the general case.

> If I plot 'with lines', I get contours. I can also plot 'with pm3d',
> which produces a color AND a z-coordinate, so contours work then.
> 
> Questions:
> 
> It makes no sense to me that 'with image' 3d plots are stuck at z=0.
> Does ANYBODY want that? 

They are not stuck at z=0.  See for example plots 6-8 of the image2 demo:

      http://gnuplot.sourceforge.net/demo_5.2/image2.html
    
> Can we apply the values to color AND z in this
> case? Is this hard, or is there some specific reason we're doing it the
> way we're doing it?
> 
> pm3d is intended for irregularly-sampled data (as I understand it)

Not really. pm3d is a coloring algorithm that can be applied to anything
constructured from quadrangles.  Typically this is a regularly gridded surface.
There are also options for interpolating an irregularly sampled data set to
generate a regular grid that can then be colored (see "help dgrid3d"). 
But it sounds like your case doesn't need any extra step to regularize the grid.

> is there overhead for using pm3d in this case? Size? Speed? If there's
> no overhead, can 'splot with image' simply map to 'splot with pm3d'?

In gnuplot version 5 you can tell pm3d to use a pre-calculated
RGB color for each grid point.  This RGB value must be in the form of
a 24-bit packed RGB integer.   I don't know exactly what  the nature of
the values in your matrix so I cannot provide exact instructions,
but in essence the command sequence would be

  set pm3d border lc rgb variable
  set style fill solid 1.0
  splot $DATA using 1:2:3:(rgbfunc($3)) with pm3d

It is up to you to define rgbfunc() appropriately.
Here is an example using a regularly sampled grid and a constant
color value:

  set xrange [-2:2]
  set yrange [-2:2]
  set sample 20
  set isosample 20

  splot '++' using 1:2:(cos(y)*sin(x)):(int(0xdd77aa)) with pm3d

But your special case may not require any of that.
If the "z" values on a regular grid are to be used also as a  palette
index then indeed the default pm3d settings may be sufficient.

> If nothing else, can we barf instead of silently not rendering the
> contours in the 'with image' case?

The more common complaint is that too many error messages
are printed for things that are not fatal errors.
Consider a hypothetical plot that includes some contours, some image data,
and some other stuff:

    set contour
    splot A with lines, B with image, C with vectors

The result is a plot with contours for A and no contours for B or C.  
What would be the benefit of spewing errors or failing just because
B and C are plotted using styles that cannot be contoured?

	Ethan


> Thanks!
> 
>

Re: Plotting contours together with 'with image' data

[Dima K. <gn...@di...>]

Dima Kogan <gn...@di...> writes:

> It makes no sense to me that 'with image' 3d plots are stuck at z=0.
> Does ANYBODY want that? Can we apply the values to color AND z in this
> case? Is this hard, or is there some specific reason we're doing it the
> way we're doing it?
>
> pm3d is intended for irregularly-sampled data (as I understand it), so
> is there overhead for using pm3d in this case? Size? Speed? If there's
> no overhead, can 'splot with image' simply map to 'splot with pm3d'?

I just answered some of this. Plotting to a pdf, the pmd3d files are 70%
larger. And it looks like pm3d re-interpolated the original data, which
I don't want, and which shouldn't be needed, since I already have
regularly-spaced matrix data.

So the question that remains is the one about making 'with image'
produce colors AND z

Plotting contours together with 'with image' data

[Dima K. <gn...@di...>]

Hi. I have a matrix data set, and I'd like to plot it using colors (with
image), AND I'd like to overlay contours on top. This apparently does
not work.

It looks like 3d 'with image' plots use the data values for colors, but
NOT for z. I.e. you get a colored image at z=0. Since it looks like
contours read the z coordinate to do their thing, this doesn't work.

If I plot 'with lines', I get contours. I can also plot 'with pm3d',
which produces a color AND a z-coordinate, so contours work then.

Questions:

It makes no sense to me that 'with image' 3d plots are stuck at z=0.
Does ANYBODY want that? Can we apply the values to color AND z in this
case? Is this hard, or is there some specific reason we're doing it the
way we're doing it?

pm3d is intended for irregularly-sampled data (as I understand it), so
is there overhead for using pm3d in this case? Size? Speed? If there's
no overhead, can 'splot with image' simply map to 'splot with pm3d'?

If nothing else, can we barf instead of silently not rendering the
contours in the 'with image' case?

I'm attaching a sample data file.

Thanks!

5.2.4 windows binaries is updated.

[Tatsuro M. <tma...@ya...>]

I have made a mistake to place fonts directory in 5.2.4 windows binary 

packages.

The corrected packages are now available from source forge site.

Tatsuro

Re: [PATCH] aqua: correctly change font in enhanced mode

[Ethan A M. <sf...@us...>]

On Thursday, July 5, 2018 6:18:40 PM PDT Jun T wrote:
> A revised patch is attached.

Applied for 5.2 and 5.3

	thanks

		Ethan

[PATCH] fix bugs found by compiler (clang)

[Jun T <tak...@kb...>]

I get several warnings while building on macOS by using clang, and I've found
some of them are not just warnings but bugs:

datafile.c:2145:44: warning: using floating point absolute value function 'fabs' when argument is of integer type [-Wabsolute-value]
                    if (undefined || (a.type == CMPLX && fabs(imag(&a) > zero))) {
                                                         ^
# should be fabs(imag(&a)) > zero

plot2d.c:652:44: warning: implicit conversion from enumeration type 'enum DATA_TYPES' to different enumeration type 'enum coord_type' [-Wenum-conversion]
        current_plot->points[i].type = (j == 0) ? NOTDEFINED : INRANGE;
                                     ~            ^~~~~~~~~~
# 'enum coord_type' has UNDEFINED, not NOTDEFINED

../term/caca.trm:1696:12: warning: use of logical '&&' with constant operand [-Wconstant-logical-operand]
        if ((head && BOTH_HEADS) != 0) {
                  ^  ~~~~~~~~~~
# should be a single &

I believe these three are bugs.
The following two are not bugs but better to be "fixed":

mouse.c:514:13: warning: format string is not a string literal (potentially insecure) [-Wformat-security]
        sprintf(s, readout.v.string_val);
                   ^~~~~~~~~~~~~~~~~~~~

../term/pstricks.trm:1079:49: warning: the value of the size argument in 'strncat' is too large, might lead to a buffer overflow [-Wstrncat-size]
            strncat(patfill, ",fillcolor=PST@BGCOLOR", sizeof(patfill));
                                                       ^~~~~~~~~~~~~~~

The next one is not a problem but the waring can be easily silenced:

plot3d.c:1041:40: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]
            } else if ((this_plot->plot_style == CIRCLES)) {
                        ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~

Jun

Re: [PATCH] aqua: correctly change font in enhanced mode

[Jun T <tak...@kb...>]

A revised patch is attached.

> 2018/07/06 2:41, Ethan A Merritt <me...@uw...> wrote:
> 
> I notice only:
>   - gnuplot style has been to follow C rules and place declarations
>     only at the top of a block

Sorry, I thought it was OK because aquaterm.trm is in Objective-C.

>   - needs free(s) at line 227

Yes, indeed.

>     They should be reset if the
> plot window size is changed interactively using the mouse but not for
> font changes.

Thanks.
I had no idea what v_tic/h_tic were for. I just guessed it need be reset
from the comments in wxt_gui.cpp (line 2438) and gp_cairo.c (line 1916).
It seems gp_cairo_set_termvar() had a code to reset v_tic/h_tic but it
was removed long time ago. Only old comments remain.


Jun

Re: [PATCH] aqua: correctly change font in enhanced mode

[Ethan A M. <me...@uw...>]

On Thursday, July 5, 2018 6:15:47 AM PDT Jun T wrote:
> [Problem]
> aqua terminal has a problem in setting font for each label (or title etc.)
> if enhanced mode is in use. For example, if I run
> 
> gnuplot> set term aqua font "Times,16"
> gnuplot> label 1 "A_{ij}" at 0,0 font "Arial,30"
> gnuplot> plot sin(x)
> 
> then A_{ij} is drawn in the default font "Times", although the size is
> correct (i.e., 30). If "A_{ij}" is replaced by "A" (no enhanced mode)
> then it is drawn in the specified font "Arial".
> 
> The problem is, in enhanced mode, ENHAQUA_put_text() calls
> enhanced_recursion() with fontname=AQUA_fontNameCur (because
> ENHAQUA_put_text() does not know the correct font for the current label),
> but AQUA_fontNameCur has not been set by AQUA_set_font() (which is
> called just before ENHAQUA_put_text()).
> 
> [A Possible Patch]
> In the attached patch, AQUA_set_font() is rewritten so that it takes
> care of AQUA_fontNameCur properly. The variable AQUA_fontNameDef was there
> but not used anywhere, so I used it to save the default font name.
> AQUA_set_font("name") will set AQUA_fontNameCur to "name", and
> AQUA_set_font("") will reset AQUA_fontNameCur to AQUA_fontNameDef.
> 
> AQUA_fontNameDef (and AQUA_fontNameCur also) is set in AQUA_options()
> (i.e., 'set term aqua font "name"' or 'set termoption font "name"').
> 
> I introduced two helper functions to simplify the code.
> 
> [Is this OK?]

Looks OK to me.  I don't have an OSX machine to try it on.
I notice only:
   - gnuplot style has been to follow C rules and place declarations
     only at the top of a block
   - needs free(s) at line 227
   - see below

> In the helper function set_font_size(), h_tic and v_tic are also reset.
> Before the patch, they were reset only in AQUA_init(), but I *guess*
> they need be reset every time font size changes. Is there any test case
> in which not resetting h_tic/v_tic causes a problem?

These are used by the core code to reserve space in the plot margins for
outward-facing tics.  Also the ratio  v_tic/h_tic is used to calculate the
aspect ration of the plot. Neither of those space requirements change 
with the font size, so h_tic and v_tic should be set initially in term->() or 
term->options() when the size is specified.  They should be reset if the
plot window size is changed interactively using the mouse but not for
font changes.

Can you send a revised patch when there has been a chance for 
feedback also from people using aquaterm?

	thanks

		Ethan

> 
> Jun
> 
> 

[PATCH] aqua: correctly change font in enhanced mode

[Jun T <tak...@kb...>]

[Problem]
aqua terminal has a problem in setting font for each label (or title etc.)
if enhanced mode is in use. For example, if I run

gnuplot> set term aqua font "Times,16"
gnuplot> label 1 "A_{ij}" at 0,0 font "Arial,30"
gnuplot> plot sin(x)

then A_{ij} is drawn in the default font "Times", although the size is
correct (i.e., 30). If "A_{ij}" is replaced by "A" (no enhanced mode)
then it is drawn in the specified font "Arial".

The problem is, in enhanced mode, ENHAQUA_put_text() calls
enhanced_recursion() with fontname=AQUA_fontNameCur (because
ENHAQUA_put_text() does not know the correct font for the current label),
but AQUA_fontNameCur has not been set by AQUA_set_font() (which is
called just before ENHAQUA_put_text()).

[A Possible Patch]
In the attached patch, AQUA_set_font() is rewritten so that it takes
care of AQUA_fontNameCur properly. The variable AQUA_fontNameDef was there
but not used anywhere, so I used it to save the default font name.
AQUA_set_font("name") will set AQUA_fontNameCur to "name", and
AQUA_set_font("") will reset AQUA_fontNameCur to AQUA_fontNameDef.

AQUA_fontNameDef (and AQUA_fontNameCur also) is set in AQUA_options()
(i.e., 'set term aqua font "name"' or 'set termoption font "name"').

I introduced two helper functions to simplify the code.

[Is this OK?]
In the helper function set_font_size(), h_tic and v_tic are also reset.
Before the patch, they were reset only in AQUA_init(), but I *guess*
they need be reset every time font size changes. Is there any test case
in which not resetting h_tic/v_tic causes a problem?

Jun

Aw: Windows compilation problems

[Bastian M. <bma...@we...>]

<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
<div>For MSYS2/MinGW64 you should use the Makefile in config/mingw - but your logs looks like you are trying the *nix configure &amp; make routine. That does not work (although we would accept patches to make that work, too).</div>

<div>&nbsp;</div>

<div>Please have look at the build instructions at</div>

<div>https://sourceforge.net/p/gnuplot/support-requests/199/</div>

<div>
<div>&nbsp;</div>

<div>Good luck,</div>

<div>&nbsp; Bastian</div>

<div>&nbsp;</div>

<div>&nbsp;</div>

<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Gesendet:</b>&nbsp;Dienstag, 12. Juni 2018 um 17:38 Uhr<br/>
<b>Von:</b>&nbsp;&quot;Kordani, Joshua&quot; &lt;jos...@gl...&gt;<br/>
<b>An:</b>&nbsp;&quot;gnu...@li...&quot; &lt;gnu...@li...&gt;<br/>
<b>Betreff:</b>&nbsp;Windows compilation errors</div>

<div name="quoted-content"><!--p.MsoNormal, li.MsoNormal, div.MsoNormal {
	margin: 0.0in;
	font-size: 11.0pt;
	font-family: Calibri , sans-serif;
}
a:link, span.MsoHyperlink {
	color: blue;
	text-decoration: underline;
}
a:visited, span.MsoHyperlinkFollowed {
	color: purple;
	text-decoration: underline;
}
span.EmailStyle17 {
	font-family: Calibri , sans-serif;
	color: windowtext;
}
*.MsoChpDefault {
	font-family: Calibri , sans-serif;
}
div.WordSection1 {
	page: WordSection1;
}
-->
<div>
<div class="WordSection1">
<p class="MsoNormal">Greetings all,</p>

<p class="MsoNormal">&nbsp;</p>

<p class="MsoNormal">I am attempting to build gnuplot from git on Windows 7 64bit using MinGW64 and receive the following error.&nbsp; Note that I have attempted to install the Microsoft html help sdk, but the installer tells me that a newer version is already installed.&nbsp; Any pointers would be greatly appreciated!</p>

<p class="MsoNormal">&nbsp;</p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">&#36; make -j</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make&nbsp; all-recursive</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[1]: Entering directory &#39;/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main&#39;</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">Making all in config</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[2]: Entering directory &#39;/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/config&#39;</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[2]: Nothing to be done for &#39;all&#39;.</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[2]: Leaving directory &#39;/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/config&#39;</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">Making all in m4</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[2]: Entering directory &#39;/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/m4&#39;</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[2]: Nothing to be done for &#39;all&#39;.</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[2]: Leaving directory &#39;/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/m4&#39;</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">Making all in term</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[2]: Entering directory &#39;/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/term&#39;</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[2]: Nothing to be done for &#39;all&#39;.</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[2]: Leaving directory &#39;/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/term&#39;</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">Making all in src</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[2]: Entering directory &#39;/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/src&#39;</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make&nbsp; all-recursive</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[3]: Entering directory &#39;/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/src&#39;</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">Making all in wxterminal</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[4]: Entering directory &#39;/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/src/wxterminal&#39;</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[4]: Nothing to be done for &#39;all&#39;.</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[4]: Leaving directory &#39;/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/src/wxterminal&#39;</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">Making all in qtterminal</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[4]: Entering directory &#39;/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/src/qtterminal&#39;</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[4]: Nothing to be done for &#39;all&#39;.</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[4]: Leaving directory &#39;/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/src/qtterminal&#39;</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[4]: Entering directory &#39;/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/src&#39;</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">depbase=&#96;echo command.o &#124; sed &#39;s&#124;[^/]*&#36;&#124;.deps/&amp;&#124;;s&#124;&#92;.o&#36;&#124;&#124;&#39;&#96;;&#92;</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">gcc -DHAVE_CONFIG_H -I. -I..&nbsp; -I../term -I../term -DBINDIR=&#92;&quot;/mingw64/bin&#92;&quot; -DX11_DRIVER_DIR=&#92;&quot;/mingw64/libexec/gnuplot/5.3&#92;&quot; -DQT_DRIVER_DIR=&#92;&quot;/mingw64/libexec/gnuplot/5.3&#92;&quot; -DGNUPLOT_SHARE_DIR=&#92;&quot;/mingw64/share/gnuplot/5.3&#92;&quot; -DGNUPLOT_PS_DIR=&#92;&quot;/mingw64/share/gnuplot/5.3/PostScript&#92;&quot; -DGNUPLOT_JS_DIR=&#92;&quot;/mingw64/share/gnuplot/5.3/js&#92;&quot; -DGNUPLOT_LUA_DIR=&#92;&quot;/mingw64/share/gnuplot/5.3/lua&#92;&quot; -DCONTACT=&#92;&quot;gnu...@li...&#92;&quot; -DHELPFILE=&#92;&quot;/mingw64/share/gnuplot/5.3/gnuplot.gih&#92;&quot; -DGNUPLOT_X11=&#92;&quot;&#96;echo gnuplot_x11 &#124; sed &#39;s,x,x,&#39;&#96;.exe&#92;&quot; -DXAPPLRESDIR=&#92;&quot;/etc/X11/app-defaults/&#92;&quot; -DGNUPLOT_QT=&#92;&quot;&#96;echo gnuplot_qt &#124; sed &#39;s,x,x,&#39;&#96;.exe&#92;&quot; -DQTGNUPLOT_DATA_DIR=&#92;&quot;/mingw64/share/gnuplot/5.3/qt&#92;&quot; -I/mingw64/include -mms-bitfields -IC:/msys64/mingw64/include/pango-1.0 -IC:/msys64/mingw64/include/fribidi -IC:/msys64/mingw64/include/cairo -IC:/msys64/mingw64/include/pixman-1 -IC:/msys64/mingw64/include -IC:/msys64/mingw64/include/freetype2 -IC:/msys64/mingw64/include -IC:/msys64/mingw64/include/harfbuzz -IC:/msys64/mingw64/include/glib-2.0 -IC:/msys64/mingw64/lib/glib-2.0/include -IC:/msys64/mingw64/include -IC:/msys64/mingw64/include/libpng16 -IC:/msys64/mingw64/include -mms-bitfields -IC:/msys64/mingw64/include/cairo -IC:/msys64/mingw64/include/pango-1.0 -IC:/msys64/mingw64/include/fribidi -IC:/msys64/mingw64/include/cairo -IC:/msys64/mingw64/include/pixman-1 -IC:/msys64/mingw64/include -IC:/msys64/mingw64/include/freetype2 -IC:/msys64/mingw64/include -IC:/msys64/mingw64/include/harfbuzz -IC:/msys64/mingw64/include/libpng16 -IC:/msys64/mingw64/include -IC:/msys64/mingw64/include/glib-2.0 -IC:/msys64/mingw64/lib/glib-2.0/include -IC:/msys64/mingw64/include -DQT_NETWORK_LIB -DQT_SVG_LIB -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -IC:/msys64/mingw64/include/QtNetwork -IC:/msys64/mingw64/include -IC:/msys64/mingw64/include/QtSvg -IC:/msys64/mingw64/include -IC:/msys64/mingw64/include/QtPrintSupport -IC:/msys64/mingw64/include -IC:/msys64/mingw64/include/QtWidgets -IC:/msys64/mingw64/include -IC:/msys64/mingw64/include/QtGui -IC:/msys64/mingw64/include -IC:/msys64/mingw64/include/QtCore -IC:/msys64/mingw64/include&nbsp; -g -O2 -MT command.o -MD -MP -MF &#36;depbase.Tpo -c -o command.o command.c &amp;&amp;&#92;</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">mv -f &#36;depbase.Tpo &#36;depbase.Po</span></p>

<p class="MsoNormal"><b><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">command.c:</span></b><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;"> In function &#39;<b>help_command</b>&#39;:</span></p>

<p class="MsoNormal"><b><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">command.c:3083:13:</span></b><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;"> <span style="color: rgb(255,64,255);">warning: </span>implicit declaration of function &#39;<b>help</b>&#39;; did you mean &#39;<b>Beep</b>&#39;? [<span style="color: rgb(255,64,255);">-Wimplicit-function-declaration</span>]</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">&nbsp;&nbsp;&nbsp;&nbsp; switch (<span style="color: rgb(255,64,255);">help</span>(helpbuf, help_ptr, &amp;subtopics)) {</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="color: rgb(255,64,255);">^~~~</span></span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="color: rgb(0,191,0);">Beep</span></span></p>

<p class="MsoNormal"><b><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">command.c:3084:10:</span></b><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;"> <span style="color: rgb(255,64,64);">error: </span>&#39;<b>H_FOUND</b>&#39; undeclared (first use in this function); did you mean &#39;<b>HFONT</b>&#39;?</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">&nbsp;&nbsp;&nbsp;&nbsp; case <span style="color: rgb(255,64,64);">H_FOUND</span>:{</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="color: rgb(255,64,64);">^~~~~~~</span></span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="color: rgb(0,191,0);">HFONT</span></span></p>

<p class="MsoNormal"><b><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">command.c:3084:10:</span></b><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;"> <span style="color: rgb(64,255,255);">note: </span>each undeclared identifier is reported only once for each function it appears in</span></p>

<p class="MsoNormal"><b><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">command.c:3114:10:</span></b><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;"> <span style="color: rgb(255,64,64);">error: </span>&#39;<b>H_NOTFOUND</b>&#39; undeclared (first use in this function); did you mean &#39;<b>H_FOUND</b>&#39;?</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">&nbsp;&nbsp;&nbsp;&nbsp; case <span style="color: rgb(255,64,64);">H_NOTFOUND</span>:</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="color: rgb(255,64,64);">^~~~~~~~~~</span></span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="color: rgb(0,191,0);">H_FOUND</span></span></p>

<p class="MsoNormal"><b><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">command.c:3117:10:</span></b><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;"> <span style="color: rgb(255,64,64);">error: </span>&#39;<b>H_ERROR</b>&#39; undeclared (first use in this function); did you mean &#39;<b>HTERROR</b>&#39;?</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">&nbsp;&nbsp;&nbsp;&nbsp; case <span style="color: rgb(255,64,64);">H_ERROR</span>:</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="color: rgb(255,64,64);">^~~~~~~</span></span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <span style="color: rgb(0,191,0);">HTERROR</span></span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[4]: *** [Makefile:910: command.o] Error 1</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[4]: Leaving directory &#39;/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/src&#39;</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[3]: *** [Makefile:969: all-recursive] Error 1</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[3]: Leaving directory &#39;/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/src&#39;</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[2]: *** [Makefile:644: all] Error 2</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[2]: Leaving directory &#39;/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/src&#39;</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[1]: *** [Makefile:426: all-recursive] Error 1</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make[1]: Leaving directory &#39;/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main&#39;</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">make: *** [Makefile:365: all] Error 2</span></p>

<p class="MsoNormal"><span style="font-size: 9.0pt;font-family: &quot;Lucida Console&quot;;">&nbsp;</span></p>
</div>
</div>
</div>
</div>
</div>
</div></div></body></html>

Windows compilation errors

[Kordani, J. <jos...@gl...>]

Greetings all,

I am attempting to build gnuplot from git on Windows 7 64bit using MinGW64 and receive the following error.  Note that I have attempted to install the Microsoft html help sdk, but the installer tells me that a newer version is already installed.  Any pointers would be greatly appreciated!

$ make -j
make  all-recursive
make[1]: Entering directory '/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main'
Making all in config
make[2]: Entering directory '/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/config'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/config'
Making all in m4
make[2]: Entering directory '/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/m4'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/m4'
Making all in term
make[2]: Entering directory '/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/term'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/term'
Making all in src
make[2]: Entering directory '/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/src'
make  all-recursive
make[3]: Entering directory '/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/src'
Making all in wxterminal
make[4]: Entering directory '/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/src/wxterminal'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/src/wxterminal'
Making all in qtterminal
make[4]: Entering directory '/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/src/qtterminal'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/src/qtterminal'
make[4]: Entering directory '/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/src'
depbase=`echo command.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
gcc -DHAVE_CONFIG_H -I. -I..  -I../term -I../term -DBINDIR=\"/mingw64/bin\" -DX11_DRIVER_DIR=\"/mingw64/libexec/gnuplot/5.3\" -DQT_DRIVER_DIR=\"/mingw64/libexec/gnuplot/5.3\" -DGNUPLOT_SHARE_DIR=\"/mingw64/share/gnuplot/5.3\" -DGNUPLOT_PS_DIR=\"/mingw64/share/gnuplot/5.3/PostScript\" -DGNUPLOT_JS_DIR=\"/mingw64/share/gnuplot/5.3/js\" -DGNUPLOT_LUA_DIR=\"/mingw64/share/gnuplot/5.3/lua\" -DCONTACT=\"gnu...@li...\" -DHELPFILE=\"/mingw64/share/gnuplot/5.3/gnuplot.gih\" -DGNUPLOT_X11=\"`echo gnuplot_x11 | sed 's,x,x,'`.exe\" -DXAPPLRESDIR=\"/etc/X11/app-defaults/\" -DGNUPLOT_QT=\"`echo gnuplot_qt | sed 's,x,x,'`.exe\" -DQTGNUPLOT_DATA_DIR=\"/mingw64/share/gnuplot/5.3/qt\" -I/mingw64/include -mms-bitfields -IC:/msys64/mingw64/include/pango-1.0 -IC:/msys64/mingw64/include/fribidi -IC:/msys64/mingw64/include/cairo -IC:/msys64/mingw64/include/pixman-1 -IC:/msys64/mingw64/include -IC:/msys64/mingw64/include/freetype2 -IC:/msys64/mingw64/include -IC:/msys64/mingw64/include/harfbuzz -IC:/msys64/mingw64/include/glib-2.0 -IC:/msys64/mingw64/lib/glib-2.0/include -IC:/msys64/mingw64/include -IC:/msys64/mingw64/include/libpng16 -IC:/msys64/mingw64/include -mms-bitfields -IC:/msys64/mingw64/include/cairo -IC:/msys64/mingw64/include/pango-1.0 -IC:/msys64/mingw64/include/fribidi -IC:/msys64/mingw64/include/cairo -IC:/msys64/mingw64/include/pixman-1 -IC:/msys64/mingw64/include -IC:/msys64/mingw64/include/freetype2 -IC:/msys64/mingw64/include -IC:/msys64/mingw64/include/harfbuzz -IC:/msys64/mingw64/include/libpng16 -IC:/msys64/mingw64/include -IC:/msys64/mingw64/include/glib-2.0 -IC:/msys64/mingw64/lib/glib-2.0/include -IC:/msys64/mingw64/include -DQT_NETWORK_LIB -DQT_SVG_LIB -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -IC:/msys64/mingw64/include/QtNetwork -IC:/msys64/mingw64/include -IC:/msys64/mingw64/include/QtSvg -IC:/msys64/mingw64/include -IC:/msys64/mingw64/include/QtPrintSupport -IC:/msys64/mingw64/include -IC:/msys64/mingw64/include/QtWidgets -IC:/msys64/mingw64/include -IC:/msys64/mingw64/include/QtGui -IC:/msys64/mingw64/include -IC:/msys64/mingw64/include/QtCore -IC:/msys64/mingw64/include  -g -O2 -MT command.o -MD -MP -MF $depbase.Tpo -c -o command.o command.c &&\
mv -f $depbase.Tpo $depbase.Po
command.c: In function 'help_command':
command.c:3083:13: warning: implicit declaration of function 'help'; did you mean 'Beep'? [-Wimplicit-function-declaration]
     switch (help(helpbuf, help_ptr, &subtopics)) {
             ^~~~
             Beep
command.c:3084:10: error: 'H_FOUND' undeclared (first use in this function); did you mean 'HFONT'?
     case H_FOUND:{
          ^~~~~~~
          HFONT
command.c:3084:10: note: each undeclared identifier is reported only once for each function it appears in
command.c:3114:10: error: 'H_NOTFOUND' undeclared (first use in this function); did you mean 'H_FOUND'?
     case H_NOTFOUND:
          ^~~~~~~~~~
          H_FOUND
command.c:3117:10: error: 'H_ERROR' undeclared (first use in this function); did you mean 'HTERROR'?
     case H_ERROR:
          ^~~~~~~
          HTERROR
make[4]: *** [Makefile:910: command.o] Error 1
make[4]: Leaving directory '/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/src'
make[3]: *** [Makefile:969: all-recursive] Error 1
make[3]: Leaving directory '/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/src'
make[2]: *** [Makefile:644: all] Error 2
make[2]: Leaving directory '/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main/src'
make[1]: *** [Makefile:426: all-recursive] Error 1
make[1]: Leaving directory '/c/Users/joshua.kordani/Code/gnuplot-gnuplot-main'
make: *** [Makefile:365: all] Error 2


This e-mail (including attached documents) may contain confidential or proprietary information intended only for use by the named recipient(s). Use by persons other than the named recipient(s), further dissemination, or copying of this email is prohibited unless authorized by the sender.

Re: Release 5.2.4

[Tatsuro M. <tma...@ya...>]

Windows binary packages are updated with correct gnuplot.pdf uploaded on the web.

Binary packages for Windows (64-bit)
    gp524-win64-mingw_1.7z      complete package (mingw)
    gp524-win64-mingw_1.exe     binary self-installer (mingw) 

Binary packages for Windows (32-bit)
    gp524-win32-mingw_1.7z      complete package (mingw)
    gp524-win32-mingw_1.exe     binary self-installer (mingw)

File names are changed from first uploaded ones (_1 is added). 

Tatsuro



----- Original Message -----
> From: Tatsuro MATSUOKA <tma...@ya...>
> To: Merritt Ethan <sf...@us...>; gnu...@li...
> Cc: 
> Date: 2018/6/6, Wed 13:21
> Subject: Re: Release 5.2.4
> 
> OK.
> 
> I understand. 
> 
> 
> However, windows binary packages now include gnuplot.pdf with incorrect version 
> number 
> because packaging system for windows uses pdf files generated from source.
> I can correct them manually.
> 
> Please allow me to make corrected windows binary packages and upload on the web.
> 
> Tatsuro
> 
> 
> 
> ----- Original Message -----
>>  From: sfeam <sf...@us...>
>>  To: gnu...@li...; Tatsuro MATSUOKA 
> <tma...@ya...>
>>  Cc: 
>>  Date: 2018/6/6, Wed 11:26
>>  Subject: Re: Release 5.2.4
>> 
>>  On Wednesday, 06 June 2018 10:06:39 Tatsuro MATSUOKA wrote:
>>>   Shigeharu Takeno found that
>>> 
>>> 
>>>   In docs/titlepag.tex in gnuplot-5.2.4.tar.gz
>>> 
>>> 
>>>   There described
>>> 
>>>   %  31 May 2017 Version 5.2
>>>      Version 5.2.3 (May 2018)
>>> 
>>>   gnuplot.pdf on SourceForge, the version number is 5.2.4 but source for 
> 
>>  document tar ball
>>>   is still 5.2.3.
>> 
>>  Yes. That is true.
>>  But the content of the manual (docs/gnuplot.doc) has not changed
>>  except for one sentence about the new ARGV array variable.
>> 
>>>   I propose to make a fixed tar ball named like gnuplot-5.2.4-1.tar.gz.
>> 
>>  In the past, people have complained about relabeling the source tarball
>>  or changing its content.  If a change is necessary, the policy is that
>>  we increment the patchlevel to create a new minor release version.
>>  But it seems unreasonable to create a release 5.2.5 only so that we
>>  can change the version stamp on the title page of the pdf documentation.
>> 
>>  By the way, the gnuplot.pdf on the download site itself correctly 
>>  lists version 5.2.4 on the title page.   I will make sure the copy
>>  linked on the main web page is correct also.
>> 
>>      Ethan
>> 
>> 
>>> 
>>>   Tatsuro
>>> 
>>> 
>>> 
>>>   ----- Original Message -----
>>>   > From: sfeam via gnuplot-beta 
>>  <gnu...@li...>
>>>   > To: gnu...@li...
>>>   > Cc: 
>>>   > Date: 2018/6/5, Tue 13:18
>>>   > Subject: Release 5.2.4
>>>   > 
>>>   > Release 5.2.4 source tarball is ready and can be downloaded from
>>>   > 
>>>   >    
>>>   > 
>> 
> https://sourceforge.net/projects/gnuplot/files/gnuplot/5.2.4/gnuplot-5.2.4.tar.gz
>>>   > 
>>>   > This release contains
>>>   > - a fix for a serious regression reported against 5.2.3 (spurious
>>>   >   evaluation of logscale coordinates as UNDEFINED)
>>>   > - re-implementation of the "refresh" command to correct 
> 
>>  regressions in
>>>   >   5.2.0 through 5.2.3
>>>   > - sanity checks for several invalid command sequences found by 
> fuzzing
>>>   > - several minor bug-fixes
>>>   > - two recent minor changes back-ported from the development 
> version
>>>   > 
>>>   > Yes it's only been a month since 5.2.3 but I think the 
> regression
>>>   > in plotting logscale axes is serious enough to warrant an 
> immediate 
>>  fix.
>>>   > If you want to test before/after here is a simple trigger for the 
> 
>>  error:
>>>   >     set log y
>>>   >     plot [1:100] x**2, 1/0
>>>   > 
>>>   > Windows binaries will follow eventually.
>>>   > 
>>>   >     happy gnuplotting
>>>   > 
>>>   >         Ethan
>>>   > 
>>>   > 
>> 
> ------------------------------------------------------------------------------
>>>   > Check out the vibrant tech community on one of the world's 
> most
>>>   > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>   > _______________________________________________
>>>   > gnuplot-beta mailing list
>>>   > gnu...@li...
>>>   > Membership management via: 
>>>   > https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
>>>   > 
>>> 
>>> 
>> 
> ------------------------------------------------------------------------------
>>>   Check out the vibrant tech community on one of the world's most
>>>   engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>   _______________________________________________
>>>   gnuplot-beta mailing list
>>>   gnu...@li...
>>>   Membership management via: 
>>  https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
>> 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> Membership management via: 
> https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
> 

Re: Release 5.2.4

[Tatsuro M. <tma...@ya...>]

OK.

I understand. 


However, windows binary packages now include gnuplot.pdf with incorrect version number 
because packaging system for windows uses pdf files generated from source.
I can correct them manually.

Please allow me to make corrected windows binary packages and upload on the web.

Tatsuro



----- Original Message -----
> From: sfeam <sf...@us...>
> To: gnu...@li...; Tatsuro MATSUOKA <tma...@ya...>
> Cc: 
> Date: 2018/6/6, Wed 11:26
> Subject: Re: Release 5.2.4
> 
> On Wednesday, 06 June 2018 10:06:39 Tatsuro MATSUOKA wrote:
>>  Shigeharu Takeno found that
>> 
>> 
>>  In docs/titlepag.tex in gnuplot-5.2.4.tar.gz
>> 
>> 
>>  There described
>> 
>>  %  31 May 2017 Version 5.2
>>     Version 5.2.3 (May 2018)
>> 
>>  gnuplot.pdf on SourceForge, the version number is 5.2.4 but source for 
> document tar ball
>>  is still 5.2.3.
> 
> Yes. That is true.
> But the content of the manual (docs/gnuplot.doc) has not changed
> except for one sentence about the new ARGV array variable.
> 
>>  I propose to make a fixed tar ball named like gnuplot-5.2.4-1.tar.gz.
> 
> In the past, people have complained about relabeling the source tarball
> or changing its content.  If a change is necessary, the policy is that
> we increment the patchlevel to create a new minor release version.
> But it seems unreasonable to create a release 5.2.5 only so that we
> can change the version stamp on the title page of the pdf documentation.
> 
> By the way, the gnuplot.pdf on the download site itself correctly 
> lists version 5.2.4 on the title page.   I will make sure the copy
> linked on the main web page is correct also.
> 
>     Ethan
> 
> 
>> 
>>  Tatsuro
>> 
>> 
>> 
>>  ----- Original Message -----
>>  > From: sfeam via gnuplot-beta 
> <gnu...@li...>
>>  > To: gnu...@li...
>>  > Cc: 
>>  > Date: 2018/6/5, Tue 13:18
>>  > Subject: Release 5.2.4
>>  > 
>>  > Release 5.2.4 source tarball is ready and can be downloaded from
>>  > 
>>  >    
>>  > 
> https://sourceforge.net/projects/gnuplot/files/gnuplot/5.2.4/gnuplot-5.2.4.tar.gz
>>  > 
>>  > This release contains
>>  > - a fix for a serious regression reported against 5.2.3 (spurious
>>  >   evaluation of logscale coordinates as UNDEFINED)
>>  > - re-implementation of the "refresh" command to correct 
> regressions in
>>  >   5.2.0 through 5.2.3
>>  > - sanity checks for several invalid command sequences found by fuzzing
>>  > - several minor bug-fixes
>>  > - two recent minor changes back-ported from the development version
>>  > 
>>  > Yes it's only been a month since 5.2.3 but I think the regression
>>  > in plotting logscale axes is serious enough to warrant an immediate 
> fix.
>>  > If you want to test before/after here is a simple trigger for the 
> error:
>>  >     set log y
>>  >     plot [1:100] x**2, 1/0
>>  > 
>>  > Windows binaries will follow eventually.
>>  > 
>>  >     happy gnuplotting
>>  > 
>>  >         Ethan
>>  > 
>>  > 
> ------------------------------------------------------------------------------
>>  > Check out the vibrant tech community on one of the world's most
>>  > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>  > _______________________________________________
>>  > gnuplot-beta mailing list
>>  > gnu...@li...
>>  > Membership management via: 
>>  > https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
>>  > 
>> 
>> 
> ------------------------------------------------------------------------------
>>  Check out the vibrant tech community on one of the world's most
>>  engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>  _______________________________________________
>>  gnuplot-beta mailing list
>>  gnu...@li...
>>  Membership management via: 
> https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
> 

Re: Release 5.2.4

[sfeam <sf...@us...>]

On Wednesday, 06 June 2018 10:06:39 Tatsuro MATSUOKA wrote:
> Shigeharu Takeno found that
> 
> 
> In docs/titlepag.tex in gnuplot-5.2.4.tar.gz
> 
> 
> There described
> 
> %  31 May 2017 Version 5.2
>    Version 5.2.3 (May 2018)
> 
> gnuplot.pdf on SourceForge, the version number is 5.2.4 but source for document tar ball
> is still 5.2.3.

Yes. That is true.
But the content of the manual (docs/gnuplot.doc) has not changed
except for one sentence about the new ARGV array variable.
 
> I propose to make a fixed tar ball named like gnuplot-5.2.4-1.tar.gz.

In the past, people have complained about relabeling the source tarball
or changing its content.  If a change is necessary, the policy is that
we increment the patchlevel to create a new minor release version.
But it seems unreasonable to create a release 5.2.5 only so that we
can change the version stamp on the title page of the pdf documentation.

By the way, the gnuplot.pdf on the download site itself correctly 
lists version 5.2.4 on the title page.   I will make sure the copy
linked on the main web page is correct also.

	Ethan

 
> 
> Tatsuro
> 
> 
> 
> ----- Original Message -----
> > From: sfeam via gnuplot-beta <gnu...@li...>
> > To: gnu...@li...
> > Cc: 
> > Date: 2018/6/5, Tue 13:18
> > Subject: Release 5.2.4
> > 
> > Release 5.2.4 source tarball is ready and can be downloaded from
> > 
> >     
> > https://sourceforge.net/projects/gnuplot/files/gnuplot/5.2.4/gnuplot-5.2.4.tar.gz
> > 
> > This release contains
> > - a fix for a serious regression reported against 5.2.3 (spurious
> >   evaluation of logscale coordinates as UNDEFINED)
> > - re-implementation of the "refresh" command to correct regressions in
> >   5.2.0 through 5.2.3
> > - sanity checks for several invalid command sequences found by fuzzing
> > - several minor bug-fixes
> > - two recent minor changes back-ported from the development version
> > 
> > Yes it's only been a month since 5.2.3 but I think the regression
> > in plotting logscale axes is serious enough to warrant an immediate fix.
> > If you want to test before/after here is a simple trigger for the error:
> >     set log y
> >     plot [1:100] x**2, 1/0
> > 
> > Windows binaries will follow eventually.
> > 
> >     happy gnuplotting
> > 
> >         Ethan
> > 
> > ------------------------------------------------------------------------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> > _______________________________________________
> > gnuplot-beta mailing list
> > gnu...@li...
> > Membership management via: 
> > https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
> > 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-beta

Re: Release 5.2.4

[Tatsuro M. <tma...@ya...>]

Shigeharu Takeno found that


In docs/titlepag.tex in gnuplot-5.2.4.tar.gz


There described

%  31 May 2017 Version 5.2
   Version 5.2.3 (May 2018)

gnuplot.pdf on SourceForge, the version number is 5.2.4 but source for document tar ball
is still 5.2.3.

I propose to make a fixed tar ball named like gnuplot-5.2.4-1.tar.gz.


Tatsuro



----- Original Message -----
> From: sfeam via gnuplot-beta <gnu...@li...>
> To: gnu...@li...
> Cc: 
> Date: 2018/6/5, Tue 13:18
> Subject: Release 5.2.4
> 
> Release 5.2.4 source tarball is ready and can be downloaded from
> 
>     
> https://sourceforge.net/projects/gnuplot/files/gnuplot/5.2.4/gnuplot-5.2.4.tar.gz
> 
> This release contains
> - a fix for a serious regression reported against 5.2.3 (spurious
>   evaluation of logscale coordinates as UNDEFINED)
> - re-implementation of the "refresh" command to correct regressions in
>   5.2.0 through 5.2.3
> - sanity checks for several invalid command sequences found by fuzzing
> - several minor bug-fixes
> - two recent minor changes back-ported from the development version
> 
> Yes it's only been a month since 5.2.3 but I think the regression
> in plotting logscale axes is serious enough to warrant an immediate fix.
> If you want to test before/after here is a simple trigger for the error:
>     set log y
>     plot [1:100] x**2, 1/0
> 
> Windows binaries will follow eventually.
> 
>     happy gnuplotting
> 
>         Ethan
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> Membership management via: 
> https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
> 

Re: Release 5.2.4

[Tatsuro M. <tma...@ya...>]

Windows binary packages are now available.

Tatsuro



----- Original Message -----
> From: sfeam via gnuplot-beta <gnu...@li...>
> To: gnu...@li...
> Cc: 
> Date: 2018/6/5, Tue 13:18
> Subject: Release 5.2.4
> 
> Release 5.2.4 source tarball is ready and can be downloaded from
> 
>     
> https://sourceforge.net/projects/gnuplot/files/gnuplot/5.2.4/gnuplot-5.2.4.tar.gz
> 
> This release contains
> - a fix for a serious regression reported against 5.2.3 (spurious
>   evaluation of logscale coordinates as UNDEFINED)
> - re-implementation of the "refresh" command to correct regressions in
>   5.2.0 through 5.2.3
> - sanity checks for several invalid command sequences found by fuzzing
> - several minor bug-fixes
> - two recent minor changes back-ported from the development version
> 
> Yes it's only been a month since 5.2.3 but I think the regression
> in plotting logscale axes is serious enough to warrant an immediate fix.
> If you want to test before/after here is a simple trigger for the error:
>     set log y
>     plot [1:100] x**2, 1/0
> 
> Windows binaries will follow eventually.
> 
>     happy gnuplotting
> 
>         Ethan
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> Membership management via: 
> https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
> 

Release 5.2.4

[sfeam <sf...@us...>]

Release 5.2.4 source tarball is ready and can be downloaded from

    https://sourceforge.net/projects/gnuplot/files/gnuplot/5.2.4/gnuplot-5.2.4.tar.gz

This release contains
- a fix for a serious regression reported against 5.2.3 (spurious
  evaluation of logscale coordinates as UNDEFINED)
- re-implementation of the "refresh" command to correct regressions in
  5.2.0 through 5.2.3
- sanity checks for several invalid command sequences found by fuzzing
- several minor bug-fixes
- two recent minor changes back-ported from the development version

Yes it's only been a month since 5.2.3 but I think the regression
in plotting logscale axes is serious enough to warrant an immediate fix.
If you want to test before/after here is a simple trigger for the error:
    set log y
    plot [1:100] x**2, 1/0

Windows binaries will follow eventually.

	happy gnuplotting

		Ethan

Re: pre-release testing version of gnuplot 5.2.4

[Tatsuro M. <tma...@ya...>]

I have tried to build by pre-build libraries  embedded to Msys2.


undefined reference to wxtwidget symbols is disappeared.

I will try to change my build system from my original one to Msys2 based one.
But it takes a time to do it completely.

Anyway, please go ahead.

Tatsuro



----- Original Message -----
> From: Tatsuro MATSUOKA <tma...@ya...>
> To: Merritt Ethan <sf...@us...>; gnu...@li...; bma...@we...
> Cc: 
> Date: 2018/6/3, Sun 07:49
> Subject: Re: pre-release testing version of gnuplot 5.2.4
> 
> Windows 64 bit build fails at link stage.
> 
> g++ -L/c/Programs/gplibs64_gcc710/lib -s -L/c/Programs/Qt/5.9.1_mgw64_710/lib 
> -mconsole -L/c/Program\ Files\ \(x86\)/HTML\ Help\ 
> Workshop/lib -L. -o gnuplot.exe eval.co getcolor.co stats.co unset.co 
> breaders.co specfun.co term.co graph3d.co dynarray.co show.co axis.co stdfn.co 
> util.co save.co util3d.co tabulate.co readline.co internal.co jitter.co 
> libcerf.co bitmap.co hidden3d.co plot3d.co color.co contour.co command.co 
> multiplot.co plot.co scanner.co gadgets.co plot2d.co tables.co time.co pm3d.co 
> matrix.co boundary.co fit.co misc.co alloc.co external.co help.co interpol.co 
> datafile.co parse.co standard.co variable.co datablock.co graphics.co mouse.co 
> set.co history.co version.co gpexecute.co wxt_gui.co gp_cairo.co 
> gp_cairo_helpers.co qt_term.co  winmain.co wgnuplib.co wgraph.co wprinter.co 
> wpause.co wgdiplus.co wd2d.co wgplt_res.co -lkernel32 -lgdi32 -lwinspool 
> -lcomdlg32 -lcomctl32 -ladvapi32 -lshell32 -lmsimg32 -lgdiplus -lshlwapi -ld2d1 
> -ldwrite
> -lole32 -lhtmlhelp\
>  -lgd -lgd -lz -L/c/Programs/gplibs64_gcc710/lib -lpng16 -lz 
> -L/c/Programs/gplibs64_gcc710/lib -lfreetype -lz -lpng16 -lz -lfontconfig -ljpeg 
> -L/c/Programs/gplibs64_gcc710/lib -lz -lpng16 -lz -lfreetype -lz -lpng16 -lz 
> -lfontconfig -ljpeg -lgd -lQt5Core -lQt5Gui -lQt5Network -lQt5Svg -lQt5Widgets 
> -lQt5PrintSupport -lqtmain -llua -liconv -lcerf -lm 
> -L/c/Programs/gplibs64_gcc710/lib   -L/c/Programs/gplibs64_gcc710/lib 
> -L/mingw64/lib   -lwx_mswu_xrc-3.0 -lwx_mswu_webview-3.0 -lwx_mswu_html-3.0 
> -lwx_mswu_qa-3.0 -lwx_mswu_adv-3.0 -lwx_mswu_core-3.0 -lwx_baseu_xml-3.0 
> -lwx_baseu_net-3.0 -lwx_baseu-3.0  -L/c/Programs/gplibs64_gcc710/lib 
> -L/c/Programs/gplibs64_gcc710/lib/../lib -L/c/Programs/gplibs64_gcc710/lib 
> -lpangocairo-1.0 -lpangowin32-1.0 -lgdi32 -lusp10 -lpango-1.0 -lm -lcairo -lz 
> -lgobject-2.0 -lffi -lglib-2.0 -lintl -lws2_32 -lole32 -lwinmm -lshlwapi -lintl 
> -lpixman-1 -lfreetype -lz -lpng16 -lz
> C:/msys64_gcc710/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/7.1.0/../../../../x86_64-w64-mingw32/bin/ld.exe: 
> skipping incompatible C:/Program Files (x86)/HTML Help Workshop/lib/htmlhelp.lib 
> when searching for -lhtmlhelp
> term.co:term.c:(.text+0x129fd): undefined reference to 
> `wxt_close_terminal_window'
> term.co:term.c:(.text+0x13007): undefined reference to `wxt_update_title'
> term.co:term.c:(.text+0x13414): undefined reference to `wxt_update_size'
> term.co:term.c:(.text+0x134c7): undefined reference to `wxt_update_position'
> term.co:term.c:(.text+0xc955): undefined reference to `wxt_text'
> term.co:term.c:(.data+0x3a70): undefined reference to `wxt_init'
> term.co:term.c:(.data+0x3a78): undefined reference to `wxt_reset'
> term.co:term.c:(.data+0x3a90): undefined reference to `wxt_graphics'
> term.co:term.c:(.data+0x3a98): undefined reference to `wxt_move'
> term.co:term.c:(.data+0x3aa0): undefined reference to `wxt_vector'
> term.co:term.c:(.data+0x3aa8): undefined reference to `wxt_linetype'
> term.co:term.c:(.data+0x3ab0): undefined reference to `wxt_put_text'
> term.co:term.c:(.data+0x3ab8): undefined reference to `wxt_text_angle'
> term.co:term.c:(.data+0x3ac0): undefined reference to `wxt_justify_text'
> term.co:term.c:(.data+0x3ac8): undefined reference to `wxt_point'
> term.co:term.c:(.data+0x3ad8): undefined reference to `wxt_set_font'
> term.co:term.c:(.data+0x3ae0): undefined reference to `wxt_pointsize'
> term.co:term.c:(.data+0x3af0): undefined reference to `wxt_text'
> term.co:term.c:(.data+0x3b00): undefined reference to `wxt_fillbox'
> term.co:term.c:(.data+0x3b08): undefined reference to `wxt_linewidth'
> term.co:term.c:(.data+0x3b10): undefined reference to `wxt_waitforinput'
> term.co:term.c:(.data+0x3b18): undefined reference to `wxt_put_tmptext'
> term.co:term.c:(.data+0x3b20): undefined reference to `wxt_set_ruler'
> term.co:term.c:(.data+0x3b28): undefined reference to `wxt_set_cursor'
> term.co:term.c:(.data+0x3b30): undefined reference to `wxt_set_clipboard'
> term.co:term.c:(.data+0x3b38): undefined reference to `wxt_make_palette'
> term.co:term.c:(.data+0x3b48): undefined reference to `wxt_set_color'
> term.co:term.c:(.data+0x3b50): undefined reference to `wxt_filled_polygon'
> term.co:term.c:(.data+0x3b58): undefined reference to `wxt_image'
> term.co:term.c:(.data+0x3b60): undefined reference to `wxt_enhanced_open'
> term.co:term.c:(.data+0x3b68): undefined reference to `wxt_enhanced_flush'
> term.co:term.c:(.data+0x3b70): undefined reference to `wxt_enhanced_writec'
> term.co:term.c:(.data+0x3b78): undefined reference to `wxt_layer'
> term.co:term.c:(.data+0x3b90): undefined reference to `wxt_hypertext'
> term.co:term.c:(.data+0x3b98): undefined reference to `wxt_boxed_text'
> term.co:term.c:(.data+0x3ba0): undefined reference to `wxt_modify_plots'
> term.co:term.c:(.data+0x3ba8): undefined reference to `wxt_dashtype'
> command.co:command.c:(.text+0x1497): undefined reference to 
> `wxt_lower_terminal_window'
> command.co:command.c:(.text+0x14b2): undefined reference to 
> `wxt_raise_terminal_window'
> command.co:command.c:(.text+0x13b2): undefined reference to 
> `wxt_lower_terminal_group'
> command.co:command.c:(.text+0x13ce): undefined reference to 
> `wxt_raise_terminal_group'
> winmain.co:winmain.c:(.text+0xdbf): undefined reference to 
> `wxt_window_opened'
> winmain.co:winmain.c:(.text+0xdd1): undefined reference to 
> `wxt_window_opened'
> winmain.co:winmain.c:(.text+0xb75): undefined reference to `wxt_screen_dump'
> wpause.co:wpause.c:(.text+0x771): undefined reference to 
> `wxt_active_window_opened'
> collect2.exe: error: ld returned 1 exit status
> make[1]: *** [Makefile:616: gnuplot.exe] Error 1
> make[1]: Leaving directory 
> '/d/usr/Tatsu/msys2mingw64_710/gnuplot/gnuplot-5.2.4-testing/gnuplot-5.2.4/config/mingw'
> make: *** [Makefile:566: console] Error 2
> 
> 
> Bastian.
> 
> Do you have time to build gnuplot 5.2.4 on windows 64 bit?
> 
> For 32bit, build went well.
> 
> 
> Tatsuro
> 
> 
> 
> ----- Original Message -----
>>  From: sfeam via gnuplot-beta <gnu...@li...>
>>  To: gnu...@li...
>>  Cc: 
>>  Date: 2018/6/2, Sat 14:23
>>  Subject: pre-release testing version of gnuplot 5.2.4
>> 
>>  I have uploaded a 5.2.4 tarball to the "testing" section of the
>>  gnuplot files folder on SourceForge.
>>    
>>      https://sourceforge.net/projects/gnuplot/files/gnuplot/testing/
>>      gnuplot-5.2.4-testing.tar.gz
>> 
>> 
>>  This release contains
>>  - a fix for a serious regression reported against 5.2.3 (spurious
>>    evaluation of logscale coordinates as UNDEFINED)
>>  - re-implementation of the "refresh" command to correct 
> regressions in
>>    5.2.0 through 5.2.3
>>  - sanity checks for several invalid command sequences found by fuzzing
>>  - several minor bug-fixes
>>  - two recent minor changes back-ported from the development version
>> 
>>  Yes it's only been a month since 5.2.3 but I think the regression
>>  in plotting logscale axes is serious enough to warrant an immediate fix.
>>  If you want to test before/after here is a simple trigger for the error:
>>      set log y
>>      plot [1:100] x**2, 1/0
>> 
>>  Please use the testing tarball to confirm a successful build or
>>  report build errors.  If no problems are found I expect to make a
>>  regular release of 5.2.4 next week.
>> 
>>      Ethan
>> 
>> 
> ------------------------------------------------------------------------------
>>  Check out the vibrant tech community on one of the world's most
>>  engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>  _______________________________________________
>>  gnuplot-beta mailing list
>>  gnu...@li...
>>  Membership management via: 
>>  https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
>> 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> Membership management via: 
> https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
> 

Re: pre-release testing version of gnuplot 5.2.4

[Tatsuro M. <tma...@ya...>]

Windows 64 bit build fails at link stage.

g++ -L/c/Programs/gplibs64_gcc710/lib -s -L/c/Programs/Qt/5.9.1_mgw64_710/lib -mconsole -L/c/Program\ Files\ \(x86\)/HTML\ Help\ Workshop/lib -L. -o gnuplot.exe eval.co getcolor.co stats.co unset.co breaders.co specfun.co term.co graph3d.co dynarray.co show.co axis.co stdfn.co util.co save.co util3d.co tabulate.co readline.co internal.co jitter.co libcerf.co bitmap.co hidden3d.co plot3d.co color.co contour.co command.co multiplot.co plot.co scanner.co gadgets.co plot2d.co tables.co time.co pm3d.co matrix.co boundary.co fit.co misc.co alloc.co external.co help.co interpol.co datafile.co parse.co standard.co variable.co datablock.co graphics.co mouse.co set.co history.co version.co gpexecute.co wxt_gui.co gp_cairo.co gp_cairo_helpers.co qt_term.co  winmain.co wgnuplib.co wgraph.co wprinter.co wpause.co wgdiplus.co wd2d.co wgplt_res.co -lkernel32 -lgdi32 -lwinspool -lcomdlg32 -lcomctl32 -ladvapi32 -lshell32 -lmsimg32 -lgdiplus -lshlwapi -ld2d1 -ldwrite
 -lole32 -lhtmlhelp\
 -lgd -lgd -lz -L/c/Programs/gplibs64_gcc710/lib -lpng16 -lz -L/c/Programs/gplibs64_gcc710/lib -lfreetype -lz -lpng16 -lz -lfontconfig -ljpeg -L/c/Programs/gplibs64_gcc710/lib -lz -lpng16 -lz -lfreetype -lz -lpng16 -lz -lfontconfig -ljpeg -lgd -lQt5Core -lQt5Gui -lQt5Network -lQt5Svg -lQt5Widgets -lQt5PrintSupport -lqtmain -llua -liconv -lcerf -lm -L/c/Programs/gplibs64_gcc710/lib   -L/c/Programs/gplibs64_gcc710/lib -L/mingw64/lib   -lwx_mswu_xrc-3.0 -lwx_mswu_webview-3.0 -lwx_mswu_html-3.0 -lwx_mswu_qa-3.0 -lwx_mswu_adv-3.0 -lwx_mswu_core-3.0 -lwx_baseu_xml-3.0 -lwx_baseu_net-3.0 -lwx_baseu-3.0  -L/c/Programs/gplibs64_gcc710/lib -L/c/Programs/gplibs64_gcc710/lib/../lib -L/c/Programs/gplibs64_gcc710/lib -lpangocairo-1.0 -lpangowin32-1.0 -lgdi32 -lusp10 -lpango-1.0 -lm -lcairo -lz -lgobject-2.0 -lffi -lglib-2.0 -lintl -lws2_32 -lole32 -lwinmm -lshlwapi -lintl -lpixman-1 -lfreetype -lz -lpng16 -lz
C:/msys64_gcc710/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/7.1.0/../../../../x86_64-w64-mingw32/bin/ld.exe: skipping incompatible C:/Program Files (x86)/HTML Help Workshop/lib/htmlhelp.lib when searching for -lhtmlhelp
term.co:term.c:(.text+0x129fd): undefined reference to `wxt_close_terminal_window'
term.co:term.c:(.text+0x13007): undefined reference to `wxt_update_title'
term.co:term.c:(.text+0x13414): undefined reference to `wxt_update_size'
term.co:term.c:(.text+0x134c7): undefined reference to `wxt_update_position'
term.co:term.c:(.text+0xc955): undefined reference to `wxt_text'
term.co:term.c:(.data+0x3a70): undefined reference to `wxt_init'
term.co:term.c:(.data+0x3a78): undefined reference to `wxt_reset'
term.co:term.c:(.data+0x3a90): undefined reference to `wxt_graphics'
term.co:term.c:(.data+0x3a98): undefined reference to `wxt_move'
term.co:term.c:(.data+0x3aa0): undefined reference to `wxt_vector'
term.co:term.c:(.data+0x3aa8): undefined reference to `wxt_linetype'
term.co:term.c:(.data+0x3ab0): undefined reference to `wxt_put_text'
term.co:term.c:(.data+0x3ab8): undefined reference to `wxt_text_angle'
term.co:term.c:(.data+0x3ac0): undefined reference to `wxt_justify_text'
term.co:term.c:(.data+0x3ac8): undefined reference to `wxt_point'
term.co:term.c:(.data+0x3ad8): undefined reference to `wxt_set_font'
term.co:term.c:(.data+0x3ae0): undefined reference to `wxt_pointsize'
term.co:term.c:(.data+0x3af0): undefined reference to `wxt_text'
term.co:term.c:(.data+0x3b00): undefined reference to `wxt_fillbox'
term.co:term.c:(.data+0x3b08): undefined reference to `wxt_linewidth'
term.co:term.c:(.data+0x3b10): undefined reference to `wxt_waitforinput'
term.co:term.c:(.data+0x3b18): undefined reference to `wxt_put_tmptext'
term.co:term.c:(.data+0x3b20): undefined reference to `wxt_set_ruler'
term.co:term.c:(.data+0x3b28): undefined reference to `wxt_set_cursor'
term.co:term.c:(.data+0x3b30): undefined reference to `wxt_set_clipboard'
term.co:term.c:(.data+0x3b38): undefined reference to `wxt_make_palette'
term.co:term.c:(.data+0x3b48): undefined reference to `wxt_set_color'
term.co:term.c:(.data+0x3b50): undefined reference to `wxt_filled_polygon'
term.co:term.c:(.data+0x3b58): undefined reference to `wxt_image'
term.co:term.c:(.data+0x3b60): undefined reference to `wxt_enhanced_open'
term.co:term.c:(.data+0x3b68): undefined reference to `wxt_enhanced_flush'
term.co:term.c:(.data+0x3b70): undefined reference to `wxt_enhanced_writec'
term.co:term.c:(.data+0x3b78): undefined reference to `wxt_layer'
term.co:term.c:(.data+0x3b90): undefined reference to `wxt_hypertext'
term.co:term.c:(.data+0x3b98): undefined reference to `wxt_boxed_text'
term.co:term.c:(.data+0x3ba0): undefined reference to `wxt_modify_plots'
term.co:term.c:(.data+0x3ba8): undefined reference to `wxt_dashtype'
command.co:command.c:(.text+0x1497): undefined reference to `wxt_lower_terminal_window'
command.co:command.c:(.text+0x14b2): undefined reference to `wxt_raise_terminal_window'
command.co:command.c:(.text+0x13b2): undefined reference to `wxt_lower_terminal_group'
command.co:command.c:(.text+0x13ce): undefined reference to `wxt_raise_terminal_group'
winmain.co:winmain.c:(.text+0xdbf): undefined reference to `wxt_window_opened'
winmain.co:winmain.c:(.text+0xdd1): undefined reference to `wxt_window_opened'
winmain.co:winmain.c:(.text+0xb75): undefined reference to `wxt_screen_dump'
wpause.co:wpause.c:(.text+0x771): undefined reference to `wxt_active_window_opened'
collect2.exe: error: ld returned 1 exit status
make[1]: *** [Makefile:616: gnuplot.exe] Error 1
make[1]: Leaving directory '/d/usr/Tatsu/msys2mingw64_710/gnuplot/gnuplot-5.2.4-testing/gnuplot-5.2.4/config/mingw'
make: *** [Makefile:566: console] Error 2


Bastian.

Do you have time to build gnuplot 5.2.4 on windows 64 bit?

For 32bit, build went well.


Tatsuro



----- Original Message -----
> From: sfeam via gnuplot-beta <gnu...@li...>
> To: gnu...@li...
> Cc: 
> Date: 2018/6/2, Sat 14:23
> Subject: pre-release testing version of gnuplot 5.2.4
> 
> I have uploaded a 5.2.4 tarball to the "testing" section of the
> gnuplot files folder on SourceForge.
>   
>     https://sourceforge.net/projects/gnuplot/files/gnuplot/testing/
>     gnuplot-5.2.4-testing.tar.gz
> 
> 
> This release contains
> - a fix for a serious regression reported against 5.2.3 (spurious
>   evaluation of logscale coordinates as UNDEFINED)
> - re-implementation of the "refresh" command to correct regressions in
>   5.2.0 through 5.2.3
> - sanity checks for several invalid command sequences found by fuzzing
> - several minor bug-fixes
> - two recent minor changes back-ported from the development version
> 
> Yes it's only been a month since 5.2.3 but I think the regression
> in plotting logscale axes is serious enough to warrant an immediate fix.
> If you want to test before/after here is a simple trigger for the error:
>     set log y
>     plot [1:100] x**2, 1/0
> 
> Please use the testing tarball to confirm a successful build or
> report build errors.  If no problems are found I expect to make a
> regular release of 5.2.4 next week.
> 
>     Ethan
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> Membership management via: 
> https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
> 

Re: pre-release testing version of gnuplot 5.2.4

[Erik L. <eri...@gm...>]

Hi,

The macOS (OS X) executable of 5.2.4 is available here:

https://csml-wiki.northwestern.edu/index.php/Binary_versions_of_Gnuplot_for_OS_X

I can confirm that the logscale problem is resolved, at least for the
trigger example given by Ethan

Best,

Erik


On Sat, Jun 2, 2018 at 12:24 AM sfeam via gnuplot-beta <
gnu...@li...> wrote:

> I have uploaded a 5.2.4 tarball to the "testing" section of the
> gnuplot files folder on SourceForge.
>
>     https://sourceforge.net/projects/gnuplot/files/gnuplot/testing/
>     gnuplot-5.2.4-testing.tar.gz
>
>
> This release contains
> - a fix for a serious regression reported against 5.2.3 (spurious
>   evaluation of logscale coordinates as UNDEFINED)
> - re-implementation of the "refresh" command to correct regressions in
>   5.2.0 through 5.2.3
> - sanity checks for several invalid command sequences found by fuzzing
> - several minor bug-fixes
> - two recent minor changes back-ported from the development version
>
> Yes it's only been a month since 5.2.3 but I think the regression
> in plotting logscale axes is serious enough to warrant an immediate fix.
> If you want to test before/after here is a simple trigger for the error:
>     set log y
>     plot [1:100] x**2, 1/0
>
> Please use the testing tarball to confirm a successful build or
> report build errors.  If no problems are found I expect to make a
> regular release of 5.2.4 next week.
>
>         Ethan
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> Membership management via:
> https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
>