From: Mail@JoesLife.org   
      
   On Tue, 6 Aug 2024 17:41:47 -0000 (UTC), Lew Pitcher wrote:   
      
   > Probably not. I haven't looked at what the -class and -u8 options to   
   > xterm do to the display, but your problem was strictly related to the   
   > choice of font.   
   >   
   >> So what was going on? And why did uxterm contain code that I didn't   
   >> need?   
   >   
   > Because uxterm does more than support /your/ needs, so it includes code   
   > to support a wide variety of needs as well.   
      
   I appreciate your taking a crack at an answer!   
      
   FWIW I decided to go with what I had.  It seemed I got success with my   
   scripts that called xterm when I used DejaVu Sans Mono.  My life was made   
   complicated, however when I tried to embody that choice of font in a   
   variable.  It occured to me that that was what the user really needed--a   
   way to work with my scripts yet still have control over the font.   
      
   I found that this worked in my .fvwm2rc:   
      
      SetEnv font "-fa DejaVuSansMono -fs 9"   
      
   And the value assigned to variable "font" was then available in my   
   scripts.  So the problem was solved.   
      
   Note however that I used "DejaVuSansMono" and not "'DejaVu Sans Mono'".   
   That was the complication I referred to above.  Removing the single   
   quotes and the spaces in the font name was a simple, but not obvious   
   solution.   
      
   I thought you would like to see where this bunny trail went.  So there   
   you are!   
      
   Thanks for your help!   
      
   -Joe   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)