Ethan A Merritt committed [c62076] on Git Repository

Ethan A Merritt committed [064c31] on Git Repository

set contourfill defined [zmin1:zmax1] color1, [zmin2:zmax2] color, ...

Ethan A Merritt committed [a5985f] on Git Repository

remove flush_binary() (used only by VMS)

Ethan A Merritt committed [a585aa] on Git Repository

remove DEC-specific binary constants

Ethan A Merritt committed [c56950] on Git Repository

Remove VMS-specific code

Ethan A Merritt committed [bd37da] on Git Repository

replace usleep with nanosleep

Ethan A Merritt committed [7a71cf] on Git Repository

docs: update description of backslash as a line-continuation

Ethan A Merritt committed [eded47] on Git Repository

ignore trailing whitespace on input command lines

Ethan Merritt modified ticket #2865

Plot title is not initialized correctly following a plot with no valid data

Ethan Merritt posted a comment on ticket #2865

Fixed in 6.1 Queued for 6.0.5

Ethan A Merritt committed [8370ad] on Git Repository

Rework the logic for extending gp_input_line incrementally on input

Ethan A Merritt committed [51916e] on Git Repository

previous plot title must always be cleared when a new plot is started

Ethan Merritt modified ticket #2865

Plot title is not initialized correctly following a plot with no valid data

Ethan Merritt modified ticket #2865

Plot title is not initialized correctly following a plot with no valid data

Ethan Merritt created ticket #2865

Plot title is not initialized correctly following a plot with no valid data

Ethan A Merritt committed [b8c8f1] on Git Repository

docs: update indication of features that have been backported to 6.0

Ethan A Merritt committed [ff2525] on Git Repository

WASI platform support - documentation

Ethan A Merritt committed [3db92c] on Git Repository

initialization of axis tic settings after "set nonlinear"

Ethan A Merritt committed [3c16f4] on Git Repository

code readability: use hypot(x,y)

Ethan A Merritt committed [81e638] on Git Repository

EUCJP encoding - avoid explicit "set encoding EUC_JP" in saved output

Ethan Merritt posted a comment on ticket #2864

Yes, the behavior has changed since version 5. User feedback (a.k.a. "bug reports") suggested revisions to the empirical rules for log tic placement. See in particular the discussion attached to Bug #2717 https://sourceforge.net/p/gnuplot/bugs/2717/ Some users feel strongly that there must be at least three major (i.e. labeled) tic marks in order to make it immediately apparent that the axis is log-scaled. The output from 5.4 on plot #2 has only two labeled tic marks. In this particular case close...

zcy modified ticket #2864

logscale issue in tics

zcy posted a comment on ticket #2864

This behavior is different from that in the previous version (at least v5.4 as I used before, see the right panel of the figure attached). "ytics" ignored the "logscale" parameter - the tic interval was supposed to be interpreted as a multiplicative factor rather than a constant. Would like to clarify if this is a new feature or a bug? Thanks! gnuplot> set log y gnuplot> set yrange [5:1e2] gnuplot> set ytics 10,10,1e3 logscale gnuplot> set mytics 10 gnuplot> p x

Ethan Merritt posted a comment on ticket #2864

Both plots show log scaling on y. The difference you notice is probably the choice of where to place major tics (labeled) vs minor tics (unlabeled). The program tries to choose a reasonable set of major and minor axis tics based on the total range. When placing log scaled major tics it currently uses heuristics like "there must be at least 3 but preferably not more than 10 major tics; do not place more than 10 minor tics between major tics; if the range would hold only 1 major tic promote the minor...

Anonymous created ticket #2864

logscale issue in tics

Ethan A Merritt committed [b2a834] on Git Repository

update NEWS

Ethan A Merritt committed [8e9a7b] on Git Repository

parametric mode is incompatible with axis range sampling

Ethan A Merritt committed [2b1485] on Git Repository

"unset warnings" should suppress axis range warning

Ethan A Merritt committed [ea1b38] on Git Repository

docs: Expand section on sum[]<expr> operator to also describe prod[]<expr>

Ethan A Merritt committed [faaade] on Git Repository

New function prod [<var> = <start> : <end>] <expression>

Ethan A Merritt committed [7dbb9f] on Git Repository

checking for plot title should not consume "noenhanced"

Ethan A Merritt committed [07ec62] on Git Repository

wxt, x11: reduce flicker during multiplot or animation

Ethan A Merritt committed [b714fc] on Git Repository

allow "string"[i] as shorthand for "string"[i:i]

Ethan A Merritt committed [7bbf83] on Git Repository

wrap the lines of a datablock (or function block) in a structure

Ethan A Merritt committed [af3c2c] on Git Repository

docs: documentation for new gprintf formats %C and %Ci

Ethan A Merritt committed [6f7db1] on Git Repository

revisit escape sequences (documentation)

Ethan A Merritt committed [9337b8] on Git Repository

revisit escape sequences (UTF-8)

Ethan A Merritt committed [24a9b6] on Git Repository

revisit escape sequences (octal)

Ethan A Merritt committed [527618] on Git Repository

Expand unicode escape sequences in string functions strstrt and strlen

Ethan A Merritt committed [5d1ebb] on Git Repository

Expand unicode escape sequnces during substring evaluation

Ethan A Merritt committed [4bd2f6] on Git Repository

expand Unicode escape sequences \U+xxxx in "noenhanced" strings

Ethan A Merritt committed [7ab1a7] on Git Repository

limit the length of axis tickmarks after "set view map; set isotropic"

Ethan A Merritt committed [601877] on Git Repository

move check for "palette <colormap-name>" from lp_parse to parse_colorspec

Ethan A Merritt committed [0ab870] on Git Repository

emf svg: remove references to old terminal option {dashed|solid}

Ethan Merritt modified ticket #833

Full dashtype support for libgd terminals and improved antialiasing quality

Ethan Merritt posted a comment on ticket #833

Got it. Thanks very much.

Ethan A Merritt committed [406bc5] on Git Repository

Windows tempfile support broken by typos in datablock.c

Ethan A Merritt committed [423698] on Git Repository

gd: antialiased thick lines, dash patterns, and transparent line support

Sethur posted a comment on ticket #833

Hi @sfeam I have attached a patch to gd.trm that adds a short description. It also includes my e-mail address, but feel free to remove it or list it exclusively if this otherwise collides with the aesthetics of the comment block. As overall commit message, I would suggest the following, but feel free to adapt it to your preferred length. I have not included new lines in the paragraphs intentionally, so you can conveniently add them were you want them. gd terminal: antialiased thick lines, dash patterns,...

Ethan A Merritt committed [ae6f61] on Git Repository

new demo: cerfi.dem

Ethan A Merritt committed [d08d85] on Git Repository

docs: clarify that erfi(x) is a real-valed function of a real variable

Ethan A Merritt committed [1d332a] on Git Repository

add config.guess config.sub to .gitignore

Ethan Merritt posted a comment on ticket #833

I am truly impressed by the quality of the output. Let's go with this version. Could you provide one more patch to apply on top of this to give yourself credit at the top of gd.trm for this major revision (a line or two to summary the work very briefly)? Also it would be nice if you provide an overall description to use as a commit message when I add it to the git repository. I could write something myself but you obviously know better than I do how to properly describe it. What should the author...

Sethur modified a comment on ticket #833

Update and patch: Looking at the graphs above it was clear that something was wrong with the disk/clipped-disk (depending on the endcaps) join rendering at positions with high curvature in the sinc curves (mainly at the bottom part of the valleys). This had nothing to do with the empty-canvas rendering patch I was testing but came down to a bug in the original patch where I used integer pixel coordinate instead of pixel centers in PNG_draw_join_disc. Also, there was another bug in PNG_draw_join_disc...

Sethur posted a comment on ticket #833

Update and patch: Looking at the graphs above it was clear that something was wrong with the disk/clipped-disk (depending on the endcaps) join rendering at positions with high curvature in the sinc curves (mainly at the bottom part of the valleys). This had nothing to do with the empty-canvas rendering patch I was testing but came down to a bug in the original patch where I used integer pixel coordinate instead of pixel centers in PNG_draw_join_disc. Also, there was another bug in PNG_draw_join_disc...

Ethan Merritt modified ticket #2863

yrange ignored in parametric mode

Sethur posted a comment on ticket #833

Hi @sfeam just wanted to tell you that I have a working solution for the transparency issue that uses the approach of rendering each line to a blank canvas that you have proposed. I will benchmark this again and check all the demo scripts for any regressions. If all goes well, I should be able to post a patch here soon. Attached is a test script for transparent lines and it's output.

Ethan A Merritt committed [c9e0fa] on Git Repository

parametric mode is incompatible with axis range sampling

Ethan Merritt posted a comment on ticket #833

Yes there have been problems with thick lines all along. Left to itself, libgd does a really poor job with them. So gnuplot draws a thick line by filling a circular area around each point along the line. This is done by drawing the line with gdImageSetBrush() and a brush constructed to be the width requested for the line. And, as you say, this causes transparent thick lines to be way less transparent than requested because every single point leads to overlaps. So yes there is extra darkening at points...

Sethur posted a comment on ticket #833

My bad, I wasn't aware that one could even choose the alpha value for line colors in Gnuplot, but apparently, this was implemented quite some time ago. I will see if I can come up with a solution for that. Your suggestion of redering everything on a blank canvas sounds reasonable. As a side note: Didn't the old libgd terminal also have this issue, at least with thick lines where overlaps should have happened before when rendering the segments?

Anonymous created ticket #2863

yrange ignored in parametric mode

Ethan Merritt posted a comment on ticket #833

No need to attach output. It's actually easier for me to test with kittycairo vs kittygd. That way I can run a test in side-by-side windows to compare the png and gd output rather than collecting and pairing up separate output files for display. I'll probably apply this version after going over the code to see if there's anything that can be tightened up or abstracted. The quality of the output is very good, with one exception that is not a deal-breaker. The algorithm used here has the imperfection...

Sethur posted a comment on ticket #833

If you are interested, I can upload the output of the demo scripts for the terminals: png (with patch), png (original) and pngcairo, but it would be quite large.

Ethan Merritt modified ticket #2860

gnuplot 6.0.4 ignores unset warnings

Ethan Merritt posted a comment on ticket #2860

Thanks. There's a fix already in 6.1 and queued for 6.0.next

MBoehme modified a comment on ticket #2860

I think I figured it out, here would be a patch: diff -Naur gnuplot-6.0.4_orig/src/axis.c gnuplot-6.0.4_patched/src/axis.c --- gnuplot-6.0.4_orig/src/axis.c 2025-11-30 23:15:20.000000000 +0100 +++ gnuplot-6.0.4_patched/src/axis.c 2026-03-13 20:03:47.739548000 +0100 @@ -433,17 +433,21 @@ double widen = (dmax == 0.0) ? FIXUP_RANGE__WIDEN_ZERO_ABS : FIXUP_RANGE__WIDEN_NONZERO_REL * fabs(dmax); - if (!(axis == FIRST_Z_AXIS && !mesg)) /* set view map */ - fprintf(stderr, "Warning: empty %s range [%g:%g],...

MBoehme posted a comment on ticket #2860

I think I figured it out, here would a patch: diff -Naur gnuplot-6.0.4_orig/src/axis.c gnuplot-6.0.4_patched/src/axis.c --- gnuplot-6.0.4_orig/src/axis.c 2025-11-30 23:15:20.000000000 +0100 +++ gnuplot-6.0.4_patched/src/axis.c 2026-03-13 20:03:47.739548000 +0100 @@ -433,17 +433,21 @@ double widen = (dmax == 0.0) ? FIXUP_RANGE__WIDEN_ZERO_ABS : FIXUP_RANGE__WIDEN_NONZERO_REL * fabs(dmax); - if (!(axis == FIRST_Z_AXIS && !mesg)) /* set view map */ - fprintf(stderr, "Warning: empty %s range [%g:%g],...

Ethan Merritt modified ticket #2862

Dumb terminal doesn't show all data

Ethan Merritt posted a comment on ticket #2862

As you say, increasing the range shows that in fact all 8 points are present. Since auto-scaling uses the extreme point coordinates to define the border, and the border of the plot is by default drawn after the points, it covers the two points with extreme coordinates. Try again with set border back to confirm.

Anonymous created ticket #2862

Dumb terminal doesn't show all data

Robert Dodier modified ticket #2861

epslatex terminal: tick labels contain LaTeX math but not enclosed in dollar signs

Robert Dodier posted a comment on ticket #2861

Thanks for the info, I'll go back and fix up the code which generated that Gnuplot script. I've marked this ticket as "not a bug" accordingly.

Ethan Merritt posted a comment on ticket #2861

The problem arises because your test script explicitly sets the tic format to '%h', but this is not correct for latex terminals. Here is the guidance from help set format: The length of the format string is restricted to 100 characters. The default format is "% h", except that LaTeX terminals use "$%h$". You can modify this to provide units or a different numeric format, for example 'set xtics format "%.2f MHz"'. "set format" with no following string will restore the default. I grant you that this...

Ethan A Merritt committed [971dae] on Git Repository

"unset warnings" should suppress axis range warning

Ethan Merritt posted a comment on ticket #833

Nice test figures!

Robert Dodier created ticket #2861

epslatex terminal: tick labels contain LaTeX math but not enclosed in dollar signs

Ethan Merritt posted a comment on ticket #2860

Most, but not all, of the warnings issued by gnuplot were sent by a shared subroutine. The "unset warnings" command silences that shared mechanism. That leaves a few [a quick-and-dirty "grep" of the source tree finds about thirty] places in the source code that print the warning directly rather than going through the shared subroutine. Some of these should probably never by silenced, like the ones from the stats and fit commands that tell you the calculation was invalid or highly unreliable. Others,...

MBoehme created ticket #2860

gnuplot 6.0.4 ignores unset warnings

Ethan Merritt posted a comment on ticket #834

Update After a minor tweak to gnuplot's svg/domterm terminal driver, I can now run the WASI/WASM gnuplot executable by invoking wasmtime inside qtdomterm. See https://domterm.org/ and (somewhat old) https://opensource.com/article/18/1/domterminal. Domterm intercepts the SVG output and then renders it inside the widget. This gets me full graphics, fonts, etc., in a Qt widget. It's great. Screenshot attached. Here's what I don't understand, though. It also makes the history and readline functions work....

Ethan A Merritt committed [ea7329] on Git Repository

svg: do not emit [CDATA] sections to generic svg output

Ethan A Merritt committed [93f272] on Git Repository

libstbi image-handling configuration

Ethan Merritt posted a comment on ticket #834

I have committed your original patchset and then committed a small modification to move the tempfile handling into a set of macros in syscfg.h rather than cluttering up the primary code with tests for #ifdef __wasi__. They also fix a memory leak that would have happened if an error is encountered while a tempfile is open. After a bit of fumbling I got the wasi-sdk installed and used that for testing. The only real problem I had is that I don't understand the mechanism for granting permission to access...

Ethan A Merritt committed [23df68] on Git Repository

WASI platform support - minor cleanup

Ethan A Merritt committed [572aca] on Git Repository

WASI platform support - new configure option and support code

Ethan A Merritt committed [ab2f4b] on Git Repository

reject filenames beginning with "|" if popen is not supported

PuQ posted a comment on ticket #834

Indeed, making fmemopen and open_memstream optional would be better. open_memstream creates a write-only stream, so I reopen the buffer with fmemopen to read from it. fmemopen can also be used for writing, but it requires a fixed-size buffer compared to open_memstream. From what I can see in Qt's docs, Qt for WebAssembly is essentially Qt for Emscripten and is designed to run in browsers. WASI's graphics APIs are still in an early stage, and no mainstream runtime supports them, unlike Emscripten,...

Ethan A Merritt committed [1e7508] on Git Repository

avoid nit-picky compiler warnings

Ethan Merritt posted a comment on ticket #834

Another question: Is there a reason you use the sequence fclose(fp); fp = fmemopen(fbuf, fbuf_len, "r"); rather than simply rewind(fp);? The documentation says fseek is usable after open_memstream(), and rewind is documented as being equivalent to fseek(stream, 0L, SEEK_SET). Allowing the code to use rewind(fp) further simplifies the change and works for me in testing (not on WASI yet).

Sethur posted a comment on ticket #833

PS: I can upload the output of the demo scripts as well, but that is 174 MB. Not sure if this is the right place.

Sethur posted a comment on ticket #833

Attachments here:

Sethur posted a comment on ticket #833

Hi @sfeam ! As promised, I have now tested and benchmarked my patch thoroughly and am confident to post it here again. The main issue I had to fight with was the fact the the integer resolution used in gd.trm was not sufficient to produce properly curve-aligned thick line-pieces. I had to use a similar approach to what is done in pngcairo to get around this, namely oversampling the coordinate space to increase the resolution for rendering and AA calculations in gd.trm. I have tested this against...

Ethan Merritt posted a comment on ticket #834

Now that I've looked at the patch, I wonder if 99% of it could be respun as "optional support for using memory-backed scratch space viafmemopen and open_memstream rather than using tempfiles. That seems like a perfectly reasonable option in any case, and it might then simplify WASI support into something like "you must select this option during configuration". Do I have that right? Thanks for the session output video. That gives me an idea of what you ended up with and what is missing. As to terminal...

PuQ posted a comment on ticket #834

wasi-sdk would be a good start, rather than installing another distro. It is a prebuilt bundle providing latest clang, wasi-libc and wasi-compiler-rt. I don't have much experience in Emscripten, but from what I know, Emscripten and WASI are two platforms (wasm32-emscripten and wasm32-wasi for compilers), providing different libc for Wasm. Wasm is more like a common architecture. WASI is also a set of system APIs designed to make more apps run anywhere including browsers/machines/servers. It provides...

Ethan Merritt posted a comment on ticket #834

I am potentially very interested in this, but I am very much not up to speed on the wasm ecosystem. Furthermore so far as I can tell, the linux systems I normally work on do not provide any of the relevant support packages, so I am at least one or two major steps away from being able to try this out. Maybe you can provide some guidance... Would it be more reasonable to work from the GitHub repository code and build it up the clang/wasm/wasi development tools from scratch or to start by installing...

PuQ created ticket #834

Add WASI platform support

Ethan Merritt modified ticket #2859

Fails to build with lua 5.5

Ethan A Merritt committed [444208] on Git Repository

lua terminals: lua version 5.5 treats loop variables as read-only

Ethan A Merritt committed [e21009] on Git Repository

Do not include the built-in colormaps in the output from "save"

Ethan A Merritt committed [a55c67] on Git Repository

lua terminals: lua version 5.5 treats loop variables as read-only

Orion Poplawski posted a comment on ticket #2854

So, it appers that there may have been a fix made to texlive. I'm no longer seeing this failure.