gnuplot-beta — Developers and beta testers of new gnuplot code

Re: Touchup of history.c

[Petr M. <mi...@ph...>]

> > > I think you can use simply
> > >   if (isanumber(c_token)) {
> > > 	act on integer
> > >   }
> 
> Unfortunately not.
> "isanumber" is mis-named. It really acts as "isapositivenumber".
> The reason is that the tokensiser places the - sign into its
> own separate token.  So isanumber(c_token) sees only the '-' sign,
> no number.
> 
> This has annoyed me many times, but never sufficiently to
> replace isanumber() with something better.

Does this mean that it is not possible to add a function "isaninteger()" 
that woul work for negative numbers as well?

---
PM

Re: Touchup of history.c

[Ethan A M. <merritt@u.washington.edu>]

On Monday 11 June 2007 12:41, Daniel J Sebald wrote:
> > 
> > I think you can use simply
> >   if (isanumber(c_token)) {
> > 	act on integer
> >   }

Unfortunately not.
"isanumber" is mis-named. It really acts as "isapositivenumber".
The reason is that the tokensiser places the - sign into its
own separate token.  So isanumber(c_token) sees only the '-' sign,
no number.

This has annoyed me many times, but never sufficiently to
replace isanumber() with something better.

-- 
Ethan A Merritt

Re: pgf/TikZ terminal for (La)TeX

[Ethan M. <merritt@u.washington.edu>]

On Sunday 10 June 2007 10:43, Mojca Miklavec wrote:
> 
> A slight disadvantage is that - yes, you need at least one additional
> TeX package (TikZ) that doesn't come by default on any linux system
> except Debian

I seem to have 
   /usr/share/texmf/tex/latex/pgf/tikz.sty

via tetex-latex-3.0-18.1mdv2007.0
on Mandriva 2007.1

Do I need something more than this?


> The code is really preliminary, but it works (lacks color, proper font
> switching, some fancy features - but all that is much easier to add
> than to "standard LaTeX" terminal). If anyone on the list is
> interested in preliminary testing (I will upload it to patches, but
> it's not ready yet for public) and is able to compile the following

I'm always interested, but also increasingly short of time.

Could you sketch out how you would use this to create files for pdflatex?
Would it be similar to using epslatex, in that the output is one pdf file
and one TeX file?

	Ethan


> Hello World on the system:
> 
> \documentclass{article}
> \usepackage{tikz}
> \begin{document}
> \begin{tikzpicture}
> \draw (1,0)--(5,2);
> \end{tikzpicture}
> \end{document}
> 
> I can send him/her the code.
> 
> Mojca

-- 
Ethan A Merritt

bug report gnuplot 4.3 patchlevel 0

[Thomas V. <tho...@it...>]

Hi guys,
here I send you the output I get loading a gnuplot file written by gnuplot 
itself (same version, of course) using the "save" command:

vogel@xxx:yyy>gnuplot -V    
gnuplot 4.3 patchlevel 0
vogel@xxx:yyy>gnuplot

Terminal type set to 'x11'
gnuplot> load 'Eall.vglTN.gnuplot'

gnuplot> set ytics border in scale 1,0.5 mirror norotate  offset character 0, 
0, 0 -0.150000,0.01,0.150000
                                                                                            
^
         "Eall.vglTN.gnuplot", line 98: invalid expression 

gnuplot> 

Here the file Eall.vglTN.gnuplot

vogel@xxx:yyy>cat -n Eall.vglTN.gnuplot
     1  #!/opt/gnuplot-4.3/bin/gnuplot -persist
     2  #
     3  #    
     4  #       G N U P L O T
     5  #       Version 4.3 patchlevel 0
     6  #       last modified February 2007
     7  #       System: Linux 2.6.17-2-686
     8  #    
     9  #       Copyright (C) 1986 - 1993, 1998, 2004, 2007
    10  #       Thomas Williams, Colin Kelley and many others
    11  #    
    12  #       Type `help` to access the on-line reference manual.
    13  #       The gnuplot FAQ is available from
    14  #               http://www.gnuplot.info/faq/
    15  #    
    16  #       Send comments and help requests to  
<gnu...@li...>
    17  #       Send bug reports and suggestions to 
<gnu...@li...>
    18  #    
    19  # set terminal x11 
    20  # set output
    21  unset clip points
    22  set clip one
    23  unset clip two
    24  set bar 1.000000
    25  set border 31 front linetype -1 linewidth 1.000
    26  set xdata
    27  set ydata
    28  set zdata
    29  set x2data
    30  set y2data
    31  set timefmt x "%d/%m/%y,%H:%M"
    32  set timefmt y "%d/%m/%y,%H:%M"
    33  set timefmt z "%d/%m/%y,%H:%M"
    34  set timefmt x2 "%d/%m/%y,%H:%M"
    35  set timefmt y2 "%d/%m/%y,%H:%M"
    36  set timefmt cb "%d/%m/%y,%H:%M"
    37  set boxwidth
    38  set style fill  empty border
    39  set style rectangle back fc  lt -3 fillstyle   solid 1.00 border -1
    40  set dummy x,y
    41  set format x "% g"
    42  set format y "% g"
    43  set format x2 "% g"
    44  set format y2 "% g"
    45  set format z "% g"
    46  set format cb "% g"
    47  set angles radians
    48  set grid nopolar
    49  set grid xtics nomxtics ytics nomytics noztics nomztics \
    50   nox2tics nomx2tics noy2tics nomy2tics nocbtics nomcbtics
    51  set grid layerdefault   linetype 0 linewidth 1.000,  linetype 0 
linewidth 1.000
    52  set key title ""
    53  set key inside right top vertical Right noreverse enhanced autotitles 
nobox
    54  set key noinvert samplen 4 spacing 1 width 0 height 0 
    55  unset label
    56  unset arrow
    57  set style increment default
    58  unset style line
    59  unset style arrow
    60  set style histogram clustered gap 2 title  offset character 0, 0, 0
    61  unset logscale
    62  set offsets 0, 0, 0, 0
    63  set pointsize 1
    64  set encoding default
    65  unset polar
    66  unset parametric
    67  unset decimalsign
    68  set view 60, 30, 1, 1
    69  set samples 100, 100
    70  set isosamples 10, 10
    71  set surface
    72  unset contour
    73  set clabel '%8.3g'
    74  set mapping cartesian
    75  set datafile separator whitespace
    76  unset hidden3d
    77  set cntrparam order 4
    78  set cntrparam linear
    79  set cntrparam levels auto 5
    80  set cntrparam points 5
    81  set size ratio 0 1,1
    82  set origin 0,0
    83  set style data points
    84  set style function lines
    85  set xzeroaxis linetype -2 linewidth 1.000
    86  set yzeroaxis linetype -2 linewidth 1.000
    87  set zzeroaxis linetype -2 linewidth 1.000
    88  set x2zeroaxis linetype -2 linewidth 1.000
    89  set y2zeroaxis linetype -2 linewidth 1.000
    90  set ticslevel 0.5
    91  set mxtics default
    92  set mytics default
    93  set mztics default
    94  set mx2tics default
    95  set my2tics default
    96  set mcbtics default
    97  set xtics border in scale 1,0.5 mirror norotate  offset character 0, 
0, 0 0.600000,0.02,1.30000
    98  set ytics border in scale 1,0.5 mirror norotate  offset character 0, 
0, 0 -0.150000,0.01,0.150000
    99  set ztics border in scale 1,0.5 nomirror norotate  offset character 0, 
0, 0 autofreq 
   100  set nox2tics
   101  set noy2tics
   102  set cbtics border in scale 1,0.5 mirror norotate  offset character 0, 
0, 0 autofreq 
   103  set title "" 
   104  set title  offset character 0, 0, 0 font "" norotate
   105  set timestamp bottom 
   106  set timestamp "" 
   107  set timestamp  offset character 0, 0, 0 font "" norotate
   108  set rrange [ * : * ] noreverse nowriteback  # (currently 
[0.00000:10.0000] )
   109  set trange [ * : * ] noreverse nowriteback  # (currently 
[-5.00000:5.00000] )
   110  set urange [ * : * ] noreverse nowriteback  # (currently 
[-5.00000:5.00000] )
   111  set vrange [ * : * ] noreverse nowriteback  # (currently 
[-5.00000:5.00000] )
   112  set xlabel "" 
   113  set xlabel  offset character 0, 0, 0 font "" textcolor lt -1 norotate
   114  set x2label "" 
   115  set x2label  offset character 0, 0, 0 font "" textcolor lt -1 norotate
   116  set xrange [ 0.590000 : 1.26000 ] noreverse nowriteback
   117  set x2range [ * : * ] noreverse nowriteback  # (currently 
[-10.0000:10.0000] )
   118  set ylabel "" 
   119  set ylabel  offset character 0, 0, 0 font "" textcolor lt -1 rotate by 
90
   120  set y2label "" 
   121  set y2label  offset character 0, 0, 0 font "" textcolor lt -1 rotate 
by 90
   122  set yrange [ -0.150000 : 0.150000 ] noreverse nowriteback
   123  set y2range [ * : * ] noreverse nowriteback  # (currently 
[-10.0000:10.0000] )
   124  set zlabel "" 
   125  set zlabel  offset character 0, 0, 0 font "" textcolor lt -1 norotate
   126  set zrange [ * : * ] noreverse nowriteback  # (currently 
[-10.0000:10.0000] )
   127  set cblabel "" 
   128  set cblabel  offset character 0, 0, 0 font "" textcolor lt -1 norotate
   129  set cbrange [ * : * ] noreverse nowriteback  # (currently 
[-10.0000:10.0000] )
   130  set zero 1e-08
   131  set lmargin  -1
   132  set bmargin  -1
   133  set rmargin  -1
   134  set tmargin  -1
   135  set locale "C"
   136  set pm3d explicit at s
   137  set pm3d scansautomatic
   138  set pm3d interpolate 1,1 flush begin noftriangles nohidden3d 
corners2color mean
   139  set palette positive nops_allcF maxcolors 0 gamma 1.5 color model RGB 
   140  set palette rgbformulae 7, 5, 15
   141  set colorbox default
   142  set colorbox vertical origin screen 0.9, 0.2, 0 size screen 0.05, 0.6, 
0 bdefault
   143  set loadpath 
   144  set fontpath 
   145  set fit noerrorvariables
   146  GNUTERM = "x11"
   147  plot 'Eall.vglTN.dat' u 1:($2-$3) w p, 0
   148  #    EOF


Thanks for doing the job!
Cheers, Thomas



-- 
Thomas Vogel

Universität Leipzig
Fakultät für Physik und Geowissenschaften
Vor dem Hospitaltore 1
D-04103 Leipzig 
 
e-mail: tho...@it... 

Re: Touchup of history.c

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

I've noticed that currently for --with-realine=builtin on CVS the history stack 
will be truncated upon add_history().  E.g.,

gnuplot> history
     1  set his 6
     2  his
     3  plot x
     4  plot x*x
     5  history
gnuplot> set his 2
gnuplot> foo = 2
gnuplot> his
     1  foo = 2
     2  his
gnuplot>

The GNU readline compilation doesn't do that.  Truncation is only done when 
saving to file.

Which way should history behave?  (I'm thinking to not truncate history list 
until saved, both GNU and builtin.)

Dan

Re: Touchup of history.c

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

Petr Mikulik wrote:

>>n = 1;
>>if (equals(c_token,"-")) {
>>    n *= -1;
>>    c_token++;
>>} else if (equals(c_token,"+"))
>>    c_token++;
>>n *= int_expression();
> 
> 
> I think you can use simply
>   if (isanumber(c_token)) {
> 	act on integer
>   }

That's what it currently does:

	} else if (isanumber(c_token)) {
	    /* show history entries */
	    n = int_expression();

'+' and '-' must test negative for isanumber().

Dan

Re: Touchup of history.c

[Petr M. <mi...@ph...>]

> > I propose "set history 0" means not to store history commands to the 
> > .gnuplot_history file.
>
> I assume you mean that the .gnuplot_history file remains as it was when 
> the user entered gnuplot, not that the .gnuplot_history ends up empty.

yes

> > > > >Several of these options may be overridden by similar qualifiers in the
> > > > >history command.
> > > > >     set history {<int>}
> > > >
> > > >I tried that "set history -1" makes an error.
> > >
> > >gnuplot> set history -1
> > >                     ^
> > >         Unrecognized option.
> > >
> > >Are you getting something else? 
> > 
> > 
> > I get the same.
> > 
> > 
> >  Of course, that means the following also
> > 
> > 
> > >Should we be recognizing the sign and then issuing an error if negative?
> > 
> > 
> > Yes.
> 
> I began programming this, but now I hesitate to do so.  It would be something
> like
> 
> n = 1;
> if (equals(c_token,"-")) {
>     n *= -1;
>     c_token++;
> } else if (equals(c_token,"+"))
>     c_token++;
> n *= int_expression();

I think you can use simply
  if (isanumber(c_token)) {
	act on integer
  }

---
PM

Re: Touchup of history.c

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

Petr Mikulik wrote:
>>>>Several of these options may be overridden by similar qualifiers in the
>>>>history command.
>>>>     set history {<int>}
>>>
>>>I tried that "set history -1" makes an error.
>>
>>gnuplot> set history -1
>>                     ^
>>         Unrecognized option.
>>
>>Are you getting something else? 
> 
> 
> I get the same.
> 
> 
>  Of course, that means the following also
> 
> 
>>Should we be recognizing the sign and then issuing an error if negative?
> 
> 
> Yes.

I began programming this, but now I hesitate to do so.  It would be something like

n = 1;
if (equals(c_token,"-")) {
     n *= -1;
     c_token++;
} else if (equals(c_token,"+"))
     c_token++;
n *= int_expression();

But to repeat this code in more than one spot wouldn't be good.  There should 
maybe be "signed_expression()" inside parse.h.

However, on second thought, just leaving it as is makes the user be a little 
cleaner in their use of integers.  I don't think it is good practice for users 
to be doing

set history +3

etc.  That simply clutters things.  I suggest leaving it as is with the 
"Unrecognized option" error.

Dan

Re: Touchup of history.c

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

Daniel J Sebald wrote:

>> I propose "set history 0" means not to store history commands to the 
>> .gnuplot_history file.

I assume you mean that the .gnuplot_history file remains as it was when the user 
entered gnuplot, not that the .gnuplot_history ends up empty.

Dan

Re: Touchup of history.c

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

Petr Mikulik wrote:
>> The value <int> indicates the value of history size when leaving gnuplot.  It
>> is used for truncating the history to at most that many lines.  The default
>> is 666.
>>
>>[snip]
>>
>> `unset history` will set history operation to its default settings: no
>> history
>> truncation at exit and thus allow indefinite number of lines, `condensed`,
>> and
>> `numbered`.
>>
>>In one case the default is 666 in the other it is indefinite.  There is no
>>"set history inf" or anything like that.
> 
> 
> 9999 could be enough... Anyway, you cannot store infinite number of commands 
> on a PC with a finite hard disk.

I'm wondering what number could represent the principle of "indefinite".  We 
wouldn't want a syntax "set history -1"... but good point, the user could just 
type in a huge number.  It's just slightly odd that there does exist such a 
setting but the way to get to it is to "unset history".

Dan

Re: Touchup of history.c

[Petr M. <mi...@ph...>]

>  The value <int> indicates the value of history size when leaving gnuplot.  It
>  is used for truncating the history to at most that many lines.  The default
>  is 666.
> 
> [snip]
> 
>  `unset history` will set history operation to its default settings: no
>  history
>  truncation at exit and thus allow indefinite number of lines, `condensed`,
>  and
>  `numbered`.
> 
> In one case the default is 666 in the other it is indefinite.  There is no
> "set history inf" or anything like that.

9999 could be enough... Anyway, you cannot store infinite number of commands 
on a PC with a finite hard disk.

---
PM

Re: Touchup of history.c

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

Petr Mikulik wrote:

>> For "set history 0", could you
>>
>>>please document whether is never forgets anything?
>>
>>What should "history 0" do?  In the code, n=0 means print everything but that
>>doesn't mean we can't issue an error.
> 
> 
> I propose "set history 0" means not to store history commands to the 
> .gnuplot_history file.

Hmm, that might be OK.  The documentation is a bit inconsistent.  If we choose 0 
to mean 0 lines go to the history file.  How do we set the history to 
"unlimited"?  The answer is "unset history".  That's a bit strange in the sense 
that the documentation says:

  The value <int> indicates the value of history size when leaving gnuplot.  It
  is used for truncating the history to at most that many lines.  The default
  is 666.

[snip]

  `unset history` will set history operation to its default settings: no history
  truncation at exit and thus allow indefinite number of lines, `condensed`, and
  `numbered`.

In one case the default is 666 in the other it is indefinite.  There is no "set 
history inf" or anything like that.

Dan

Re: Touchup of history.c

[Petr M. <mi...@ph...>]

> > >Several of these options may be overridden by similar qualifiers in the
> > >history command.
> > >      set history {<int>}
> > 
> > I tried that "set history -1" makes an error.
> 
> gnuplot> set history -1
>                      ^
>          Unrecognized option.
> 
> Are you getting something else? 

I get the same.


 Of course, that means the following also

> Should we be recognizing the sign and then issuing an error if negative?

Yes.

>  For "set history 0", could you
> > please document whether is never forgets anything?
> 
> What should "history 0" do?  In the code, n=0 means print everything but that
> doesn't mean we can't issue an error.

I propose "set history 0" means not to store history commands to the 
.gnuplot_history file.

---
PM

Re: Touchup of history.c

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

Petr Mikulik wrote:
>>Command line history may be controlled with several options described
>>below.
>>Several of these options may be overridden by similar qualifiers in the
>>history command.
>>      set history {<int>}
> 
> 
> I tried that "set history -1" makes an error.

I get:

gnuplot> set history -1
                      ^
          Unrecognized option.

Are you getting something else?  Of course, that means the following also errors:

gnuplot> set history +4
                      ^
          Unrecognized option.

Should we be recognizing the sign and then issuing an error if negative?


  For "set history 0", could you
> please document whether is never forgets anything?

What should "history 0" do?  In the code, n=0 means print everything but that 
doesn't mean we can't issue an error.

Dan

Order of initialization?

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

I'm trying to debug the "set term x11 <windowID>" feature and have a question. 
What should be the sequence of initialization for terminals?  If one looks at 
xlib/x11 terminals, CVS is coded like this:

X11_options()
{
[snip]
     X11_init();
[snip--code using X11_ipc]
}


TERM_PUBLIC void
Xlib_init()
{
     /* x11.trm thinks it is writing to a private pipe, but here we */
     /* set it to use the channel opened by 'set output <file>'     */
     X11_ipc = gpoutfile;

fprintf(stderr,"xlib_init\n");
#ifdef PIPE_IPC
     /* There is, of course, no mouse feedback */
     ipc_back_fd = IPC_BACK_UNUSABLE;
#endif
}

Also, the xlib term has X11_options in its table.  Now when the code is run, the 
sequence appears to be:

gnuplot> set term xlib 5

1) Terminal type set to 'xlib'

2) X11_options() ...

3) ... which in turn calls X11_init(), given the code we see above.

gnuplot> plot x

4) Xlib_init(), which sets X11_ipc.


The consequence of this, if you haven't been following the flow is that "set 
term xlib" first has a series of commands in the X11_options code that actually 
goes out to gnuplot_x11 rather than being recorded to gpoutfile.  (I'd like to 
see what those are... that's why I'm asking.)  So, the questions are:

Why doesn't the init function come before the options function in the sequence?

Why is X11_init() in the middle of the X11_options function?  Something seems 
contradictory there.  If the X11_init() needs to come before writing anything to 
X11_ipc, it comes back to the first question of why the core code doesn't do a 
term->init before the term->options.

Dan

Re: Patches item #1729825 ready to go.

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

Petr Mikulik wrote:
>>Two unresolved things.
>>
>>1) What should be the default for {full|ignoredups|condensed}?  And why?
> 
> 
> condensed -- it is the current behaviour, and it speeds us browsing and 
> mouse-copying previous commands

There's an updated patch on SourceForge.  "condensed" is default.


>>2) Can we deprecate "historysize".  (I've currently programmed "set history
>><n>" and "set historysize <n>" to be the same.)
> 
> 
> change it to 'set history size'

As Ethan pointed out, just leaving the match string "his$storysize" allows both

set historysize <n>
set history <n>

to work.  Of course, that means "set historysize {<n>} {quiet|numbered} 
{condensed|ignoredups|full}" works, but because the options are documented as 
"set history", the user will not be inclinde to type "set historysize ignoredups".

BTW, I didn't use the phrase "erasedups" (i.e., "condensed") because we aren't 
technically erasing anything.

Dan

pgf/TikZ terminal for (La)TeX

[Mojca M. <moj...@gm...>]

Hello,

I was a bit bored today and decided to rewrite the ConTeXt terminal to
spit out some (La)TeX-friendly code in TikZ (there is currently no
decent LaTeX terminal except epslatex which doesn't work with pdfTeX).

The big advantage of TikZ is that it's fully portable (it works with
plain TeX, LaTeX and ConTeXt, and works with e-TeX+dvips, pdfTeX,
XeTeX, LuaTeX, 4ht, ... you name it), and much more powerful and
standard than any other other ancient graphic hacks (plenty of
terminals which don't work with anything except LaTeX+dvips).

A slight disadvantage is that - yes, you need at least one additional
TeX package (TikZ) that doesn't come by default on any linux system
except Debian (some people make effort to bring it to other platforms
as well).

The code is really preliminary, but it works (lacks color, proper font
switching, some fancy features - but all that is much easier to add
than to "standard LaTeX" terminal). If anyone on the list is
interested in preliminary testing (I will upload it to patches, but
it's not ready yet for public) and is able to compile the following
Hello World on the system:

\documentclass{article}
\usepackage{tikz}
\begin{document}
\begin{tikzpicture}
\draw (1,0)--(5,2);
\end{tikzpicture}
\end{document}

I can send him/her the code.

Mojca

Re: Patches item #1729825 ready to go.

[Petr M. <mi...@ph...>]

> Two unresolved things.
> 
> 1) What should be the default for {full|ignoredups|condensed}?  And why?

condensed -- it is the current behaviour, and it speeds us browsing and 
mouse-copying previous commands

> 2) Can we deprecate "historysize".  (I've currently programmed "set history
> <n>" and "set historysize <n>" to be the same.)

change it to 'set history size'

---
PM

Winding down patches...

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

Due to an probable change of venue in the coming weeks, I will likely not have 
time for gnuplot code as I occassionally have had in the past.  If there are any 
code bugs or features, or any sourceforge patches that people want me to look 
at, now is time.

Dan

Re: gnuplot-beta Digest, Vol 12, Issue 10

[m s. <mw...@us...>]

> ----- Original Message -----
> From: "Ethan Merritt" <merritt@u.washington.edu>
> To: gnu...@li...
> Subject: Re: gnuplot-beta Digest, Vol 12, Issue 10
> Date: Mon, 4 Jun 2007 16:01:09 -0700
>=20
>=20
> On Monday 04 June 2007 13:14, Ethan Merritt wrote:
> > On Sunday 03 June 2007 19:48, m sutton wrote:
> > > I would like a couple of my patches to be considered for=20
> > inclusion into CVS:
> > > >  1659135  	  dashed grid for GD term to accept linewidths
> >
> > OK, that's better than the earlier version.
>=20
> On closer inspection, I'm not entirely happy.
> This line:
>=20
>          static int png_linetype_dotted[MAXLINEWIDTH*MAXLINEWIDTH*5];
>=20
> ties up 0.2 MByte permanently, on the off-chance that we want
> to change the grid width.  Yeah I know, virtual memory is cheap these day=
s.
> But it's ugly.  Doesn't 200,000,000 bytes of storage to specify
> a 2+3 dot pattern seem a little outrageous?
>=20

I originally selected static to avoid alloc/free overhead.  Feel free to ch=
ange to dynamic allocation.

Regards,

Mike Sutton


--=20
Get a Free E-mail Account at Mail.com!
Choose From 100+ Personalized Domains
Visit http://www.mail.com today

Re: Patches item #1729825 ready to go.

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

Daniel J Sebald wrote:
> Ethan Merritt wrote:
> 
>>On Friday 08 June 2007 11:11, Daniel J Sebald wrote:
>>
>>
>>>2) Can we deprecate "historysize".  (I've currently programmed "set history <n>" 
>>>and "set historysize <n>" to be the same.)
>>
>>
>>??
>>I don't understand the question.
>>For as far back as I have sources for, "set history" has always been
>>shorthand for "set historysize".  What, exactly, would you be deprecating?
>>If you just mean:
>>
>>tables.c
>>182: -    { "his$torysize", S_HISTORYSIZE },
>>182: +    { "his$tory", S_HISTORYSIZE },
>>
>>I don't see any point.

Oh, I see what you are saying.  Under the gnuplot.doc entry for

?commands set historysize
?set historysize
?unset historysize
?historysize
?nohistorysize

just change every 'historysize' to 'history' and no one will know the 
difference.  Is that what you meant?

Dan

Re: Patches item #1729825 ready to go.

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

Ethan Merritt wrote:
> On Friday 08 June 2007 11:11, Daniel J Sebald wrote:
> 
>>2) Can we deprecate "historysize".  (I've currently programmed "set history <n>" 
>>and "set historysize <n>" to be the same.)
> 
> 
> ??
> I don't understand the question.
> For as far back as I have sources for, "set history" has always been
> shorthand for "set historysize".  What, exactly, would you be deprecating?
> If you just mean:
> 
> tables.c
> 182: -    { "his$torysize", S_HISTORYSIZE },
> 182: +    { "his$tory", S_HISTORYSIZE },
> 
> I don't see any point.

Well, the following would be kind of awkward:

   Syntax:
         set historysize {<int>} {numbered|quiet} {full|ignoredups|condensed}
         unset historysize

(We're changing the properties of the history.  Not the historysize.)

I've changed the table to

      { "hid$den3d", S_HIDDEN3D },
-    { "his$torysize", S_HISTORYSIZE },
+    { "his$tory", S_HISTORY },
+    { "historys$ize", S_HISTORYSIZE },
      { "is$osamples", S_ISOSAMPLES },

so that

   set his #
   set historys #

do the same thing.  I'm fine with leaving it like that, but just wonder if 
retaining "historysize" as duplicate behavior is that important.

Dan

Re: Patches item #1729825 ready to go.

[Ethan M. <merritt@u.washington.edu>]

On Friday 08 June 2007 11:11, Daniel J Sebald wrote:
> 
> 2) Can we deprecate "historysize".  (I've currently programmed "set history <n>" 
> and "set historysize <n>" to be the same.)

??
I don't understand the question.
For as far back as I have sources for, "set history" has always been
shorthand for "set historysize".  What, exactly, would you be deprecating?
If you just mean:

tables.c
182: -    { "his$torysize", S_HISTORYSIZE },
182: +    { "his$tory", S_HISTORYSIZE },

I don't see any point.


-- 
Ethan A Merritt

Re: Patches item #1729825 ready to go.

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

Before I make changes, lets agree on behavior.  Below is a rewrite of the 
documentation.  Basically, the rule is never discard anything from history, 
simply display and next/previous through it according to one of three modes 
resembling the bash shell options.

Two unresolved things.

1) What should be the default for {full|ignoredups|condensed}?  And why?

2) Can we deprecate "historysize".  (I've currently programmed "set history <n>" 
and "set historysize <n>" to be the same.)

Dan


-----------

?commands set history
?set history
?unset history
  Note: the command `set history` is only available when gnuplot has been
  gnuplot has been configured with the GNU readline or its own history feature.

  Syntax:
        set history {<int>} {numbered|quiet} {full|ignoredups|condensed}
        unset history

  The value <int> indicates the value of history size when leaving gnuplot.  It
  is used for truncating the history to at most that many lines. The default
  is 666.  The option `quiet` will suppress numbers alongside the history, which
  is useful for mouse copy and paste.

  Options `full`, `ignoredups` and `condensed` control the manner in which
  history is displayed and the way in which next/previous step through history.
  In `full` mode, gnuplot shows every history entry.  In `ignoredups` mode,
  whenever there are back-to-back duplicate entries only one is listed.  It is
  similar in appearance to bash shell history with the "ignoredups" option, but
  no commands are actually discarded from gnuplot's history list.  `condensed`
  mode results in a displayed history with only the most recent unique entries
  and is similar in appearance to bash shell history with the "erasedups"
  configuration.  Again, no commands are actually discarded from history in any
  of the modes.  This ensures that repeated recall from history by number with
  the same number produces the same command.

  `unset history` will set history operation to its default settings: no history
  truncation at exit and thus allow indefinite number of lines, `full`, and
  `numbered`.

----------------

?commands history
?history
  `history` command lists, saves or executes previous entries in the history of
  the command line editing.  The history list is retained in full and as typed
  by the user.  However, gnuplot may be configured (see `set history`) to display
  the history in a variety of abbreviated and quiet formats.  In quiet format, no
  numbers are listed next to the history commands.  In condensed format, only the
  most recent of any repeated commands is shown.  In ignoredups format, only one
  of a succession of duplicate entries is show.  The examples below illustrate
  several other features:

        history               # show the history
        history 5             # show last 5 entries in the history
        history quiet 5       # show last 5 entries without entry numbers
        history numbered 5    # show last 5 entries with entry numbers
        history "hist.gp"     # write the complete history to file hist.gp
        history "hist.gp" append # append the complete history to file hist.gp
        history 10 "hist.gp"  # write last 10 commands to file hist.gp
        history 10 "|head -5 >>diary.gp" # write 5 history commands using pipe
        history ?load         # show all history entries starting with "load"
        history ?"set c"      # like above, several words enclosed in quotes
        hi !reread            # execute last entry starting with "reread"
        hist !"set xr"        # like above, several words enclosed in quotes
        hi !hi                # possibly recursive, see note below
        hi !123               # execute entry numbered 123 in the history list
        history full 10       # show every line of last 10 entries
        history condensed     # show only most recent unique history entries
        history ignoredups    # show just one of contiguous duplicate entries
        hi clear              # clear all entries from the history

  On systems which support a popen function (Unix), the output of history can be
  piped through an external program by starting the file name with a '|', as one
  of the above examples demonstrates.

  Use of ! to execute old commands in the history list have the potential to be
  recursive.  For example "hi !hi" may be directly recursive if it itself was
  the most recent command.  However, there are more indirect, non-obvious ways
  to an infinite recursion.  For this reason, gnuplot will stop if in any series
  of history commands the same line is executed twice.

Re: Patches item #1729825 ready to go.

[Ethan M. <merritt@u.washington.edu>]

On Friday 08 June 2007 09:26, Daniel J Sebald wrote:
> 
> Got it.  I suppose removing spaces is analogous to removing redundant lines.  So 
> rather than toss out the spaces, in condensed mode I could do comparison tests 
> based upon spaces removed rather than actually removing the spaces.

I agree with <pl...@pi...>
Please do not remove spaces when doing string comparisons.
To do it correctly, you'd have to build a whole command parsing system
into the history routines.

-- 
Ethan A Merritt