Re: Compile warnings in new post/pslatex terminal code

[Hans-Bernhard B. <br...@ph...>]

Harald Harders wrote:

>     set title '\hello'
> why is it saved as
>     set title "\\hello"
> ? 

Because by the time 'save' operates, it no longer knows if you 
originally use '' or "" quotes.  And because there are some things in a 
string that could only have gotten in there using "" syntax, most 
importantly literal linebreaks.  So, at that point, always using "" 
syntax and escaping all non-printable characters on their out from 
internal storage to the file is the only available option.

>>And while we're at it: I have serious usability reservations about the
>>'header' option.  It's barely usable for your example prefixing two
>>simple \usepackage lines --- this really should be a header taken from a
>>file, instead.
> 
> 
> I don't agree. It is useful to be able to make some local header additions
> in a gnuplot script. 

I'm not debating that.  I'm debating the user interface to getting that 
effect.  Two shortish LaTeX command lines may still reasonably fit into 
a single gnuplot command line, but there comes a point at which it 
becomes highly repetitive and stressful command line editing.  That's 
why I requested taking these header snippets from a separate file as an 
additional option, not as a replacement of the existing one.

Come to think of it, maybe I'm simply against the entire "standalong" 
thingy --- it's not doing anything that a typical LaTeX user can't 
easily do with a quickly typed framework document instead.

>>At least it should be allowed to keep it in a separate file.
> 
> 
> It is already: If gnuplot.cfg is in the LaTeX path it is loaded. This may
> be in the current working directory or somewhere in $TEXMF.

A default configuration file is not exactly what I had in mind, either. 
   I was talking about giving file name instead of the literal string, 
so the string can be pulled from that file, instead of having to become 
part of the already quite crowded "set terminal epslatex" line.