"caca driver ncurses" terminal does not work properly
vladimiroltean opened this issue · 2 comments
vladimiroltean commented
Hi,
I am in need of a way to run feedgnuplot in a command-line-only environment, and the "dumb" terminal does not look too good. Compiling gnuplot 5.2 with "./configure --with-caca" gives me a feedgnuplot environment where:
- Replotting does not work. Although I get output, the following gets printed: "line 5: warning: refresh not possible and replot is disabled"
- I cannot kill feedgnuplot interactively (does not respond to Ctrl-c, Ctrl-z, q, x).
I know these probably sound more like caca terminal implementation bugs, but I don't know enough about how gnuplot works in order to be able to debug it. Can you please help identify the source of these issues?
Thanks,
Vladimir
P.S. this is not a joke
dkogan commented
Vladimir Oltean <notifications@github.com> writes:
I am in need of a way to run feedgnuplot in a command-line-only environment, and the "dumb" terminal does not look too good. Compiling gnuplot 5.2 with "./configure --with-caca" gives me a feedgnuplot environment where:
* Replotting does not work. Although I get output, the following gets printed: "line 5: warning: refresh not possible and replot is disabled"
* I cannot kill feedgnuplot interactively (does not respond to Ctrl-c, Ctrl-z, q, x).
I know these probably sound more like caca terminal implementation bugs, but I don't know enough about how gnuplot works in order to be able to debug it. Can you please help identify the source of these issues?
I've never used the caca gnuplot terminal, so don't know much about it.
In general, feedgnuplot doesn't plot anything itself: it just generates
a gnuplot command, which is sent to gnuplot, and IT does all the work.
You can produce this command by passing --dump to feedgnuplot. Then you
can pass it onto gnuplot yourself by either pasting it into a gnuplot
session, or saving it to a file and invoking
load "file"
in gnuplot, where "file" is the --dump output. Try that. If it looks
like you're still having issues, then gnuplot is at fault. The
maintainer is relatively responsive to bug reports, so do talk to them
via either the bug tracker or the gnuplot-beta mailing list.
dkogan commented
Closing for no activity