Got it. Need to run ttmkfdir BEFORE mkfontdir (doh). I'm going back to bed.
Thanks for the kick in the right direction.
Benn
-Original Message-
From: Benn Schreiber [mailto:[EMAIL PROTECTED]
Sent: Monday, September 29, 2003 3:20 PM
To: '[EMAIL PROTECTED]'
Subject: Re: x
> Did you have to run ttmkfdir (or whatever it is called) at any point?
> Harold
Yes, I have run both ttmkfdir and mkfontdir in the directory. Interestingly,
if I do the xset after the window manager is up (as best I can correlate
it), it works fine. But, if I do it in startxwin, the font element
4.3.0-9
From: "Benn Schreiber" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
Subject: xset add to font path kills Xserver
Date: Mon, 29 Sep 2003 08:40:05 -0700
I just upgraded my system to the latest XFree (4.3.0-4, I believe). In my
startxwin I had
4.3.0-1
XFree86-lib-compat 4.3.0-1
XFree86-man 4.3.0-1
XFree86-prog4.3.0-4
XFree86-ps 4.3.0-1
XFree86-startup-scripts 4.2.0-5
XFree86-xserv 4.3.0-9
From: "Benn Schreiber" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: <
Benn Schreiber [EMAIL PROTECTED] wrote:
> 1) Have you successfully added truetype fonts to your font
> path? If so, how?
I have. You need an XF86Config file in /etc/X11. There is
a link to an example XF86Config file in the cygwin/xfree
FAQ or User Guide (I can't get to the site right now to
fi
I just upgraded my system to the latest XFree (4.3.0-4, I believe). In my
startxwin I had an xset fp+ to add the truetype fonts directory to the font
path (which I never got working...perhaps this is a hint, but...)
With the latest bits the Xserver core dumps shortly after the xset fp+
happens.
S