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

[Daniel J S. <dan...@ie...>]

On 10/20/2012 12:20 PM, sfeam (Ethan Merritt) 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?

Yes, save "-q" for "--quiet".


> Not that I have a better letter of the alphabet to suggest....

Tossing out some ideas:

   -n, --nostartup
   -s, --skip
   -f, --factory

No great ones there.  Any others?

Dan

PS:  I just noticed on the help output that there is a comma missing for 
the "-p" entry:

Usage: gnuplot [OPTION]... [FILE]
for X11 options see 'help X11->command-line-options'
   -V, --version
   -h, --help
   -p  --persist
   -e  "command1; command2; ..."

>
>> 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
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
>

-- 

Dan Sebald
email: daniel(DOT)sebald(AT)ieee(DOT)org
URL: http://www(DOT)dansebald(DOT)com