6:24 p.m.
Em 9 de novembro de 2012, Allin Cottrell escreveu:
On Fri, 9 Nov 2012, Johannes Lips wrote:
> I am happy with the enable switch but I would like to ask
> which patch from cvs I need to apply against 1.9.10 or are
> you planning on releasing a new version to fix those small
> issues?
I'm thinking it would be a good idea to release 1.9.11
shortly, with the build/install issues fixed, so that
packagers don't have to mess with patches. (We're fortunate
that by now gretl is well supported by the major Linux
distributions.)
The one complication is that current CVS contains some
substantial internal changes in the handling of user-defined
variables (other than regular series) relative to 1.9.10, and
while these are quite well tested I'd prefer that they are
more fully tested before doing another release.
I think that a time-scale of putting out 1.9.11 next week will
probably work. In the meantime it would be very helpful if
people who are using 1.9.10cvs could beat on the program and
look for any problems. In particular, one area where I'm not
100% confident is the behavior of the GUI icon view and/or
scalars editor when an executing script makes relevant changes
(adding, deleting or redefining scalars, matrices or bundles).
The question is: is the icon view staying properly in sync?
(If it's not, this can lead to weirdness and the danger of a
crash.)
Dear Allin, I have a small error/misbehavior list that I think
would be good to address before Gretl 1.9.11:
<hansl>
open australia.gdt
series morethan15characters = PAU
series really_muchmorethan15characters = PUS
"Teste VAR" <- var 4 E morethan15characters \
really_muchmorethan15characters
fcast
</hansl>
Open in Icon view crashes Gretl and output formatting is weird (the var
names are truncated on model presentations and aren't on F-Tests re-
sults. Additionally, the var names on the forecast results are too large.
<hansl>
open australia.gdt
series morethan15characters = PAU
series really_muchmorethan15characters = PUS
"Teste VEC" <- coint2 1 E morethan15characters \
really_muchmorethan15characters
</hansl>
Output formating is weird.
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
# Ok!
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
# Ok!
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
# Ok!
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
# 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 syntax highlighting problem occurs with the first "set"
statement inside the curly brackets (the syntax is gone).
Best regards
--
Henrique Andrade*
*
6:46 p.m.
On Fri, 9 Nov 2012, Henrique Andrade wrote:
Dear Allin, I have a small error/misbehavior list that I think
would be good to address before Gretl 1.9.11:
Thanks, this is very useful.
<hansl>
open australia.gdt
series morethan15characters = PAU
series really_muchmorethan15characters = PUS
"Teste VAR" <- var 4 E morethan15characters \
really_muchmorethan15characters
fcast
</hansl>
I plan to fix problems associated with variable names of more
than 15 characters, but not necessarily before 1.9.11. After
all, the documentation still says the limit is 15: very long
names are still a "secret" experimental feature.
In fact, maybe we ought to reset the limit to 15 for the
1.9.11 release so that users who haven't read the docs and
happen to use very long names don't see horrible output or
crashes, then immediately reset it to 31 in CVS after the
release and work some more on the needed fixes.
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)...
OK, I'll look into that.
Allin
9:30 p.m.
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
4179
days inactive
4179
days old
2 comments
2 participants
participants (2)
-
Allin Cottrell -
Henrique Andrade