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

Re: width of text in latex terminals

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

On Monday 14 March 2005 09:02 am, Robert Hart wrote:
> Is there any plans to improve the method of estimating the width of text
> strings for pslatex plots?

No.

> Is this something that could fit into the existing enhanced text support
> (used by other terminals). Or would the terminal drivers need to be
> extended with an optional "strlen" function?

There is a new dummy driver in the current cvs version called
"estimate.trm" that is used internally to do exactly what you 
want for strings using gnuplot's own enhanced text mode.

But that is not going to get you a full TeX interpreter inside
gnuplot.  



-- 
Ethan A Merritt       merritt@u.washington.edu
Biomolecular Structure Center
Mailstop 357742
University of Washington, Seattle, WA 98195

Re: ./prepare fails

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

On Saturday 12 March 2005 07:39 pm, Jeff Hagen wrote:
> 
> 	I am trying to install the gnuplot beta so that I can play around with 
> histograms.... I get to the point of running prepare then it fails. It can 
> not find config.guess and config.sub....

Yes.
I have that same problem.
It seems to be a recent autoconf bug.

The work-around is to create empty instances of these files before hand,
and they will be replaced with correct ones.

[1] touch config.guess config.sub
[2] ./prepare
[3] ./configure


Having done this once, you may never have to do it again.
I have run into to this on 3 separate machines, but in each case
only the initial installation was affected.

There is a similar long-standing problem with the way gnuplot's
./configure file tries to initialize the local lisp directories.
I have not been able to figure out a clean way around this.
Best to disable lisp processing with

./configure --without-lisp-files

If you really need the lisp stuff, you may have to dummy up a
couple of files in the appropriate system directories.


-- 
Ethan A Merritt       merritt@u.washington.edu
Biomolecular Structure Center
Mailstop 357742
University of Washington, Seattle, WA 98195

width of text in latex terminals

[Robert H. <en...@no...>]

Is there any plans to improve the method of estimating the width of text
strings for pslatex plots?

e.g something like:
set format y '[r]{%.0t$\times$10$^{%+03T}$}'
ends up with a huge gap between the border of the plot and yaxis label
because gnuplot assumes the tic labels are much bigger than the actually
are.

I think the only real way of getting the length of a text string would
be to run it through LaTeX, and that isn't really feasible, but I think
a much better estimate of the length of the string could be got by
neglecting "{}$^_" and counting "\somecommand" as one character (i.e.
assuming it produces a single symbol).

Is this something that could fit into the existing enhanced text support
(used by other terminals). Or would the terminal drivers need to be
extended with an optional "strlen" function?

Rob



-- 
Robert Hart <en...@no...>
University of Nottingham


This message has been checked for viruses but the contents of an attachment
may still contain software viruses, which could damage your computer system:
you are advised to perform your own checks. Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.

Re: pslatex code contaminating the gnuplot core

[Harald H. <h.h...@tu...>]

On Mon, 14 Mar 2005, Hans-Bernhard Broeker wrote:

> Ethan Merritt wrote:
>
> > Yes, but no other terminal driver that I know of interprets this as
> > meaning that the back labels are underneath *everything* else.
>
> Well, it's not really the terminal drivers that are doing that job
> at all.  So far, "layers" are implemented only by the core.  The
> terminal drivers don't know what the core is doing.  It's this lack of
> knowledge that is causing the problem at hand in epslatex.  It could be
> hacked around inside the driver, e.g. by outputting the \includegraphics
> line the moment the core issues the first non-text command to the
> terminal, but I think I'd prefer a term->set_layer() over such an approach.

Yes, I have tried to find another solution, but I did not know a better
workaround than this one.

> That would essentially mean the {e}pslatex type of driver is a lost
> cause.  Given the very high opinion about its usefulness everybody seems
> to share, esp. after its recent overhaul, I find it hard to accept such
> a point of view.
>
> Epslatex with a separate PostScript file, unless changed somewhat
> radically, to support more than one graphical output file to be
> intermixed with the texts, will be inherently limited in its support of
> a more generalized layering of gnuplot's output, but I don't agree that
> we shouldn't even try to support such ordering because of that.

I have also thought of splitting the graphic part of the output. But this
would mean to have three output files which would be a bad thing. I am
aware that the 'back' option in the epslatex terminal is different than in
other terminals. Of course, it would be nice if the 'back' option would
behave as in the other terminals. But it is still better if it works at
least similarly and allows the user to place labels behind portions of the
graph than to ignore the 'back' option at all.

Thus, we really should find a good solution for this implementation
problem without removing the feature 'back' in epslatex.

Regards
Harald

-- 
Harald Harders
h.h...@tu...
http://www.harald-harders.de

Re: pslatex code contaminating the gnuplot core

[Robert H. <en...@no...>]

On Mon, 2005-03-14 at 16:27 +0100, Hans-Bernhard Broeker wrote:
> It could be
> hacked around inside the driver, e.g. by outputting the \includegraphics
> line the moment the core issues the first non-text command to the
> terminal

Is that really such a bad idea? It seems to fit with the semantics
currently used by the core and the other terminals. 

The multi-layer approach either requires that the core output the
various layers in order (in which case nothing has really changed), or
that most terminals buffer up all the graphics for each layer and
composite them all together at the end (which is a lot of extra hassle
for no real gain). I suppose it would make sense for things like .fig
which actually have real layers.

Rob

-- 
Robert Hart <en...@no...>
University of Nottingham


This message has been checked for viruses but the contents of an attachment
may still contain software viruses, which could damage your computer system:
you are advised to perform your own checks. Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.

Re: ./prepare fails

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

Jeff Hagen wrote:
> 	I am trying to install the gnuplot beta so that I can play around with 
> histograms.... I get to the point of running prepare then it fails. It can 
> not find config.guess and config.sub....

That's quite wrong indeed --- it's not supposed to need those files, so 
it shouldn't be looking for them.

[...]
> rm -f Makefile.am Makefile.amt
> sed -n '1,/^##plt-files-begin/p' Makefile.am.in > Makefile.amt
> echo PLT_FILES = *.plt | fmt | (tr '\012' @; echo ) \
>   |sed 's/@$/%/;s/@/ \\@/g;' | tr @% '\012 ' >> Makefile.amt
> sed -n '/^##plt-files-end/,$p' Makefile.am.in >> Makefile.amt
> chmod a-w Makefile.amt
> mv Makefile.amt Makefile.am

These are from running the preparation rules in 'tutorial'.  The next 
step is to run aclocal, automake and autoconf in 'lisp':

> automake: configure.in: required file `../config.guess' not found
> automake: configure.in: required file `../config.sub' not found

There are references in the lisp/configure I get from autoconf-2.58,
but neither aclocal nor automake of version 1.7.9 emits this error, 
AFAICS.  This points to some local auto-tools hickup on your end.

Re: pslatex code contaminating the gnuplot core

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

Ethan Merritt wrote:

> Yes, but no other terminal driver that I know of interprets this as 
> meaning that the back labels are underneath *everything* else.

Well, it's not really the terminal drivers that are doing that job
at all.  So far, "layers" are implemented only by the core.  The
terminal drivers don't know what the core is doing.  It's this lack of
knowledge that is causing the problem at hand in epslatex.  It could be
hacked around inside the driver, e.g. by outputting the \includegraphics
line the moment the core issues the first non-text command to the
terminal, but I think I'd prefer a term->set_layer() over such an approach.

What the core does is it goes through all the labels twice, once rather
early in the process, for the "back" labels, once after everything else,
for the "front" labels.  That's why there are two calls to
place_labels() in do_plot(), and place_labels() takes a "layer" argument.

> I think you can argue that if intermixing the order of labels and 
> other plot elements is important, then epslatex is the wrong terminal
>  driver to use in the first place.

That would essentially mean the {e}pslatex type of driver is a lost
cause.  Given the very high opinion about its usefulness everybody seems
to share, esp. after its recent overhaul, I find it hard to accept such
a point of view.

Epslatex with a separate PostScript file, unless changed somewhat
radically, to support more than one graphical output file to be
intermixed with the texts, will be inherently limited in its support of
a more generalized layering of gnuplot's output, but I don't agree that
we shouldn't even try to support such ordering because of that.

Re: ./prepare fails

[Lars H. <lhe...@us...>]

Jeff Hagen writes:
> Hello all,
> 
> 	I am trying to install the gnuplot beta so that I can play around with 
> histograms.... I get to the point of running prepare then it fails. It can 
> not find config.guess and config.sub....
> 
> A (long) log of activity follows... I have checked to make sure that it is not 
> in fact checking out those files.
> 
> Please CC me in any replies as I am not a member of the mailinglist.
 
[...]
> rm -f Makefile.am Makefile.amt
> sed -n '1,/^##plt-files-begin/p' Makefile.am.in > Makefile.amt
> echo PLT_FILES = *.plt | fmt | (tr '\012' @; echo ) \
>   |sed 's/@$/%/;s/@/ \\@/g;' | tr @% '\012 ' >> Makefile.amt
> sed -n '/^##plt-files-end/,$p' Makefile.am.in >> Makefile.amt
> chmod a-w Makefile.amt
> mv Makefile.amt Makefile.am
> automake: configure.in: required file `../config.guess' not found
> automake: configure.in: required file `../config.sub' not found
 
 I cannot reproduce this. Which versions of autoconf and automake are
 you using? gnuplot requires autoconf 2.52 or newer, and you really should
 use the latest versions available (autoconf 2.59/automake 1.9.5).

Re: pslatex code contaminating the gnuplot core

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

On Sunday 13 March 2005 01:16 pm, Hans-Bernhard Broeker wrote:
> Ethan Merritt wrote:
>
> > Is it really so important to be able to write labels behind the plot?
>
> It could be --- that's why we *have* back/front options on 'set label'
> and other commands, in the first place.  

Yes, but no other terminal driver that I know of interprets this as
meaning that the back labels are underneath *everything* else. Only
that they are underneath the actual plot lines/points/surfaces and
of course underneath any front labels.  

I think you can argue that if intermixing the order of labels and other
plot elements is important, then epslatex is the wrong terminal driver
to use in the first place. Its prime function is to separate the handling
of text and non-text items.  If you need tighter control over the mixed
placement of text and non-text, then the plain old post/eps driver would
be a better choice.

-- 
Ethan A Merritt
Biomolecular Structure Center
University of Washington 98195-7742

Re: pslatex code contaminating the gnuplot core

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

On Sunday 13 March 2005 01:16 pm, Hans-Bernhard Broeker wrote:
>  A proposition:  let's say we do add a
> term->changelayer(int layer) function, to be called by the core at
> appropriate places (and in strictly ascending order of 'layer').  The
> numbers passed to this function would have a meaning only to the core,
> but be documented somewhere.  What currently has options 'front' /
> 'back' would become layers 1 and 30000, e.g., and be documented as such.

I am not very enthusiastic about this.  
I can see a multitude of questions that arise immediately.

Is the core code always required to generate a series of these benchmark
calls, on the off-chance that a terminal driver is looking for a particular
transition?  
For example, does the terminal test routing test_command() have to call
term->changelayer(N) many times? Once? Never?
Is the value of N guaranteed to be strictly increasing?

Any driver implementing (term->changelayer)() must now keep extra state
information, possibly a lot of extra state information.
Suppose there is an int_error() or some other event that terminates
the sequence of layering calls prematurely.  Does the terminal driver
have to recognize this and reset its state when it receives the next
plot command?

Can this scheme co-exist with multiplot mode?
I would expect that the component graphs in a multiplot would each
step through some identical sequence of layering numbers, so that
the overall sequence would be something like
a,b,c,...,j        Operations setting up the page as a whole
k,l,...,n          Operations producing subplot 1
k,l,...,n          Operations producing subplot 2
...
k,l,...,n          Operations producing subplot <N>
o,p,...,z          Operations closing out the page as a whole
But this would mean that the layering calls are *not* strictly monotonic.
So now what does a driver do if it notices that the layer has jumped back
from n to k?  Ignore it?  Assume multiplotting is in progress?  
If somewhere in the range k...n there is a transition point, should the
driver allow it to trigger multiple times?

Would these term->changelayer calls have to be passed through to
outboard drivers like gnuplot_x11?  

Would the calls be regenerated during zoom commands
or other operations triggered by hot-keys?

-- 
Ethan A Merritt
Biomolecular Structure Center
University of Washington 98195-7742

Re: pslatex code contaminating the gnuplot core

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

Ethan Merritt wrote:
> On Sunday 13 March 2005 11:34 am, Hans-Bernhard Broeker wrote:

>> The issue is not how they're defined, the issue is which parts of
>> the programs know about, and use them.  The terminal API shouldn't
>> have to know about the meanings of individual layers' designators.

> But that is exactly what the epslatex driver *does* claim to want.

The wish to do that is not entirely unreasonable.  But the method to
fulfill it needs reconsideration.  A proposition:  let's say we do add a
term->changelayer(int layer) function, to be called by the core at
appropriate places (and in strictly ascending order of 'layer').  The
numbers passed to this function would have a meaning only to the core,
but be documented somewhere.  What currently has options 'front' /
'back' would become layers 1 and 30000, e.g., and be documented as such.

The epslatex driver could then output its \includegraphics line as the
layer number crosses a certain number (hardcoded, possibly configurable
by a 'set term' option).

> Is it really so important to be able to write labels behind the plot?
> 
It could be --- that's why we *have* back/front options on 'set label'
and other commands, in the first place.  A more obvious candidate would
be the on-axis tick labels in a plot like this:

	set xtics axis
	set xzeroaxis ; set yzeroaxis
	splot x*y

Having these labels appear in front of the plotted data would be
visually very disturbing, creating an Escher-like appearance.

Re: pslatex code contaminating the gnuplot core

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

Harald Harders wrote:
> On Thu, 10 Mar 2005, Hans-Bernhard Broeker wrote:

>>I don't thus think that *naming* the layers would be a good idea at all.
>>Let them have numbers, and export those to the user interface in some
>>way the users can (hopefully) understand.

> Would you prefer something like this? Or how do you think it should be
> implemented?

A heap of #define'd numbers offer exactly no improvement over an enum 
--- they'ld actually be worse.

The issue is not how they're defined, the issue is which parts of the 
programs know about, and use them.  The terminal API shouldn't have to 
know about the meanings of individual layers' designators.

./prepare fails

[Jeff H. <unu...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello all,

	I am trying to install the gnuplot beta so that I can play around with 
histograms.... I get to the point of running prepare then it fails. It can 
not find config.guess and config.sub....

A (long) log of activity follows... I have checked to make sure that it is not 
in fact checking out those files.

Please CC me in any replies as I am not a member of the mailinglist.

Thanks,
	Jeff Hagen
	jh...@uc...

- ------ Log follows-----------

[root@Dalek gnuplot]# mkdir gnuplot
[root@Dalek gnuplot]# export 
CVSROOT=:pserver:ano...@cv...:/cvsroot/gnuplot
[root@Dalek gnuplot]# cvs login
Logging in to :pserver:ano...@cv...:2401/cvsroot/gnuplot
CVS password:
[root@Dalek gnuplot]# cvs -z3 checkout gnuplot
cvs checkout: Updating gnuplot
U gnuplot/.cvsignore
U gnuplot/BUGS
U gnuplot/ChangeLog
U gnuplot/ChangeLog.0
U gnuplot/CodeStyle
U gnuplot/Copyright
U gnuplot/FAQ
U gnuplot/GNUmakefile
U gnuplot/INSTALL
U gnuplot/INSTALL.gnu
U gnuplot/Makefile.am
U gnuplot/Makefile.maint
U gnuplot/NEWS
U gnuplot/PATCHLEVEL
U gnuplot/PGPKEYS
U gnuplot/PORTING
U gnuplot/README
U gnuplot/README.1ST
U gnuplot/README.exp
U gnuplot/TODO
U gnuplot/VERSION
U gnuplot/configure.in
U gnuplot/configure.vms
U gnuplot/depcomp
U gnuplot/install-sh
U gnuplot/missing
U gnuplot/mkinstalldirs
U gnuplot/prepare
U gnuplot/stamp-h.in
cvs checkout: Updating gnuplot/NeXT
cvs checkout: Updating gnuplot/NeXT/English.lproj
cvs checkout: Updating gnuplot/NeXT/English.lproj/GnuTerm.nib
cvs checkout: Updating gnuplot/NeXT/English.lproj/gnuview.nib
cvs checkout: Updating gnuplot/beos
cvs checkout: Updating gnuplot/config
U gnuplot/config/.cvsignore
U gnuplot/config/Makefile.am.in
U gnuplot/config/README
U gnuplot/config/buildvms.com
U gnuplot/config/config.amg
U gnuplot/config/config.cyg
U gnuplot/config/config.mgw
U gnuplot/config/config.nt
U gnuplot/config/config.os2
U gnuplot/config/djconfig.sh
U gnuplot/config/make_vms.com
U gnuplot/config/makefile.286
U gnuplot/config/makefile.amg
U gnuplot/config/makefile.ami
U gnuplot/config/makefile.cyg
U gnuplot/config/makefile.dj2
U gnuplot/config/makefile.emx
U gnuplot/config/makefile.g
U gnuplot/config/makefile.mgw
U gnuplot/config/makefile.msc
U gnuplot/config/makefile.msw
U gnuplot/config/makefile.mto
U gnuplot/config/makefile.nt
U gnuplot/config/makefile.os2
U gnuplot/config/makefile.os9
U gnuplot/config/makefile.st
U gnuplot/config/makefile.tc
U gnuplot/config/makefile.unx
U gnuplot/config/makefile.vms
U gnuplot/config/makefile.wc
U gnuplot/config/makefile.win
U gnuplot/config/makefile.ztc
U gnuplot/config/term_pc.h
cvs checkout: Updating gnuplot/config/MacOSX
U gnuplot/config/MacOSX/ReadMe.rtf
U gnuplot/config/MacOSX/createdist.sh
U gnuplot/config/MacOSX/gnuplot.packproj
cvs checkout: Updating gnuplot/config/MacOSX/PkgResources
U gnuplot/config/MacOSX/PkgResources/InstallationCheck
U gnuplot/config/MacOSX/PkgResources/License.rtf
U gnuplot/config/MacOSX/PkgResources/postinstall
cvs checkout: Updating gnuplot/config/MacOSX/PkgResources/English.lproj
U gnuplot/config/MacOSX/PkgResources/English.lproj/InstallationCheck.strings
cvs checkout: Updating gnuplot/demo
U gnuplot/demo/.cvsignore
U gnuplot/demo/1.dat
U gnuplot/demo/2.dat
U gnuplot/demo/3.dat
U gnuplot/demo/Makefile.am.in
U gnuplot/demo/airfoil.dem
U gnuplot/demo/all.dem
U gnuplot/demo/animate.dem
U gnuplot/demo/arrowstyle.dat
U gnuplot/demo/arrowstyle.dem
U gnuplot/demo/asciimat.dat
U gnuplot/demo/battery.dat
U gnuplot/demo/big_peak.dat
U gnuplot/demo/binary.dem
U gnuplot/demo/bivariat.dem
U gnuplot/demo/blutux.rgb
U gnuplot/demo/borders.dem
U gnuplot/demo/candlesticks.dat
U gnuplot/demo/candlesticks.dem
U gnuplot/demo/charset.dem
U gnuplot/demo/clip14in.dat
U gnuplot/demo/colorwheel.dem
U gnuplot/demo/contours.dem
U gnuplot/demo/controls.dem
U gnuplot/demo/ctg-y2.dat
U gnuplot/demo/dashcolor.dem
U gnuplot/demo/datastrings.dem
U gnuplot/demo/demo.edf
U gnuplot/demo/density.fnc
U gnuplot/demo/discrete.dem
U gnuplot/demo/electron.dem
U gnuplot/demo/enhancedtext.dem
U gnuplot/demo/epslatex.dem
U gnuplot/demo/fillbetween.dem
U gnuplot/demo/fillcrvs.dem
U gnuplot/demo/fillstyle.dem
U gnuplot/demo/fit.dem
U gnuplot/demo/fontfile.dem
U gnuplot/demo/fontfile_latex.dem
U gnuplot/demo/glass.dat
U gnuplot/demo/gnuplot.cfg
U gnuplot/demo/gnuplot.rot
U gnuplot/demo/hemisphr.dat
U gnuplot/demo/hexa.fnc
U gnuplot/demo/hidden.dem
U gnuplot/demo/histograms.dem
U gnuplot/demo/histograms2.dem
U gnuplot/demo/image.dem
U gnuplot/demo/immigration.dat
U gnuplot/demo/keystroke.dem
U gnuplot/demo/klein.dat
U gnuplot/demo/labelplot.pdb
U gnuplot/demo/layout.dem
U gnuplot/demo/lcdemo.dat
U gnuplot/demo/line.fnc
U gnuplot/demo/macros.dem
U gnuplot/demo/mgr.dem
U gnuplot/demo/moli3.dat
U gnuplot/demo/mousevariables.dem
U gnuplot/demo/multimsh.dem
U gnuplot/demo/multiplt.dem
U gnuplot/demo/nearmap.csv
U gnuplot/demo/param.dem
U gnuplot/demo/pm3d.dem
U gnuplot/demo/pm3dcolors.dem
U gnuplot/demo/pm3dgamma.dem
U gnuplot/demo/pointsize.dem
U gnuplot/demo/polar.dem
U gnuplot/demo/poldat.dem
U gnuplot/demo/prob.dem
U gnuplot/demo/prob2.dem
U gnuplot/demo/rainbow.dem
U gnuplot/demo/random.dem
U gnuplot/demo/reflect.fnc
U gnuplot/demo/scatter.dem
U gnuplot/demo/scatter2.bin
U gnuplot/demo/scatter2.dat
U gnuplot/demo/silver.dat
U gnuplot/demo/simple.dem
U gnuplot/demo/sine.bin
U gnuplot/demo/singulr.dem
U gnuplot/demo/sound.par
U gnuplot/demo/sound2.par
U gnuplot/demo/soundvel.dat
U gnuplot/demo/spline.dem
U gnuplot/demo/srl.dat
U gnuplot/demo/starmap.dem
U gnuplot/demo/start.par
U gnuplot/demo/stat.inc
U gnuplot/demo/steps.dat
U gnuplot/demo/steps.dem
U gnuplot/demo/stringvariables.dem
U gnuplot/demo/surface1.dem
U gnuplot/demo/surface2.dem
U gnuplot/demo/table.dat
U gnuplot/demo/textcolor.dem
U gnuplot/demo/textrotate.dem
U gnuplot/demo/timedat.dat
U gnuplot/demo/timedat.dem
U gnuplot/demo/triangle.dat
U gnuplot/demo/using.bin
U gnuplot/demo/using.dat
U gnuplot/demo/using.dem
U gnuplot/demo/vector.dem
U gnuplot/demo/webify.pl
U gnuplot/demo/whale.dat
U gnuplot/demo/world.cor
U gnuplot/demo/world.dat
U gnuplot/demo/world.dem
U gnuplot/demo/world2.dem
cvs checkout: Updating gnuplot/docs
U gnuplot/docs/.cvsignore
U gnuplot/docs/Makefile.in
U gnuplot/docs/README
U gnuplot/docs/checkdoc.c
U gnuplot/docs/doc2gih.c
U gnuplot/docs/doc2hlp.c
U gnuplot/docs/doc2ipf.c
U gnuplot/docs/doc2ms.c
U gnuplot/docs/doc2rnh.c
U gnuplot/docs/doc2rtf.c
U gnuplot/docs/doc2tex.c
U gnuplot/docs/doc2texi.el
U gnuplot/docs/doc2x.h
U gnuplot/docs/gnuplot.doc
U gnuplot/docs/gnuplot.texi
U gnuplot/docs/gpcard.tex
U gnuplot/docs/makefile.ami
U gnuplot/docs/makefile.dst
U gnuplot/docs/termdoc.c
U gnuplot/docs/titlepag.ms
U gnuplot/docs/titlepag.tex
U gnuplot/docs/toc_entr.sty
U gnuplot/docs/xref.c
U gnuplot/docs/xref.h
cvs checkout: Updating gnuplot/docs/latextut
cvs checkout: Updating gnuplot/docs/old
U gnuplot/docs/old/ChangeLog.old
U gnuplot/docs/old/History.old
U gnuplot/docs/old/README.3d
U gnuplot/docs/old/README.3p1
U gnuplot/docs/old/README.3p2
U gnuplot/docs/old/README.3p3
U gnuplot/docs/old/README.3p4
U gnuplot/docs/old/README.3p5
U gnuplot/docs/old/README.ami
U gnuplot/docs/old/README.emx
U gnuplot/docs/old/README.fit
U gnuplot/docs/old/README.gnu
U gnuplot/docs/old/README.iso
U gnuplot/docs/old/README.mf
U gnuplot/docs/old/README.nex
U gnuplot/docs/old/README.pic
U gnuplot/docs/old/README.pro
U gnuplot/docs/old/README.win
U gnuplot/docs/old/README.xli
U gnuplot/docs/old/makefile.r
cvs checkout: Updating gnuplot/docs/psdoc
U gnuplot/docs/psdoc/.cvsignore
U gnuplot/docs/psdoc/Makefile
U gnuplot/docs/psdoc/README
U gnuplot/docs/psdoc/ps_file.doc
U gnuplot/docs/psdoc/ps_fontfile_doc.tex
U gnuplot/docs/psdoc/ps_guide.ps
U gnuplot/docs/psdoc/ps_symbols.gpi
cvs checkout: Updating gnuplot/lisp
U gnuplot/lisp/.cvsignore
U gnuplot/lisp/COPYING
U gnuplot/lisp/ChangeLog
U gnuplot/lisp/INSTALL
U gnuplot/lisp/Makefile.am
U gnuplot/lisp/README
U gnuplot/lisp/README.1st
U gnuplot/lisp/configure.in
U gnuplot/lisp/dot.el
U gnuplot/lisp/dotemacs
U gnuplot/lisp/gnuplot-gui.el
U gnuplot/lisp/gnuplot.el
U gnuplot/lisp/gnuplot.el.old
U gnuplot/lisp/gpelcard.tex
U gnuplot/lisp/info-look.20.2.el
U gnuplot/lisp/info-look.20.3.el
cvs checkout: Updating gnuplot/lisp/old
cvs checkout: Updating gnuplot/m4
U gnuplot/m4/.cvsignore
U gnuplot/m4/Makefile.am.in
U gnuplot/m4/README
U gnuplot/m4/apple.m4
U gnuplot/m4/beos.m4
U gnuplot/m4/msdos.m4
U gnuplot/m4/next.m4
cvs checkout: Updating gnuplot/man
U gnuplot/man/.cvsignore
U gnuplot/man/Makefile.am
U gnuplot/man/gnuplot.1
U gnuplot/man/lasergnu.1
cvs checkout: Updating gnuplot/os2
cvs checkout: Updating gnuplot/pm3d
U gnuplot/pm3d/README
cvs checkout: Updating gnuplot/pm3d/contrib
U gnuplot/pm3d/contrib/README
U gnuplot/pm3d/contrib/colorpts-demo.gp
U gnuplot/pm3d/contrib/colorpts.awk
U gnuplot/pm3d/contrib/pm3dCompress.awk
U gnuplot/pm3d/contrib/pm3dConvertToImage.awk
U gnuplot/pm3d/contrib/pts.dat
cvs checkout: Updating gnuplot/pm3d/demo
cvs checkout: Updating gnuplot/pm3d/old-docs
cvs checkout: Updating gnuplot/share
cvs checkout: Updating gnuplot/share/LaTeX
U gnuplot/share/LaTeX/Makefile
U gnuplot/share/LaTeX/README
U gnuplot/share/LaTeX/gnuplot.cfg
cvs checkout: Updating gnuplot/src
U gnuplot/src/.cvsignore
U gnuplot/src/GNUmakefile
U gnuplot/src/Makefile.am
U gnuplot/src/Makefile.maint
U gnuplot/src/README
U gnuplot/src/alloc.c
U gnuplot/src/alloc.h
U gnuplot/src/amiga.c
U gnuplot/src/ansi2knr.1
U gnuplot/src/ansi2knr.c
U gnuplot/src/ansichek.h
U gnuplot/src/axis.c
U gnuplot/src/axis.h
U gnuplot/src/bf_test.c
U gnuplot/src/bin_hook.c
U gnuplot/src/binary.c
U gnuplot/src/binary.h
U gnuplot/src/bitmap.c
U gnuplot/src/bitmap.h
U gnuplot/src/breaders.c
U gnuplot/src/breaders.h
U gnuplot/src/color.c
U gnuplot/src/color.h
U gnuplot/src/command.c
U gnuplot/src/command.h
U gnuplot/src/contour.c
U gnuplot/src/contour.h
U gnuplot/src/corgraph.asm
U gnuplot/src/corplot.c
U gnuplot/src/datafile.c
U gnuplot/src/datafile.h
U gnuplot/src/dynarray.c
U gnuplot/src/dynarray.h
U gnuplot/src/eval.c
U gnuplot/src/eval.h
U gnuplot/src/fit.c
U gnuplot/src/fit.h
U gnuplot/src/gadgets.c
U gnuplot/src/gadgets.h
U gnuplot/src/genopt.com
U gnuplot/src/getcolor.c
U gnuplot/src/getcolor.h
U gnuplot/src/gnuplot.def
U gnuplot/src/gnuplot.opt
U gnuplot/src/gnuplot.prj
U gnuplot/src/gp_hist.h
U gnuplot/src/gp_time.h
U gnuplot/src/gp_types.h
U gnuplot/src/gpexecute.c
U gnuplot/src/gpexecute.h
U gnuplot/src/gplt_x11.c
U gnuplot/src/gplt_x11.h
U gnuplot/src/graph3d.c
U gnuplot/src/graph3d.h
U gnuplot/src/graphics.c
U gnuplot/src/graphics.h
U gnuplot/src/header.mac
U gnuplot/src/help.c
U gnuplot/src/help.h
U gnuplot/src/hidden3d.c
U gnuplot/src/hidden3d.h
U gnuplot/src/history.c
U gnuplot/src/hrcgraph.asm
U gnuplot/src/intergra.x11
U gnuplot/src/internal.c
U gnuplot/src/internal.h
U gnuplot/src/interpol.c
U gnuplot/src/interpol.h
U gnuplot/src/lasergnu
U gnuplot/src/lineproc.mac
U gnuplot/src/linkopt.vms
U gnuplot/src/linkopt.ztc
U gnuplot/src/makefile.all
U gnuplot/src/matrix.c
U gnuplot/src/matrix.h
U gnuplot/src/misc.c
U gnuplot/src/misc.h
U gnuplot/src/mouse.c
U gnuplot/src/mouse.h
U gnuplot/src/mousecmn.h
U gnuplot/src/national.h
U gnuplot/src/os9.c
U gnuplot/src/parse.c
U gnuplot/src/parse.h
U gnuplot/src/pcgraph.asm
U gnuplot/src/plot.c
U gnuplot/src/plot.h
U gnuplot/src/plot2d.c
U gnuplot/src/plot2d.h
U gnuplot/src/plot3d.c
U gnuplot/src/plot3d.h
U gnuplot/src/pm3d.c
U gnuplot/src/pm3d.h
U gnuplot/src/readline.c
U gnuplot/src/readline.h
U gnuplot/src/rgipgnu
U gnuplot/src/save.c
U gnuplot/src/save.h
U gnuplot/src/scanner.c
U gnuplot/src/scanner.h
U gnuplot/src/set.c
U gnuplot/src/setshow.h
U gnuplot/src/show.c
U gnuplot/src/specfun.c
U gnuplot/src/specfun.h
U gnuplot/src/standard.c
U gnuplot/src/standard.h
U gnuplot/src/stdfn.c
U gnuplot/src/stdfn.h
U gnuplot/src/strftime.c
U gnuplot/src/syscfg.h
U gnuplot/src/tables.c
U gnuplot/src/tables.h
U gnuplot/src/template.h
U gnuplot/src/term.c
U gnuplot/src/term.h
U gnuplot/src/term_api.h
U gnuplot/src/time.c
U gnuplot/src/unset.c
U gnuplot/src/util.c
U gnuplot/src/util.h
U gnuplot/src/util3d.c
U gnuplot/src/util3d.h
U gnuplot/src/variable.c
U gnuplot/src/variable.h
U gnuplot/src/version.c
U gnuplot/src/version.h
U gnuplot/src/vms.c
U gnuplot/src/x11.opt
cvs checkout: Updating gnuplot/src/NeXT
U gnuplot/src/NeXT/Controller.h
U gnuplot/src/NeXT/Controller.m
U gnuplot/src/NeXT/GnuTerm.iconheader
U gnuplot/src/NeXT/GnuTerm.tiff
U gnuplot/src/NeXT/GnuTerm_main.m
U gnuplot/src/NeXT/GnuView.h
U gnuplot/src/NeXT/GnuView.m
U gnuplot/src/NeXT/Makefile
U gnuplot/src/NeXT/Makefile.postamble
U gnuplot/src/NeXT/Makefile.preamble
U gnuplot/src/NeXT/PB.gdbinit
U gnuplot/src/NeXT/PB.project
U gnuplot/src/NeXT/README.rtf
U gnuplot/src/NeXT/bigger.tiff
U gnuplot/src/NeXT/gnuviewController.h
U gnuplot/src/NeXT/gnuviewController.m
U gnuplot/src/NeXT/smaller.tiff
cvs checkout: Updating gnuplot/src/NeXT/English.lproj
cvs checkout: Updating gnuplot/src/NeXT/English.lproj/GnuTerm.nib
U gnuplot/src/NeXT/English.lproj/GnuTerm.nib/data.classes
U gnuplot/src/NeXT/English.lproj/GnuTerm.nib/data.nib
cvs checkout: Updating gnuplot/src/NeXT/English.lproj/gnuview.nib
U gnuplot/src/NeXT/English.lproj/gnuview.nib/bigger.tiff
U gnuplot/src/NeXT/English.lproj/gnuview.nib/data.classes
U gnuplot/src/NeXT/English.lproj/gnuview.nib/data.nib
U gnuplot/src/NeXT/English.lproj/gnuview.nib/smaller.tiff
cvs checkout: Updating gnuplot/src/OpenStep
U gnuplot/src/OpenStep/Controller.h
U gnuplot/src/OpenStep/Controller.m
U gnuplot/src/OpenStep/GnuTerm.iconheader
U gnuplot/src/OpenStep/GnuTerm.tiff
U gnuplot/src/OpenStep/GnuTerm_main.m
U gnuplot/src/OpenStep/GnuView.h
U gnuplot/src/OpenStep/GnuView.m
U gnuplot/src/OpenStep/GnuViewController.h
U gnuplot/src/OpenStep/GnuViewController.m
U gnuplot/src/OpenStep/Makefile
U gnuplot/src/OpenStep/Makefile.postamble
U gnuplot/src/OpenStep/Makefile.preamble
U gnuplot/src/OpenStep/PB.project
U gnuplot/src/OpenStep/TODO
cvs checkout: Updating gnuplot/src/OpenStep/English.lproj
cvs checkout: Updating gnuplot/src/OpenStep/English.lproj/GnuTerm.nib
U gnuplot/src/OpenStep/English.lproj/GnuTerm.nib/classes.nib
U gnuplot/src/OpenStep/English.lproj/GnuTerm.nib/objects.nib
cvs checkout: Updating gnuplot/src/OpenStep/English.lproj/gnuview.nib
U gnuplot/src/OpenStep/English.lproj/gnuview.nib/data.classes
U gnuplot/src/OpenStep/English.lproj/gnuview.nib/objects.nib
cvs checkout: Updating gnuplot/src/OpenStep/PBUserInfo
U gnuplot/src/OpenStep/PBUserInfo/PBUserInfo_leigh.plist
cvs checkout: Updating gnuplot/src/OpenStep/derived_src
cvs checkout: Updating gnuplot/src/beos
U gnuplot/src/beos/GPApp.cpp
U gnuplot/src/beos/GPApp.h
U gnuplot/src/beos/GPBitmap.cpp
U gnuplot/src/beos/GPBitmap.h
U gnuplot/src/beos/GPView.cpp
U gnuplot/src/beos/GPView.h
U gnuplot/src/beos/GPWindow.cpp
U gnuplot/src/beos/GPWindow.h
U gnuplot/src/beos/Makefile
U gnuplot/src/beos/XStringList.cpp
U gnuplot/src/beos/XStringList.h
U gnuplot/src/beos/constants.h
cvs checkout: Updating gnuplot/src/os2
U gnuplot/src/os2/.cvsignore
U gnuplot/src/os2/dialogs.c
U gnuplot/src/os2/dialogs.h
U gnuplot/src/os2/gclient.c
U gnuplot/src/os2/gnuplot.ico
U gnuplot/src/os2/gnupmdrv.c
U gnuplot/src/os2/gnupmdrv.def
U gnuplot/src/os2/gnupmdrv.h
U gnuplot/src/os2/gnupmdrv.ipf
U gnuplot/src/os2/gnupmdrv.rc
U gnuplot/src/os2/print.c
U gnuplot/src/os2/ptrcross.ptr
U gnuplot/src/os2/rotating.ptr
U gnuplot/src/os2/scaling.ptr
cvs checkout: Updating gnuplot/src/win
U gnuplot/src/win/geticon.c
U gnuplot/src/win/pgnuplot.c
U gnuplot/src/win/rotating.cur
U gnuplot/src/win/scaling.cur
U gnuplot/src/win/wcommon.h
U gnuplot/src/win/wgnupl32.def
U gnuplot/src/win/wgnuplib.c
U gnuplot/src/win/wgnuplib.def
U gnuplot/src/win/wgnuplib.h
U gnuplot/src/win/wgnuplib.rc
U gnuplot/src/win/wgnuplot.def
U gnuplot/src/win/wgnuplot.hpj
U gnuplot/src/win/wgnuplot.mnu
U gnuplot/src/win/wgnuplot.rc
U gnuplot/src/win/wgraph.c
U gnuplot/src/win/winmain.c
U gnuplot/src/win/winmain.h
U gnuplot/src/win/wmenu.c
U gnuplot/src/win/wpause.c
U gnuplot/src/win/wprinter.c
U gnuplot/src/win/wresourc.h
U gnuplot/src/win/wtext.c
U gnuplot/src/win/wtext.h
cvs checkout: Updating gnuplot/term
U gnuplot/term/.cvsignore
U gnuplot/term/Makefile.am.in
U gnuplot/term/README
U gnuplot/term/aed.trm
U gnuplot/term/ai.trm
U gnuplot/term/amiga.trm
U gnuplot/term/apollo.trm
U gnuplot/term/aquaterm.trm
U gnuplot/term/atariaes.trm
U gnuplot/term/atarivdi.trm
U gnuplot/term/be.trm
U gnuplot/term/cgi.trm
U gnuplot/term/cgm.trm
U gnuplot/term/compact.c
U gnuplot/term/corel.trm
U gnuplot/term/debug.trm
U gnuplot/term/djsvga.trm
U gnuplot/term/driver.h
U gnuplot/term/dumb.trm
U gnuplot/term/dxf.trm
U gnuplot/term/dxy.trm
U gnuplot/term/eepic.trm
U gnuplot/term/emf.trm
U gnuplot/term/emxvga.trm
U gnuplot/term/epson.trm
U gnuplot/term/estimate.trm
U gnuplot/term/excl.trm
U gnuplot/term/fg.trm
U gnuplot/term/fig.trm
U gnuplot/term/gd.trm
U gnuplot/term/ggi.trm
U gnuplot/term/gnugraph.trm
U gnuplot/term/gpic.trm
U gnuplot/term/gpr.trm
U gnuplot/term/grass.trm
U gnuplot/term/hp26.trm
U gnuplot/term/hp2648.trm
U gnuplot/term/hp500c.trm
U gnuplot/term/hpgl.trm
U gnuplot/term/hpljii.trm
U gnuplot/term/hppj.trm
U gnuplot/term/imagen.trm
U gnuplot/term/impcodes.h
U gnuplot/term/iris4d.trm
U gnuplot/term/kyo.trm
U gnuplot/term/latex.trm
U gnuplot/term/linux.trm
U gnuplot/term/mac.trm
U gnuplot/term/metafont.trm
U gnuplot/term/metapost.trm
U gnuplot/term/mgr.trm
U gnuplot/term/mif.trm
U gnuplot/term/multitos.trm
U gnuplot/term/next.trm
U gnuplot/term/object.h
U gnuplot/term/openstep.trm
U gnuplot/term/pbm.trm
U gnuplot/term/pc.trm
U gnuplot/term/pdf.trm
U gnuplot/term/pm.trm
U gnuplot/term/post.h
U gnuplot/term/post.trm
U gnuplot/term/pslatex.trm
U gnuplot/term/pstricks.trm
U gnuplot/term/qms.trm
U gnuplot/term/regis.trm
U gnuplot/term/rgip.trm
U gnuplot/term/sun.trm
U gnuplot/term/svg.trm
U gnuplot/term/t410x.trm
U gnuplot/term/table.trm
U gnuplot/term/tek.trm
U gnuplot/term/texdraw.trm
U gnuplot/term/tgif.trm
U gnuplot/term/tkcanvas.trm
U gnuplot/term/tpic.trm
U gnuplot/term/unixpc.trm
U gnuplot/term/unixplot.trm
U gnuplot/term/v384.trm
U gnuplot/term/vgagl.trm
U gnuplot/term/vws.trm
U gnuplot/term/win.trm
U gnuplot/term/x11.trm
U gnuplot/term/xlib.trm
cvs checkout: Updating gnuplot/tutorial
U gnuplot/tutorial/.cvsignore
U gnuplot/tutorial/Makefile.am.in
U gnuplot/tutorial/eg1.plt
U gnuplot/tutorial/eg2.plt
U gnuplot/tutorial/eg3.dat
U gnuplot/tutorial/eg3.plt
U gnuplot/tutorial/eg4.plt
U gnuplot/tutorial/eg5.plt
U gnuplot/tutorial/eg6.plt
U gnuplot/tutorial/header.tex
U gnuplot/tutorial/linepoin.plt
U gnuplot/tutorial/makefile.dst
U gnuplot/tutorial/tutorial.tex
cvs checkout: Updating gnuplot/win
[root@Dalek gnuplot]# cd gnuplot/
[root@Dalek gnuplot]# ./prepare
rm -f Makefile.am Makefile.amt
sed -n '1,/^##m4-files-begin/p' Makefile.am.in > Makefile.amt
echo EXTRA_DIST = README Makefile.am.in buildvms.com config.* \
  djconfig.sh make_vms.com term_pc.h makefile.* | fmt | \
  (tr '\012' @; echo) |sed 's/@$/%/;s/@/ \\@/g' |tr @% '\012 ' >> Makefile.amt
sed -n '/^##m4-files-end/,$p' Makefile.am.in >> Makefile.amt
chmod a-w Makefile.amt
mv Makefile.amt Makefile.am
rm -f Makefile.am Makefile.amt
sed -n '1,/^##m4-files-begin/p' Makefile.am.in > Makefile.amt
echo EXTRA_DIST = Makefile.am.in *.bin *.cor *.dat *.dem *.edf \
  *.fnc *.inc nearmap.csv labelplot.pdb *.rgb sound.par sound2.par \
  start.par webify.pl *.rot | fmt | \
  (tr '\012' @; echo) | sed 's/@$/%/;s/@/ \\@/g' | tr @% '\012 ' \
  >> Makefile.amt
sed -n '/^##m4-files-end/,$p' Makefile.am.in >> Makefile.amt
chmod a-w Makefile.amt
mv Makefile.amt Makefile.am
rm -f Makefile.am Makefile.amt
sed -n '1,/^##m4-files-begin/p' Makefile.am.in > Makefile.amt
echo EXTRA_DIST = README Makefile.am.in *.m4 | fmt | \
  (tr '\012' @; echo ) \
  |sed 's/@$/%/;s/@/ \\@/g' |tr @% '\012 ' \
  >> Makefile.amt
sed -n '/^##m4-files-end/,$p' Makefile.am.in >> Makefile.amt
chmod a-w Makefile.amt
mv Makefile.amt Makefile.am
rm -f Makefile.am Makefile.amt
sed -n '1,/^##trm-files-begin/p' Makefile.am.in > Makefile.amt
echo CORETERM = *.trm | fmt | (tr '\012' @; echo) \
  |sed 's/@$/%/;s/@/ \\@/g' | tr @% '\012 ' \
  >> Makefile.amt
sed -n '/^##trm-files-end/,$p' Makefile.am.in >> Makefile.amt
chmod a-w Makefile.amt
mv Makefile.amt Makefile.am
rm -f Makefile.am Makefile.amt
sed -n '1,/^##plt-files-begin/p' Makefile.am.in > Makefile.amt
echo PLT_FILES = *.plt | fmt | (tr '\012' @; echo ) \
  |sed 's/@$/%/;s/@/ \\@/g;' | tr @% '\012 ' >> Makefile.amt
sed -n '/^##plt-files-end/,$p' Makefile.am.in >> Makefile.amt
chmod a-w Makefile.amt
mv Makefile.amt Makefile.am
automake: configure.in: required file `../config.guess' not found
automake: configure.in: required file `../config.sub' not found

Some part of the preparation process failed.
Please refer to INSTALL for details.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCM7XxkvgQCyW4kdARArO+AJ4mltKqhYgpfpkrAdQqcoCZ3zRR1wCeIIb+
nlKjK2mmMoNPrtxysn2lhc4=
=573I
-----END PGP SIGNATURE-----

Re: pslatex code contaminating the gnuplot core

[Harald H. <h.h...@tu...>]

On Thu, 10 Mar 2005, Hans-Bernhard Broeker wrote:

> Ethan Merritt wrote:
>
> > How about a terminal entry point (*term->layer)((int) layernumber)
> > that the core code would call at each stage of the plot process, once
> > per layer?
> [...]
> > enum layer { LAYER_PLOT_BACKGROUND, LAYER_AXES, LAYER_BACK_LABELS,
> > LAYER_PLOT_LINES, LAYER_FRONT_RECTANGLES, LAYER_FRONT_LABELS, ... }
>
> This idea certainly has a nicer ring to it than the current situation.
[...]
> I don't thus think that *naming* the layers would be a good idea at all.
> Let them have numbers, and export those to the user interface in some
> way the users can (hopefully) understand.

Would you prefer something like this? Or how do you think it should be
implemented?

int layer;
#define LAYER_PLOT_BACKGROUND -3
#define LAYER_AXES -2
#define LAYER_BACK_LABELS -1
#define LAYER_PLOT_LINES 0
#define LAYER_FRONT_RECTANGLES 1
#define LAYER_FRONT_LABELS 2


-- 
Harald Harders
h.h...@tu...
http://www.harald-harders.de

Re: pslatex code contaminating the gnuplot core

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

Ethan Merritt wrote:

> How about a terminal entry point (*term->layer)((int) layernumber) 
> that the core code would call at each stage of the plot process, once
> per layer?
[...]
> enum layer { LAYER_PLOT_BACKGROUND, LAYER_AXES, LAYER_BACK_LABELS,
> LAYER_PLOT_LINES, LAYER_FRONT_RECTANGLES, LAYER_FRONT_LABELS, ... }

This idea certainly has a nicer ring to it than the current situation.

What I'm a little bit worried about is, as always, the conceptual
clarity of our terminal layer API.  So far, the terminal API is,
essentially, just a rather generic vector drawing API --- all the way to
the old "gnuplot library" which exported this API for generic usage.

A new API entry like the above would, effectively, specialize the
interface to gnuplot as the client, and kill all remaining hopes of one
day splitting up the program into well-separated layers of functionality.

I don't thus think that *naming* the layers would be a good idea at all.
Let them have numbers, and export those to the user interface in some
way the users can (hopefully) understand.

Re: Returning system command output to a string variable

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

On Monday 07 March 2005 10:42 pm, Juergen Wieferink wrote:
> I meant an ordinary function which takes a string (the system
> command) and returns another one---the output of the system command.
> Using the backtics wouldn't work for RFE#1108413.

Ah, sorry. 
I assumed you were continuing the previous discussion, which 
involved also the substitution of macro values into the command
passed to the system. For example
	result = system("grep @key @file") 
The problem there is that macro substitution doesn't happen
inside quoted strings.

If you don't care about macro substitution, then I think it
would be possible. I was earlier very worried about memory leaks
from such an operation, but I think I now understand how to
avoid leaking memory.

-- 
Ethan A Merritt
Biomolecular Structure Center
University of Washington 98195-7742

Re: Returning system command output to a string variable

[Juergen W. <wie...@fr...>]

On Monday 07 March 2005 23:45, Ethan Merritt wrote:
> Juergen Wieferink wrote (apropos RFE 1108413):
> > The proper syntax would be a string function
> > "command('blabla1')" returning the standard output as a
> > string (as suggested by Petr in October 2004). I still think
> > this would be a useful feature.
[...]
> The syntax command(`blabla`) is difficult to implement in gnuplot's
> parser, because it will try evaluate the contents of the parantheses
> before recognizing the particular function being called.  This just
> pushes back the original problem by one layer of function call.
> There may be a way around this, but so far I haven't been able to see it.
>
> What I *can* see how to do easily is to distinguish between
> single back-quotes and double back-quotes.  The system command would be
> executed in either case.  The single back-quote case would then

I didn't propose backtics.  And the double quotes were not meant
literally.  Sorry for such ambiguous suggestions.

I meant an ordinary function which takes a string (the system
command) and returns another one---the output of the system command.
Using the backtics wouldn't work for RFE#1108413.


Juergen

Re: Returning system command output to a string variable

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

On Monday 07 March 2005 02:45 pm, Ethan Merritt wrote:
> Juergen Wieferink wrote (apropos RFE 1108413):
> 
> > The proper syntax would be a string function
> > "command('blabla1')" returning the standard output as a
> > string (as suggested by Petr in October 2004). I still think
> > this would be a useful feature.
> 
> 
> What I *can* see how to do easily is to distinguish between
> single back-quotes and double back-quotes.

And then there is the very unix-style solution:
Create an external script named "quote"
#!/bin/csh
echo '"'
$*
echo '"'


and then issue the command as
gnuplot>  numvar = `mycommand $1 $2 $3`
gnuplot>  stringvar = `quote mycommand $1 $2 $3`



-- 
Ethan A Merritt       merritt@u.washington.edu
Biomolecular Structure Center
Mailstop 357742
University of Washington, Seattle, WA 98195

Returning system command output to a string variable

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

Juergen Wieferink wrote (apropos RFE 1108413):

> The proper syntax would be a string function
> "command('blabla1')" returning the standard output as a
> string (as suggested by Petr in October 2004). I still think
> this would be a useful feature.

The suggestion from the previous discussion was:

> > On Friday 15 October 2004 12:01 am, Petr Mikulik wrote:
> 
> >> I would propose to ignore macro expansion in `blabla1` and !blabla2
> >> but allow them in system('blabla2') and in value = execute('blabla1');
> 
> >> Where the execute() is a new command. The user could use what he
> >> wants.

The syntax command(`blabla`) is difficult to implement in gnuplot's
parser, because it will try evaluate the contents of the parantheses
before recognizing the particular function being called.  This just
pushes back the original problem by one layer of function call.
There may be a way around this, but so far I haven't been able to see it.

What I *can* see how to do easily is to distinguish between
single back-quotes and double back-quotes.  The system command would be
executed in either case.  The single back-quote case would then
return the output directly into the gnuplot input line, just as it does
now.  The double back-quote case would also return the output into
the gnuplot input line, but it would wrap it in double quotes.
This makes it suitable for string variable assignment.

This is implemented by the attached patch.

gnuplot> numvar = `uname -mo`
         undefined variable: i686

gnuplot> stringvar = ``uname -mo``
gnuplot> show var

        Variables:
        pi = 3.14159265358979
        stringvar = i686 GNU/Linux


What do you think.  Can we live with this syntax?


-- 
Ethan A Merritt       merritt@u.washington.edu
Biomolecular Structure Center
Mailstop 357742
University of Washington, Seattle, WA 98195

Re: pasting to terminal

[Per P. <per...@ma...>]

On Mar 4, 2005, at 21:27, Kristopher Wieland wrote:

> For some reason, when I paste large amounts of text to gnuplot, it 
> truncates it.  Is this a know bug?  Is this a problem with terminal 
> for mac, and not gnuplot?

FWIW, I can't reproduce the problem on Mac OS X 10.3.8 using gnuplot 
4.1 compiled from CVS a few days ago. I don't think this is a problem 
with Terminal.app. Maybe someone else can comment on whether gnuplot 
has had any changes between 4.0 and current that may affect this.

/Per

Re: pslatex code contaminating the gnuplot core

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

On Sunday 06 March 2005 03:32 am, Harald Harders wrote:
> > Ethan Merritt wrote:
> > >
> > > In particular I object to the following contamination of core
> > > routines with terminal-specific code.  If we need a new terminal
> > > entry for this, then so be it.
> With "terminal entry", do you mean a
> new member in the TERMENTRY struct? It could be something like
>     void (*place_plot) __PROTO((void));
> that does nothing by default and writes the above line to the output
> file if defined:

Not exactly. If it is necessary to do this at all, let's try to
make it as general as possible.  Your epslatex driver wants to be
notified of the appropriate time to place the \includegraphics
command, but that is very terminal-specific and the core code 
should not be expected to make this decision.  Some other driver
might need to act at a different time, or perform some other
action instead.

How about a terminal entry point (*term->layer)((int) layernumber)
that the core code would call at each stage of the plot process,
once per layer?   Right now we only use 2 layers, or 3 if you consider 
this to be a new one, but I could imagine expanding this to a more
fine-grained description in the future.

Right now we have:
term_api.h:    int layer;                  /* 0 = back, 1 = front */

This could be replaced by a set of enum values so that future
expansion is possible:
    enum layer { LAYER_PLOT_BACKGROUND,
                 LAYER_AXES, LAYER_BACK_LABELS, LAYER_PLOT_LINES,
                 LAYER_FRONT_RECTANGLES, LAYER_FRONT_LABELS, ... }

We don't need all of these to begin with, but you see the idea.			 

The epslatex driver would ignore all (*term->layer)(layernumber) calls 
except for the one with layernumber = LAYER_PLOT_LINES

This approach could actually generalize some of the existing 
special-purpose driver entries.  For example
(*term->suspend)() could become (*term->layer)(LAYER_END_MULTIPLOT)
(*term->resume)() could become (*term->layer)(LAYER_BEGIN_MULTIPLOT)
and the processing associated with the flag 
#define TERM_INIT_ON_REPLOT   8  /* call term->init() on replot     */
could instead be triggered by (*term->layer)(LAYER_BEGIN_REPLOT)

I'm thinking out loud here, so I may be overlooking serious
drawbacks to this approach.


-- 
Ethan A Merritt
Biomolecular Structure Center
University of Washington 98195-7742

Re: pslatex code contaminating the gnuplot core

[Harald H. <h.h...@tu...>]

On Tue, 1 Mar 2005, Daniel J Sebald wrote:

> Ethan Merritt wrote:
> > By the way, in trying to build gnuplot without the postscript
> > terminal driver I discovered that the recent commingling of
> > postscript/pslatex/epslatex has made this impossible.
> >
> > In particular I object to the following contamination of core
> > routines with terminal-specific code.  If we need a new terminal
> > entry for this, then so be it. But having the core code writing
> > this garbage is just really really ugly.
>
> Oo, yes.  Don't start this sort of thing.  There must be a good solution to this inside the terminal
> driver, e.g., static variables for remembering when to put this string in the LaTeX file.  Harald?
>
> > -    /* Print \includegraphics here when using back option for text */
> > -    if (term->name=="epslatex" && gpoutfile)
> > -       fprintf(gpoutfile, "    \\put(0,0){\\includegraphics{%s}}%%\n",
> > -               pslatex_auxname);

This was the only possibility to enable the user to use the keywords
'front' and 'back' for 'labels'. With "terminal entry", do you mean a new
member in the TERMENTRY struct? It could be something like
    void (*place_plot) __PROTO((void));
that does nothing by default and writes the above line to the output file
if defined:

graphics.c, graph3d.c, and term.c:

    if (term->place_plot)
        (*term->place_plot)();

post.trm:

TERM_PUBLIC void
PS_place_plot()
{
    if (term->name=="epslatex" && gpoutfile)
        fprintf(gpoutfile, "    \\put(0,0){\\includegraphics{%s}}%%\n",
                pslatex_auxname);
}

Shall I write a patch and upload it to sourceforge?

-- 
Harald Harders
h.h...@tu...
http://www.harald-harders.de

Re: Missing .../share directory?

[Harald H. <h.h...@tu...>]

On Tue, 1 Mar 2005, Ethan Merritt wrote:

> from the ChangeLog entry for
>
> 2005-02-09  Harald Harders  <h.h...@tu...>
>
>         * share/: New directory.
>
>         * share/LaTeX/Makefile share/LaTeX/README share/LaTeX/gnuplot.cfg:
>         New directory LaTeX/. New files for supporting the epslatex terminal.
>
> I can't find this directory.

In my cvs tree, this directory exists. Has somebody fixed it?

Harald

-- 
Harald Harders
h.h...@tu...
http://www.harald-harders.de

plot ... using (timecolumn(<column_no>))

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

The timecolumn(<column_no>) function seems to be totally undocumented.

Would anyone care to contribute a short description
or example of use?


-- 
Ethan A Merritt       merritt@u.washington.edu
Biomolecular Structure Center
Mailstop 357742
University of Washington, Seattle, WA 98195

pasting to terminal

[Kristopher W. <kwi...@wu...>]

For some reason, when I paste large amounts of text to gnuplot, it  
truncates it.  Is this a know bug?  Is this a problem with terminal for  
mac, and not gnuplot?

Thanks
Kristopher

Here is the text portion that shows what I mean.  After the cd  
"GaAs_In_15K_shunt" command, it should look similar to the prior two  
sets of commands.

________________________________________________________________________ 
___
[kwieland@SolinG5s-Computer ~]>> gnuplot

         G N U P L O T
         Version 4.0 patchlevel 0
         last modified Thu Apr 15 14:44:22 CEST 2004
         System: Darwin 7.8.0

         Copyright (C) 1986 - 1993, 1998, 2004
         Thomas Williams, Colin Kelley and many others

         This is gnuplot version 4.0.  Please refer to the documentation
         for command syntax changes.  The old syntax will be accepted
         throughout the 4.0 series, but all save files use the new  
syntax.

         Type `help` to access the on-line reference manual.
         The gnuplot FAQ is available from
                 http://www.gnuplot.info/faq/

         Send comments and requests for help to
                 <gnu...@li...>
         Send bugs, suggestions and mods to
                 <gnu...@li...>


Terminal type set to 'unknown'
gnuplot> reset
gnuplot> set xlabel "X Position (um)"
gnuplot> set ylabel "Z Position (um)"
gnuplot> cd "/Users/kwieland/Documents/March/theory/GaAs_WashU/"
gnuplot> set terminal postscript eps enhanced color landscape
Terminal type set to 'postscript'
set size ratio -2

set output '../Bare GaAs 15K vector.ps'
set title "Bare GaAs, T=15K" font "Helvitica,18"
cd "GaAs_In_15K_noshunt"
set xrange [-500:10500]
set yrange [-250:2250]
plot "j_B0.out" using 1:2:($3/.35):($4/.35) w vec lw 1, "bseg.out" w l  
lw 4,"inport.out" w l lw 4, "outport.out" w l lw 4, "V1port.out" w l lw  
4, "V2port.out" w l lw 4
cd ".."

set output '../Bare GaAs 300K vector.ps'
set title "Bare GaAs, T=300K" font "Helvitica,18"
cd "GaAs_In_300K_noshunt"
set xrange [-500:10500]
set yrange [-250:2250]
plot "j_B0.out" using 1:2:($3/.35):($4/.35) w vec lw 1, "bseg.out" w l  
lw 4,"inport.out" w l lw 4, "outport.out" w l lw 4, "V1port.out" w l lw  
4, "V2port.out" w l lw 4
cd ".."

set output '../Hybrid GaAs 15K vector.ps'
set title "Hybrid GaAs, T=15K" font "Helvitica,18"
set xrange [-500:10500]
set yrange [-250:3250]
cd "GaAs_In_15K_shunt"
plot "j_B0.out" using 1:2:($3/.35):($4/.35) w vec lw 1, "bseg.out" w l  
lw 4,"inport.out" w l lw 4, "outport.out"Options are 'landscape  
enhanced color colortext \
    dashed dashlength 1.0 linewidth 1.0 defaultplex \
    palfuncparam 2000,0.003 \
    butt "Helvetica" 14'
gnuplot> set size ratio -2
gnuplot>
gnuplot> set output '../Bare GaAs 15K vector.ps'
gnuplot> set title "Bare GaAs, T=15K" font "Helvitica,18"
gnuplot> cd "GaAs_In_15K_noshunt"
gnuplot> set xrange [-500:10500]
gnuplot> set yrange [-250:2250]
gnuplot> plot "j_B0.out" using 1:2:($3/.35):($4/.35) w vec lw 1,  
"bseg.out" w l lw 4,"inport.out" w l lw 4, "outport.out" w l lw 4,  
"V1port.out" w l lw 4, "V2port.out" w l lw 4
gnuplot> cd ".."
gnuplot>
gnuplot> set output '../Bare GaAs 300K vector.ps'
gnuplot> set title "Bare GaAs, T=300K" font "Helvitica,18"
gnuplot> cd "GaAs_In_300K_noshunt"
gnuplot> set xrange [-500:10500]
gnuplot> set yrange [-250:2250]
gnuplot> plot "j_B0.out" using 1:2:($3/.35):($4/.35) w vec lw 1,  
"bseg.out" w l lw 4,"inport.out" w l lw 4, "outport.out" w l lw 4,  
"V1port.out" w l lw 4, "V2port.out" w l lw 4
gnuplot> cd ".."
gnuplot>
gnuplot> set output '../Hybrid GaAs 15K vector.ps'
gnuplot> set title "Hybrid GaAs, T=15K" font "Helvitica,18"
gnuplot> set xrange [-500:10500]
gnuplot> set yrange [-250:3250]
gnuplot> cd "GaAs_In_15K_shunt"
gnuplot> plot "j_B0.out" using 1:2:($3/.35):($4/.35) w vec lw 1,  
"bseg.out" w l lw 4,"inport.out" w l lw 4, "outport.out" w l lw 4,  
"V1port.out" w l lw 4, "V2port.out" w l lw 4
gnuplot> cd ".."
gnuplot>
gnuplot> set outptor.ps'
              ^
          valid set options:  [] = choose one, {} means optional

         'angles', 'arrow', 'autoscale', 'bars', 'border', 'boxwidth',
         'clabel', 'clip', 'cntrparam', 'colorbox', 'contour',  
'decimalsign',
         'dgrid3d', 'dummy', 'encoding', 'fit', 'format', 'grid',
         'hidden3d', 'historysize', 'isosamples', 'key', 'label',  
'locale',
         'logscale', '[blrt]margin', 'mapping', 'mouse', 'multiplot',
         'offsets', 'origin', 'output', 'palette', 'parametric', 'pm3d',
         'pointsize', 'polar', 'print', '[rtuv]range', 'samples', 'size',
         'style', 'surface', 'terminal', tics', 'ticscale', 'ticslevel',
         'timestamp', 'timefmt', 'title', 'view', '[xyz]{2}data',
         '[xyz]{2}label', '[xyz]{2}range', '{no}{m}[xyz]{2}tics',
         '[xyz]{2}[md]tics', '{[xyz]{2}}zeroaxis', 'zero'

gnuplot> set tititica,18"
              ^
          valid set options:  [] = choose one, {} means optional

         'angles', 'arrow', 'autoscale', 'bars', 'border', 'boxwidth',
         'clabel', 'clip', 'cntrparam', 'colorbox', 'contour',  
'decimalsign',
         'dgrid3d', 'dummy', 'encoding', 'fit', 'format', 'grid',
         'hidden3d', 'historysize', 'isosamples', 'key', 'label',  
'locale',
         'logscale', '[blrt]margin', 'mapping', 'mouse', 'multiplot',
         'offsets', 'origin', 'output', 'palette', 'parametric', 'pm3d',
         'pointsize', 'polar', 'print', '[rtuv]range', 'samples', 'size',
         'style', 'surface', 'terminal', tics', 'ticscale', 'ticslevel',
         'timestamp', 'timefmt', 'title', 'view', '[xyz]{2}data',
         '[xyz]{2}label', '[xyz]{2}range', '{no}{m}[xyz]{2}tics',
         '[xyz]{2}[md]tics', '{[xyz]{2}}zeroaxis', 'zero'

gnuplot> se0:3250]sing 1w l lw 4,"inport.lw 4, "V1port.out"
          ^
          invalid command

gnuplot> cd ".."
gnuplot>