Thank you Eric,
That was the problem, it appears that there is an odditiy in TightVNC where it
doesn't assign x-fonts properly. For anyone who runs into the problem in the future,
the easiest fix is to add the following line to the file in (for FreeBSD)
"/usr/X11R6/bin/vncserver"
$fontPath = "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/";
Thank you again for the help,
Frank Berthold
> >>>>> "fb" == Frank Berthold <[EMAIL PROTECTED]> writes:
>
> the problem seems to due to Hemlock trying to open a font that you
> don't have installed. (NAME-ERROR is being signaled by CLX, and it's
> telling you that an OpenFont call failed on the X11 server; the rest
> of the error message is the Motif debugger failing noisily).
>
> Hemlock under X defaults to trying to use X11 fonts named
>
> "*-courier-medium-r-normal--*-120-*"
> "*-courier-medium-o-normal--*-120-*"
> "*-courier-bold-r-normal--*-120-*"
>
> and will fail if the X11 server doesn't have these available. You can
> change the default fonts from your Hemlock initialization file, for
> example
>
> ,---- $HOME/.hemlock-init.lisp
> | (in-package :hemlock)
> |
> | (setv default-font "fixed")
> | (setv open-paren-highlighting-font "fixed")
> | (setv active-region-highlighting-font "fixed")
> `----
>
> --
> Eric Marsden <URL:http://www.laas.fr/~emarsden/>
