Re: [PATCH] Unit tests don't use the local user's .gnuplot file

[sfeam (E. Merritt) <eam...@gm...>]

On Saturday, 20 October 2012, Dima Kogan wrote:
> I'm attaching a patch to add a "-q" option to gnuplot to suppress parsing of
> .gnuplot and gnuplotrc files. 

I like the idea of providing a way to suppress reading ~/.gnuplot.

Minor quibble: Isn't "-q" usually short for "--quiet" and interpreted
as a request to suppress output rather than input?
Not that I have a better letter of the alphabet to suggest....

> This is done primarily so that unit tests test the stock configuration

Hmm. I usually want the opposite.
E.g. if I want to make sure that "set someoption obscure" doesn't
trigger memory leaks, I put it in ~/.gnuplot and then run the
unit tests under valgrind.
For simple doesn't-crash sanity checks after applying a patch,
I usually add any relevant options to ~/.gnuplot and run
"make check".

	Ethan