henry@yogi.fhhosp.ab.ca (12/05/90)
How do I get xterm to come up with a different default font (ie the font you get when it first fires up)? What's the resource name? Thanks, -Henry Bland
bonnett@seismo.CSS.GOV (H. David Bonnett) (12/06/90)
From the man page of xterm (SunOS 4.1.1)
" The following resources are specified as part of the vt100
widget (class VT100):
....
boldFont (class Font)
Specifies the name of the bold font to use instead
of overstriking.
....
font (class Font)
Specifies the name of the normal font. The default
is ``vtsingle.''
"
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.
BTW: All of this is from the man pages available online on most Unix
machines......
-dave bonnett; Center for Seismic Studies
bonnett@seismo.css.gov -etaylor@wilkins.iaims.bcm.tmc.edu (Eric Taylor) (12/06/90)
In article <1990Dec5.011516.1691@yogi.fhhosp.ab.ca>, henry@yogi.fhhosp.ab.ca writes: |> How do I get xterm to come up with a different default font (ie the font |> you get when it first fires up)? What's the resource name? |> |> Thanks, |> -Henry Bland -font -- Eric Taylor Baylor College of Medicine etaylor@wilkins.bcm.tmc.edu (713) 798-3776
khera@thneed.cs.duke.edu (Vick Khera) (12/06/90)
In article <49246@seismo.CSS.GOV> bonnett@seismo.CSS.GOV (H. David Bonnett) 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.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vick Khera, Gradual Student/Systems Guy Department of Computer Science
ARPA: khera@cs.duke.edu Duke University
UUCP: ...!mcnc!duke!khera Durham, NC 27706 (919) 660-6528bonnett@seismo.CSS.GOV (H. David Bonnett) (12/06/90)
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 -
geg@beep.mlb.semi.harris.com (Greg Garland) (12/06/90)
In article <KHERA.90Dec5153210@thneed.cs.duke.edu>, khera@thneed.cs.duke.edu (Vick Khera) writes: |> In article <49246@seismo.CSS.GOV> bonnett@seismo.CSS.GOV (H. David Bonnett) 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. |> |> line switches like -fn to set the font. I set my default font in |> .Xdefaults as: |> XTerm.vt100.font: -*-courier-medium-r-normal-*-14-*-*-*-*-*-*-* |> | Does anybody know if there is a good reason for Sun using such a brain-dead method of specifying font names in OpenWindows? What was wrong with the MIT release's method of using a fonts.alias file so that you could refer to this font by a simple name of say... courR14? -- Greg Garland - Alive, occupying space, and exerting gravitational force MS 62-024, Harris Semiconductor Sector, PO Bx 883, Melbourne FL 32905. geg@beep.mlb.semi.harris.com "Never let the facts interfere with your perception of reality."
fgreco@dprg-330.GOVt.shearson.COM (Frank Greco) (12/14/90)
> |> > |> line switches like -fn to set the font. I set my default font in > |> .Xdefaults as: > > |> XTerm.vt100.font: -*-courier-medium-r-normal-*-14-*-*-*-*-*-*-* > |> > | > > Does anybody know if there is a good reason for Sun using such a > brain-dead method of specifying font names in OpenWindows? What This naming convention is derived from X Window (actually ISO), so in all fairness, don't blame it on Sun. > was wrong with the MIT release's method of using a fonts.alias > file so that you could refer to this font by a simple name of > say... courR14? > Nothing prevents you from doing this for OW. Frank G.