>> 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)

This works for me.  We just installed 21.1 yesterday and I've only
been using it for less than a day, so it's hard to say if there will
be other issues.

I can say that I had problems with the mh-e package.  In case anyone
uses it, I had to redefine one function in mh-utils.el to get proper
display behavior in the folder buffers:

(defun mh-recenter (arg)
  ;; Like recenter but with two improvements: nil arg means recenter,
  ;; and only does anything if the current buffer is in the selected
  ;; window.  (Commands like save-some-buffers can make this false.)
  (if (eq (get-buffer-window (current-buffer))
	  (selected-window))
      (recenter (if arg arg t))))

and the emacs maintainers are going to fix the recenter bug, according
to the discussion on gnu.emacs.bug.

>> 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
>> >
>> >
>> 
>> 

Kevin Layer             <Franz.COM at layer>        http://www.franz.com/
Franz Inc., 1995 University Avenue, Suite 275, Berkeley, CA  94704, USA
Phone: (510) 548-3600   FAX: (510) 548-8253