by Per my question last week about reducing the memory footprint of a
minimalist X desktop, I abandoned KDE and Gnome altogether and now I just
launch sawfish, sawfish-client, and an Xterm window at startup. The
titlebars were hard to read and I figured I would change them to a
different font, such as the Comic TTF that I ported over from my old Win95
directory.
Alas! The font list that sawfish-ui offers does not include the fonts in
my truetype path.
Interestingly, "xset q" doesn't show the truetype path either. I have only
the one line in my XF86Config file, per xfs recommendations:
FontPath "unix/:7100" Then all the fonts are specified in the
/etc/X11/fs/config file in the catalogue section. So where does xset q get
this font path:
/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/
lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fon
ts/100dpi/
Finally, when I brought up kcontrol, KDE does recognize the xfs font path.
So... is it normal for xset and sawfish to be unaware of xfs, or am I doing
something wrong?
--
Peter B. Steiger
Cheyenne, WY
If you reply by email, send it to pbs at com dot
canada (or vice-versa). All adverti*ts will be
returned to your postmaster, eh!