From bug-request at octave dot org Thu Jan  5 07:55:24 2006
Subject: Re: gnuplot gset
From: "Sean O'Rourke" <sorourke at cs dot ucsd dot edu>
To: "John W. Eaton" <jwe at bevo dot che dot wisc dot edu>
Cc: Paul Kienzle <pkienzle at users dot sourceforge dot net>, bug@octave.org
Date: Thu, 5 Jan 2006 07:49:02 -0600

"John W. Eaton" <jwe at bevo dot che dot wisc dot edu> writes:

> On  4-Jan-2006, Sean O'Rourke wrote:
>
> | Paul Kienzle <pkienzle at users dot sourceforge dot net> writes:
> | 
> | > How about the following?
> | >
> | >    function gnuplot(varargin), __gnuplot_plot__(varargin{:}); endfunction
> | >    function gnuset(varargin), __gnuplot_set__(varargin{:}); endfunction
> | 
> | Does the old gplot do some special command-line parsing,
>
> Yes.

Thanks.  Can we keep it as a function that takes a single string
as argument and lexes that instead of implicitly quoting the
entire command line?  e.g.

    gnuset("term post eps font \"Palatino\" ... ");
    gnuplot("x as linesp, y as points pt 3");

It seems like it should be easy to shove the string through the
existing lexer, but I'm not at all familiar with that part of
Octave.

One way to get back the original functionality from this would be
to have a "mark_as_übercommand" that would pass the entire
unevaluated line to the command function (possibly after joining
continuation lines).  I don't really care if this feature is left
out, but at least having the single-string versions would be
worthwhile.

/s



-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------