Re: [Gnuplot-bugs] Script parsing in version 4.0 (testcase)

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

On Thu, 22 Apr 2004, Hans-Bernhard Broeker wrote:

> That suggests two possible reasons:
> 
> 1) Command line length
> 2) Timing
> 
> I suspect the latter, since running this on Linux with a different
> terminal than X11, like this:
> 
> 	cat test.gp | env GNUTERM=dumb gnuplot -persist
> 
> gave me a plot instead of any error message.

I'll eat those words and claim the opposite: it *is* about line length,
and I've found out why.  

The crucial bit is that one of your backslashes from line continuations
falls exactly onto the border where the input_line buffer is extended by
another KiB, i.e. when read_line() calls extend_input_line() in line 2476
of command.c.  The problem is the 'continue' that follows this call --- it
jumps across the handling of backslash-newline.  Patch is under 
construction.

The reason this doesn't happen if you 'load' this same script, I think, is
that the gnuplot prompt is formally part of the input line, i.e. your
critical point gets shifted by a couple of charactes, and the problem
disappears.

-- 
Hans-Bernhard Broeker (br...@ph...)
Even if all the snow were burnt, ashes would remain.