Re: VAriables on the command line.

[Harry Binswanger hb@xxxxxxxx]

The COCO would put out two commas. Doesn't tyf want only one? But anyway,
you seem to have left out a space before the "d" and have the slash going
the wrong way, then you need
<,p,v,<,v,a,$,f,i,>,>,
where the angle brackets are guillemets. so outside a kbd file it would
look like this:

BX tyf/nv ,d:\>.psQ2
I would experiment by doing it on the command line first--i.e., check out
what happens using the above syntax (w/o the BX and Q2 of course).
20=BX,t,y,f,/,n,v,COCO,d,:,/,'v,a,$,f,i,',.,p,s,Q2
Regarding keyboard assignments and VAriables, TYping to File and giving
the destination file a name by using a key assignment like this:

20=BX,t,y,f,/,n,v,COCO,d,:,/,'v,a,$,f,i,',.,p,s,Q2
results in the file creation d:/'va$fi'.ps. In other words, literal string
replacement for the filename rather than what I wanted, which was the
current XyWrite window's filename with .ps appended. The same result
obtains when I manually enter the TYpe to File command on the command
line. I suggest that I am either making a mistake with the keyboard
assignment or command line entry, or that the command line will not parse
the VAriable assignments, even when set off by quotes (I also tried
guillemets). Or, the inevitable third thing that I'm not even thinking of.
It should be said that the "funny-named" file does contain the PostScript
content that I need, having been TYF'd through POSTGHST.PRN.

All the best to everyone,

Fred WeinerÂ