On June 6, Jaime Villate wrote:
> it is a bug that I accidentally introduced in 5.18.1. A quick-hack to
> fix it is to replace lines 3797 and 3798 in xmaxima from:
>
> set fontMap([font create -family {Bitstream Vera Sans Mono} -size 10])
> [list Courier 10]
> set fontMap([font create {helvetica 16 normal}]) [list Helvetica 16]
>
> to:
>
> catch {set fontMap([font create -family {BitstreamVeraSansMono} -size
> 10]) [list Courier 14]}
> catch {set fontMap([font create {helvetica 16 normal}]) [list Helvetica
> 16]}
>
> Unfortunately, in Windows xmaxima is wrapped inside a starkit file so
> you need some knowledge of those files in order to fix it. I will see if
> I can modify that starkit in the next few days. In the meantime, you can
> call plotdf from console-maxima instead of xmaxima. In console-maxima a
> new wish process is open for each plotdf, so that error
> does not appear.
>
thanks for the info. One of the nice things about Maxima (at least with
windows) is that I
can open multiple independent window sessions of Xmaxima and also console
maxima, so this makes
it easy to transfer the plotdf stuff to console while mainly working with
Xmaxima.
Ted