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

[Dima K. <gn...@di...>]

> On Sat, 20 Oct 2012 10:20:32 -0700
> "sfeam (Ethan Merritt)" <eam...@gm...> wrote:
>
> 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....
> 

The options I chose (-q, --no-init-file) are what emacs uses. If some other
program uses other letters, I'd be ok with those as well. I do feel we should
match SOME precedent, instead of making up our own.


> > 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".

OK. Sounds like there are two different use cases. One for tests during
development (use case you described) and another for deployment, i.e. when a
distribution package maintainer is running the unit tests as part of the
packaging process. For the latter, it makes sense to run without user-defined
.gnuplot.

dima