🚀 go-pugleaf

Emacs 19.25.  Sun Sparc 1 running SunOS 4.1.3.
MIT X11R5.  Compiled with --with-x-toolkit.

I tried to run the following code:

================================================================
;;; From: dgilbert@pci.on.CA (David Gilbert)

;;; This cool function should allow us to move our emacs windos from
;;; machine to machine.
(defun X-move-me (server)
  "move the emacs from the current machine to the specified machine"
  (interactive "sEnter Display :\n")
  (setq X-move-config (current-frame-configuration))
  (x-close-current-connection)
  (x-open-connection server)
  (setq default-minibuffer-frame
        (setq frame-initial-frame
              (new-frame initial-frame-alist)))
  (display-buffer (get-buffer-create "*scratch*"))
  (insert (format "%s" (current-frame-configuration)))
  (write-file "/home/other/dgilbert/tmp/temp")
;  (set-frame-configuration current-frame-configuration)
  (print "Hi Mom!")
  (redraw-display))

(X-move-me ":0.0")
================================================================

When I run this code, Emacs dies with the following error:

X protocol error: BadFont (invalid Font parameter) on protocol request 55


I then ran Emacs under the debugger.  I set a breakpoint where Emacs
makes a new X connection and XSynchronize there (incidientally it
would be handy to have some global variable I could set that would
make Emacs do this for me).

I found that Emacs was dying on line 888 of xlwmenu.c:

  mw->menu.foreground_gc = XtGetGC ((Widget)mw,
				    GCFont | GCForeground | GCBackground,
				    &xgcv);


Beyond this, I am not certain what the bug might be.  I speculate that
Emacs is caching information about the font that it is not allowed to
cache across server connections, but I have not checked this (I think
this could be the case because Emacs did this in the non-Xt case a few
releases ago.  I have not checked since then).

Tom
---
tromey@busco.lanl.gov             Member, League for Programming Freedom
"`Nova heat moving in,' dig?" -- Robert Anton Wilson