XEmacs suddenly doesn't work on my Mac

Greetings,

I don't know how much support is available on this list any more, but
it does appear that people can report problems and get responses.

I'm running XEmacs beta (21.4 patch 22) on my up-to-date iMac running
El Capitan. (Mac OS X 10.11.5)

Yesterday I got a note that there was an update to XQuartz. I've never
had a problem with it, so routinely install updates.

After installing the new version, when I start XEmacs the usual way
(from a menu ... but I also tried it from a terminal command line), I
get this message on STDERR:

X server not responding
: "/private/tmp/com.apple.launchd.zC9wJRhG9U/org.macosforge.xquartz:0.0"

(The com.apple.launchd.* component is different at different times.)

I can run xemacs -nw, but because of my startups it's not nice. And I
can run xemacs -nw -q, but who wants to do that except to debug?

I've used various Emacsen constantly since 1987 and XEmacs since it
was pre-beta in the early 90s on every platform. To me if an OS
doesn't run XEmacs, it's not a computer.

I've considered biting the bullet and switching over to GNU Emacs, but
I really, really don't want to do that. I *like* XEmacs the way it is,
and just want it to continue working for me. Besides which, I'm buried
in work and don't really have the time.

Boo hoo, right? But I thought I'd share that in case one of the local
wizards who is still around here has seen this and worked through it
and can share some information.

Much thanks to all who continue to support XEmacs.

-- 
Lynn David Newton
Columbus, Ohio
neologisticsediting.com
lynndavidnewton.com