Currently it isn't possible to capture the output of non file format outputs directly when using the library, to allow using for example SVG outputs without having to write and read temporary files it would be preferable be able to access the output from the calling Rust code.
I have somewhat looked into implementing this and can see two ways this could be implemented. Either by adding support for specifying the stdout for the gnuplot Command::new in show_and_keep_running and having a way to access the process piped stdout from CloseSentinel
Or by adding a new method similar to how show works but instead of returning CloseSentinel the method would return the command output directly.
I have proof of concept available at Neutroni@7bde03a still mostly untested but if either or both implementations seem sensible I can actually test the code and create PR.
Currently it isn't possible to capture the output of non file format outputs directly when using the library, to allow using for example SVG outputs without having to write and read temporary files it would be preferable be able to access the output from the calling Rust code.
I have somewhat looked into implementing this and can see two ways this could be implemented. Either by adding support for specifying the stdout for the gnuplot
Command::newinshow_and_keep_runningand having a way to access the process piped stdout fromCloseSentinelOr by adding a new method similar to how
showworks but instead of returningCloseSentinelthe method would return the command output directly.I have proof of concept available at Neutroni@7bde03a still mostly untested but if either or both implementations seem sensible I can actually test the code and create PR.