🚀 go-pugleaf

I got three helpful responses to my posting (although I wasn't really 
asking for help; by the time I posted I had cured the problem or the 
problem had cured itself.)

-----

Begin forwarded message (from Scott Hess):


  Logout out and login as exit to kill the windowserver.  Or,
  perhaps it's good enough to logout/login.  

Latter didn't work; I presume the former is a weaker form of reboot, 
which did cure the mouse.

  I've had the
  problems with Courier as the window titles, and it's not
  something that "sticks", it just goes away for no reason I am
  certain of.  But I suspect that it's something in the
  windowserver that gets wedged, which is why the
  exit-the-windowserver advice ...

It did go away on the next (second) reboot, but then I had also found 
"dread" showed GLOBAL NXFont Courier, which I did a dwrite GLOBAL NXFont 
Helvetica before that.  It may or may not have had any affect.

-----

Begin forwarded message (from Art Isbell):

  I've not lost my cursor (well, I have, but it's happened when 
  something panicked the system :-), but I have seen the Courier font 
  in Window titles, Menus, etc.  The cure is to just restart the 
  window server by typing "exit" and 2 returns in the Login Panel.  
  Then when the Login Panel reappears, log in as usual and the fonts 
  should be normal.  I don't know why this occasionally happens, but 
  it has been so rare that I just ignored it.

Sounds consistent with Scott's experience.

-----

Begin forwarded message (from Soo Lee):

  - run Terminal
  - type "pft" followed by return.
  - type "showcursor" and hit return; if you don't get the cursor 
    back, type "showcursor" a few more times. 
  - then type "Control-D" to exit

Interesting -- I didn't know about pft.  Next time, if it ever happens again.

  I am afraid your "~/.NeXT" directory is munged by crash or some 
  mishap like disk full. Copy fresh ".NeXT" to rebuild your own from 
  somewhere others account. Before copy another .NeXT, it might work 
  well if you remove ~/.NeXT/.NeXTdefaults.L.

Well, no crash or disk-full or whatever.  This is also a new approach (for 
me), but, as noted above, the problem already went away.

Thanks, everybody.

   Dick Silbar