On Fri, 9 Nov 2012, Henrique Andrade wrote:
When using "advanced" Gnuplot command I'm getting an
error and
a syntax highlighting "flaw". Please take a look at the attached .inp
file (also reproduced below):
<hansl>
open australia.gdt
[...]
# Error!
gnuplot E IAU IUS {set style line 1 lc rgb "#ff0000"; set style line 2 \
lc rgb "#2CC81D"; set style line 3 lc rgb "#0000ff";} --time-series
--with-lines --single-yaxis --output=display
</hansl>
The problem here is that your line-continuing backslash is
being masked by the '#' character, which usually indicates the
start of a comment (though it obviously doesn't here). This is
fallout from an attempted bug-fix of a few days ago. It should
now be fixed properly in CVS and snapshots.
The syntax highlighting problem occurs with the first
"set"
statement inside the curly brackets (the syntax is gone).
Well, that's sort of a buglet within a buglet. We shouldn't
really be using hansl syntax highlighting for embedded gnuplot
commands. It just so happens that "set" is a valid command in
both languages, but of course in hansl a command-word cannot
immediately follow "{" so it doesn't get highlighted there.
If I can figure out a way to make gtksourceview switch
highlighting modes (or just turn off highlighting altogether
in this context) that would be nice, but I don't know if it's
possible.
Allin