On Sun, Mar 18, 2012 at 11:13 PM, Mike Kupfer <mike.kupfer(a)xemacs.org> wrote:
Bruce Visscher wrote:
> Removing what little was in ~/.xemacs did not help. I haven't done
> anything to the X11 fonts on this system and I could not find a
> .Xresources or .xinitrc file anywhere.
Hmm. Does starting XEmacs with "-vanilla" change the behavior?
No,
Come to think of it, I thought XEmacs defaulted to Courier if there
was
a font problem. But looking at my system, I don't see any "courier"
fonts, just "courier new" and "courier 10 pitch". I'm not sure
what
you'd need to change in the source (if anything) to get XEmacs to use
"courier new" instead of "courier". Maybe someone else can chime in
here...
I came up with a couple shell commands that might give us more clues:
xemacs -vanilla -eval "(shell-command (concat \"echo \" (face-font-name
'default) \" > `tty`\"))" -kill
Warning: Cannot convert string
"-*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct
-*-*-medium-r-*-*-*-120-*-*-c-*-*-*
xemacs -eval "(shell-command (concat \"echo \"
(face-font-name 'default) \" > `tty`\"))" -kill
Warning: Cannot convert string
"-*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct
-*-*-medium-r-*-*-*-120-*-*-c-*-*-*
There's probably a more elegant way to get this information, but
my Lisp
skills aren't up to the task...
mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta