I recently encountered a similar problem because I upgraded to GNU/Emacs
21.1 (yes, there's a new version!!!) My solution was to modify
acl60/eli/fi-site-init.el, the function fi::emacs-type.

Old line
	  ((string-match "^20\." emacs-version) 'emacs20)
New line
	  ((string-match "^2[01]\." emacs-version) 'emacs20)

A similar solution might work for your xemacs problem.

BTW, anybody know if there's something unkosher about doing this?

Best,
Ilya

> -----Original Message-----
> From: Andrew Philpot <ISI.EDU] at [mailto:philpot>
> Sent: Tuesday, October 23, 2001 2:20 PM
> To: <cs.berkeley.edu at allegro-cl>
> Subject: using ELI under xemacs
>
>
>
> Does anyone have any experience running the emacs-Lisp interface of
> ACL6 under xemacs?
>
> I have xemacs 21.1, which has
>
>   emacs-version => "21.1 (patch 14) \"Cuyahoga Valley\" XEmacs Lucid"
>
> I get an error upon startup, an error which looks like it occurs
> during parsing of the above string.  ELI continues past the error, but
> this is the sort of thing I like to correct or at least paste
> over for
> the benefit of concerned onlookers.
>
> Since the manual states
>
>   The most common cause of other strange or unexplained behavior is
>   using the Emacs-Lisp interface with a version of Emacs other than
>   the one distributed with Allegro CL. The Emacs-Lisp interface is
>   only supported on that specific version.
>
> I know I can't get any support from Franz on this one.
>
> Everything is fine on GNU Emacs 19.34.1 which has
>
>   emacs-version => "19.34.1"
>
> so I suspect this comes from xemacs' baroque syntax for emacs-version.
> Accordingly, I would think the appropriate fix is to patch xemacs'
> implementation of emacs-version to nuke some of the extraneous
> verbiage, at least locally while ELI is getting started.  If someone
> else has been here before, please let me know how you handled it.
>
> Andrew
>
>