> We also ran into the Emacs/XEmacs conflict problem. I didn't know if There should be an xemacs that deals with this soon (it's been fixed on the emacs side, but I haven't seen an updated xemacs yet.)