🚀 go-pugleaf

We encountered a small problem recently that involves switching
between fonts using x-set-font and x-set-kfont in nemacs.

We were switching between three sizes of Kanji fonts when nemacs
locked up, dumped core, and dumped us out of X. We know that part of
the problem was the number of users on the machine(limited memory).

The x-set-font (x-set-kfont) functions only call XLoadQueryFont. What
happens if the font is already loaded? Does XLoadQueryFont simply
return the XFontStruct* ? I'm thinking, "probably not", because of the
time delay(above and beyond the expected delay due to machine load) in
loading the new Kanji font. These fonts range from about 500k (14 point
font) to somwhere in the neighborhood of about 975k (24 point font).
Not small!

Is this an X (R3) bug or should the x11fns.c file be fiddled to check to
see if the font is cached already before doing the load?

--
-----------------------------------------------------------------------------
mleisher@nmsu.edu                      "I laughed.
Mark Leisher                                I cried.
Computing Research Lab                          I fell down.
New Mexico State University                        It changed my life."
Las Cruces, NM                     - Rich [Cowboy Feng's Space Bar and Grille]