****Check use of strdic() against etc$sttyco.x.

-   Doc says an indir file can contain:

	    inputspec	titlespec	linetype	markertype	or
	    inputspec	*		*		markertype	etc.

    In practice, each field must be enclosed in quotes.  (?? not so in tests...)

-   if user specifies "none" in main parameter space, and has nothing in title
    position in indirection file, then use real "none" for all.

-   bus error when "waveplot dev=stdgraph"; check out ability to edit a
    metacode file output by wave/longplot in cursor mode, then dump it on
    the Calcomp.

D   very long plots come out with y-axis label too far to left of axis

-   when one axis is squeezed down, and plotting with otheraxisautoscale=true,
    other range should be determined from limited range of 1st axis.

-   ability to rotate whole plot 90 degrees (task parameter).

-   ability to waveplot multiple images in one execution.  Will have to
    create separate non-script version for WAVEPLOT.

-   Look at adding some parameters to the indirection-file.  Also make sure
    it is easy to create an indirection-file by using tools (ls).

    Examples:
	-   marker size
	-   xt, yt	NO:  this is going too far; Caty says no problem.

-   marker type directly as task parameter, rather than only through file
    indirection

-   marker size "; also add as field in input indirection

-   WAVEPLOT cannot work with an indirection file that includes any fields
    other than the inputspec.  WAVEPLOT uses imgets to expand the contents
    of its own input specification -- thus it works fine for an "@file" that
    contains only one image name per line -- and then calls LONGPLOT once for
    each image.  It has to do it this way, because only WAVEPLOT is supposed
    to know anything about the KPNO-specific wavecal parameters (e.g. W0, WPC).
    The only solution would be to create a separate, local-to-KPNO version
    of waveplot that contains its own version of longplot that does the wavecal
    extraction itself -- i.e. don't drive it from a script.

-   look at legality & expectations for reading a longplot into cursor mode,
    editing, and writing out again, then plotting with CALCOMP.

-   order of generating plot commands:  try to minimize pen movement

NA  w/regard to splitting WAVEPLOT from LONGPLOT, consider separate scripts
    in IMRED.

-   individual-point marker size control -- argument for splitting list &
    image input versions

NA  use file indirection cap. directly from WAVEPLOT for real spectra as
    markers with synthetic spectra as lines.  (either add xt, yt as extra
    indirection parameters, or write image-specific version of longplot.

-   check out log/elog transforms!  and their interactions w/scaling,
    ticking.
