Fails to build with lua 5.5
lua terminals: lua version 5.5 treats loop variables as read-only
Do not include the built-in colormaps in the output from "save"
lua terminals: lua version 5.5 treats loop variables as read-only
So, it appers that there may have been a fix made to texlive. I'm no longer seeing this failure.
That appears to have done the trick. Thanks!
I don't have lua 5.5 yet, so this patch is just a guess based on the "changes" section of the README on their web site. Could you please try it?
Fails to build with lua 5.5
Mouse coordinates in multiplots
Yay! Multiplots are now at long last now mouseable in 6.1 Well, except for some weird cases like non-linear axis mappings.
multiplot mousing: gnuplot.doc document multiplot mousing
multiplot mousing: project_notes documentation of this implementation
multiplot_mousing: A nonlinear axis mapping must not persist across panels
multiplot_mousing: update_active_region() is no longer needed
multiplot mousing: 3D rotation in all panels
multiplot mousing: move panel bookkeeping from gadgets.c to multiplot.c
multiplot mousing: correct logic errors in axis mapping and playback
multiplot mousing: queue pan/zoom event from hotkey and apply it later
multiplot mousing: track panel in which the most recent mouse event was accepted
multiplot mousing: classify panel content in panel_flags[]
multiplot mousing: Finally! mouse readout for all panels of a multiplot
multiplot_mousing.dem
comments: revisit and/or remove old FIXMEs
I am not able to reproduce this. Is your browser not able to display the SVG on-line demos? https://gnuplot.sourceforge.net/demo_svg_6.0/ What O/S and browser are you using? I would be happy to look a patch, but it will be hard to test and evaluate if I can't reproduce the problem.
logscale - Too many axis ticks requested
It turns out that the failure was due to round-off error in testing initial tickmark placement against the range endpoints. After adding an allowance for floating-point round-off to integer values everything seems to be working.
Fix poor tic placement no logscale axis that spans exactly two decades
Fix poor tic placement no logscale axis that spans exactly two decades
Do not allow to load $GPVAL_LAST_MULTIPLOT from inside a multiplot
psdoc: avoid missing characters in TeX font lasy
Do not allow to load $GPVAL_LAST_MULTIPLOT from inside a multiplot
gnuplot_svg.js cannot create JSON with settings
Hmm. OK. I saw something else initially but now I can reproduce your report. I don't know what is going on here.
The syntax is set xtics <incr> | <start>, <incr> {,<end>}, so my command set xtics 10 is correct too, actually it is equivalent to your command set xtics 1.e6, 10. Neither your command nor my command produce meaningful x-axis tics. Only default setting of xtics (no command) produces correct tics on x-axis, even though the default settins should be eqivalent to: set xtics 10 or set xtics 1e6,10 or set xtics 1e6,1e8
The syntax is set xtics <start>,<increment>{,<end>}. For log scale axes the increment is multiplicative rather than additive. So to place major tics as you describe, the command would be set xtics 1.e6, 10 Which is what you get by default. Minor tics are a separate command, but what you describe (I thiink) is also what you get by default.
I disagree. There should be no error message. On x-axis with logarithmic scaling and "set xtics 10" I expect major tic on every decimal-multiple value, and 8 minor tics between major tics (for 2-, 3-, 4-, 5-, 6-, 7-, 8-, 9-multiple). The range 1e6-1e9 contains 28 tics. The range 1e6-1e8 should contain 19 tics, and that is far from "1e+07" tics, therefore the message is nonsense.
Version 6.0 patchlevel 3
But the error message is correct, right? What tick placement are you trying to obtain?
Hi Ethan, I have put considerable effort into fixing this and just wanted to let you know that I have a working fix. It addresses all of the comments you had and it generates output that looks very similar to what is generated by pngcairo at a fraction of the computational cost. The fixed patch now: Supports dashes for all truecolor capable libgd terminals, but falls back to solid lines when truecolor is turned off. Supports rounded, butt and square endcaps and uses round joins at steep angles to...
Hi Ethan, I have put considerable effort into fixing this and just wanted to let you know that I have a working fix. It addresses all of the comments you had and looks very similar to the output generated by pngcairo at a fraction of the computational cost. The fixed patch now: Supports dashes for all truecolor capable libgd terminals, but falls back to solid lines when truecolor is turned off. Supports rounded, butt and square endcaps and uses round joins at steep angles to prevent gaps in the lines....
Hi Ethan, I have put considerable effort into fixing this and just wanted to let you know that I have a working fix. I addresses all of the comments you had and looks very similar to the output generated by pngcairo at a fraction of the computational cost. The fixed patch now: Supports dashes for all truecolor capable libgd terminals, but falls back to solid lines when truecolor is turned off. Supports rounded, butt and square endcaps and uses round joins at steep angles to prevent gaps in the lines....
Thanks for checking out the patch. Your concerns about this approach of rendering the dashes as straight tangents to the curve are definitely warranted. I personally did not see the issue because when I used the patched png terminal to produce my plots (which had more rapidly changing slopes than in the example above) I was using only relatively thin lines (max lw = 3) and short dashes or dot patterns. For your example script, the issue was confounded because you were using a custom dash pattern,...
ReGIS output cleared after display
ps_fontfile_doc.pdf fails to build with texlive 20250308
empty cell in extra column makes data point disappear
This has been the behavior back at least as far as version 5.0 (11 years ago). The program assumes a uniform format for the input line, so when it sees 3 or more columns of data in the first line that sets an expectation that subsequent lines will provide the same. Lines will fewer columns are then flagged as containing "missing" data, which is why the point is omitted. You demonstrate this by providing only two values on the first line of data. Specifying using 1:2 tells the program explicitly that...
empty cell in extra column makes data point disappear
Back from vacation, looking at the patch now... I don't have any previous experience with AI-generated code, so I don't know how much paranoia to approach this with. First thoughts I get a couple of compiler warnings, but those are minor and I won't bother with them now. It seems like a lot of code. Maybe that's necessary. Major issue Unfortunately I don't think this implementation actually does what is needed. It fails to follow the continuous path of a line; instead it connects only line segment...
logscale - Too many axis ticks requested
logscale - Too many axis ticks requested
http://gnuplot.info/help.html links no longer working
accept the command "set encoding EUC_JP"
psdoc: avoid missing characters in TeX font lasy
docs: airy Ai Bi
Here is a proper fix that avoids the missing characters.
Attached is a patch that removes the LASY10 column from the document. Does this work for you?
I can reproduce the error messages from texlive2025, but as you say the output pdf file seems correct. Switching to lualatex and font wasy yields similar error messages and a similar pdf output file. I take it you are invoking the "make pdf" from inside something else (rpmbuild?) Is there a way to tell it to ignore the error? Can you remove the .../docs/psdoc make target from your build script? I suspect that the entire mechanism being documented - embedding Type 1 fonts in a PostScript file output...
ps_fontfile_doc.pdf fails to build with texlive 20250308
plot style "with labels" silently ignores "noenhanced" setting
checking for plot title should not consume "noenhanced"
protect against segfault in test for nonlinear axis
differentiate between "replot" and "remultiplot"
Well, EUC-JP string "2025\xc7\xaf" are printed correctly for set encoding locale, set encoding "EUC_JP", and without "set encoding" command. The compound string of EUC-JP character and "\U+xxxx" are also printed correctly for the same situation. Thank you.
I tested current git version. Then the script all.dem stopped at the command "test palette" in pm3d.dem. gnuplot> set encoding EUC_JP ^ line 68: unrecognized encoding specification; see 'help encoding'. I tested on wxt terminal, then the same message appeared for the case "set encoding locale": gnuplot> set encoding default gnuplot> test palette # no problem gnuplot> set encoding locale gnuplot> test palette gnuplot> set encoding EUC_JP ^ line 68: unrecognized encoding specification; see 'help encoding'....
It would have been possible to add large parts of this patch directly to libgd, which indeed would have been the better solution, but gnuplot would still have to be patched to utilize the new capabilities. Additionally, the changes in how antialiasing with this patch works in general are significant and I found it quite unlikely that such a long-established library would adopt them. Also, I do not have a lot of experience with these kind of libraries and although I have tested this patch quite a...
I'm traveling and will have alook ar your patch when I return next week. In the meantime, just a question. IsYour code something that could be added to the libgd library itself? If so that would benefit not just gnuplot but all other users of the library. I have contributed fixes to libgd before so I know they are receptive. Thanks for your contribution.
Are patches still considered? Should I have posted this somewhere else?
As an example of what is possible with the new dashtype support, I have attached the output of the follwing example script: set samples 500 set xrange [0:4*pi] set yrange [-1.5:7.5] set xlabel "x" set ylabel "y" set title "Antialiased Dashed Lines Test" font ",14" set key right top box opaque set grid # Define line styles with different dash types and colors set style line 1 lc rgb "#E41A1C" lw 1 dt solid # Red - solid set style line 2 lc rgb "#377EB8" lw 2 dt 2 # Blue - dashed set style line 3 lc...
Full dashtype support for libgd terminals and improved antialiasing quality
plot style "with labels" silently ignores "noenhanced" setting
displaying key sample in "with pm3d" style with explicit fillcolor
'set mouse mouseformat' directly passing user defined format to 'snprintf()'
Do not disable mousing after a ^C
save axis mappings across a "reset" command
sixeltek: transparency and background options
allow plotting with dashtype specified by a numerical expression
malformed html on titlepage of html documentation
sixeltek terminal: transparency and background options
sixeltek: transparency and background options
Allow replacement of a single line in a data block
Thanks for catching that. It used to be k == 1, to at least have one sixel line written (and then it should now be k == ks) but from testing it seems the condition can be omitted entirely because a dash is output which moves to the next line. Incidentally, but I guess that is another ticket, the y-size should be a multiple of 6 for sixels. And setting the size to for example 640,366 the image is not complete with the "test" command; this used to be the correct with earlier gnuplot versions, before...
In file included from term.h:170, from term.c:1311: ../term/tek.trm: In function ‘SIXEL_text’: ../term/tek.trm:817:57: warning: self-comparison always evaluates to true [-Wtautological-compare] 817 | if (n < b_xsize-1 || pc != '?' || k == k) { /* do not output empty lines */ | ^~ What is the intent here?
sixeltek terminal: transparency and background options
The clear screen escape sequence is sent by term_reset(), which is invoked when you either (1) made another plot, (2) change the terminal type or settings, or (3) exit the program. I believe the intent was that the plot would remain visible on your screen until you did one of those things. However the "set output" / "unset output" commands are treated as changed the terminal settings. term_reset() appends the clear screen sequence to the output file when it is closed. This is/was probably not ideal...
ReGIS output cleared after display
Improvement of datablock size retrieval performance
Thank you for accepting the feature request and implementing the fix! I really appreciate it. This will make working with large datablocks much more practical.
The difference will go away if you tell the program to treat a coordinate whose value is found to be NaN the same as a coordinate that is missing from the input data. set datafile missing NaN The next question is obviously "why does $2*$1/$1 evaluate to NaN while $2+10 apparently does not?". Good question. When reading in a line of data, the program returns an error flag DF_MISSING to indicate that a required coordinate is missing. The test for that condition is trivial if the coordinate is simply...
Sorry, that should have been commit 7f0dfb24
I had to wrap the character array in a new structure typedef struct data_array { struct array_header header; char **data; } data_array; Commit 42849f98 It was not too messy, although it introduces additional steps in initializing the data block. I think I found everywhere that need modification, but I almost missed a spot in the "test palette" code so I worry a bit that I might also have missed some other non-obvious case. Timing is now equivalent for your test cases: [~/git/gnuplot/src] ./gnuplot...
wrap the lines of a datablock (or function block) in a structure
Improvement of datablock size retrieval performance
6.0.4 does not compile with BACKWARD_COMPATIBILITY
Thanks.
fix: compile failure if BACKWARD_COMPATIBILITY is defined