Path: utzoo!attcan!uunet!peregrine!elroy.jpl.nasa.gov!usc!rutgers!dimacs.rutgers.edu!seismo!seismo.CSS.GOV!bonnett
From: bonnett@seismo.CSS.GOV (H. David Bonnett)
Newsgroups: comp.windows.x
Subject: Re: xterm default font
Message-ID: <49247@seismo.CSS.GOV>
Date: 5 Dec 90 21:46:37 GMT
References: <1990Dec5.011516.1691@yogi.fhhosp.ab.ca> <49246@seismo.CSS.GOV> <KHERA.90Dec5153210@thneed.cs.duke.edu>
Sender: usenet@seismo.CSS.GOV
Reply-To: bonnett@seismo.CSS.GOV (H. David Bonnett)
Organization: Center for Seismic Studies, Arlington, VA
Lines: 27

In article <KHERA.90Dec5153210@thneed.cs.duke.edu>, khera@thneed.cs.duke.edu (Vick Khera) writes:
|>  bonnett@seismo.CSS.GOV (H. David Bonnett) [Me] writes: 
|>    and from my .xresourcerc (Xdefaults)
|>    xterm*Font:                     *courier-medium-r-*-140-*               
|>    The * tells xrdb to ignore all intermediate classes.  
|>    xterm.vt100.font :              *courier-medium-r-*-140-*
|>    should work as well.
|> 
|> one thing to note is that because of the way xterm handles resources,
|> if you specify fonts this way you cannot override them using command
|> line switches like -fn to set the font.  I set my default font in
|> .Xdefaults as:
|> 
|> XTerm.vt100.font: -*-courier-medium-r-normal-*-14-*-*-*-*-*-*-*
|> 
|> which uses the xterm class name so i can use the command line
|> switches.  not all applications work this way, though.
|> --

Gee, That's interesting........ (From my .mwmrc file)

    "Big Window"        f.exec "xterm -fn 9x15bold -T BigLocal -n Big -132 &"
This works just fine on my machine under motif 1.1.  Of course, not setting
a bold fonts causes some side effects with curses et al.

-dave bonnett; Center for Seismic Studies
      bonnett@seismo.css.gov -