wgnuplot (since ~version 5.2 ? ) dies instantly when trying to copy something out of the console window.
Unfortunately, not always. I have no clue on how to reliably reproduce, I think it happens more often when copying multiple lines of text. It definitely occured to me on several different machines, win7 and win10.
Just now it happened, I reloaded wgnuplot, marked some text again, pressed CTRL+Ins, it crashed, I reloaded, tried again ~20x, then next crash.
The text that's supposed to be copied is not in the clipboard after the crash.
This is what windows gives me for problem details:
Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: wgnuplot.exe
Anwendungsversion: 0.0.0.0
Anwendungszeitstempel: 5fdb00a1
Fehlermodulname: msvcrt.dll
Fehlermodulversion: 7.0.7601.17744
Fehlermodulzeitstempel: 4eeb033f
Ausnahmecode: c0000005
Ausnahmeoffset: 0000000000001235
Betriebsystemversion: 6.1.7601.2.1.0.256.48
Gebietsschema-ID: 1031
Zusatzinformation 1: 8e3c
Zusatzinformation 2: 8e3c0209261cc99d98be93397a84985b
Zusatzinformation 3: a71e
Zusatzinformation 4: a71e897266ea9c3758ae4720e4535539
It may be a totally different issue, but readline 8.1 broke copy/paste to or from the gnuplot command line and requires a fix to the code. It's in our git repository for both 5.4 and 5.5 but arrived too late to make it into the 5.4.3 release.
Yea, copypasting into gnuplot is also a bit broken. Tabs trigger the filename completion, and I yesterday noticed that unix LF line endings just vanish on windows (i.e. when copypasting out of a browser). I can't build a windows version now unfortunately to check.
Last edit: Karl Ratzsch 2022-02-23
For gnuplot for windows, GNU Readline is not recommended to be linked in config/mingw/Makefile
As far as I know, windows binaries has never been linked with the GNU Readline.
Last edit: Tatsuro MATSUOKA 2022-02-23
For CTRL+Ins hang on wgnuplot, I could reproduce on 5.4 and 5.5.
I cannot say that CTRL+Ins hang and Tabs trigger the filename completion unix LF line endings just vanish on windows are the same origin.
Sounds like separate issues, yes. Should I file as a new bug?
My opinion is that it is better to file as sparate issues on the bug ticket.