I am not familiar with MULE at all, and can't say that I read bytecode, so I'm asking for a little guidance here. I compiled XEmacs 21.1.2 without MULE (on Irix 6.2 and various flavors of Solaris), installed the non-MULE SUMO, and have been putting the result through its paces. At one point, I tried to file a bug report. I got an error instead, "Symbol's value as variable is void: mime-charset-coding-system-alist". Somewhat surprised, I just did a setq of that variable to nil and continued. Then I got "Symbol's function definition is void: find-coding-system". Digging a little further, I see the following chain of events. I am a Gnus user. I am also a PGP user. So when my .gnus is loaded, tm-pgp.el gets loaded as well in support of the PGP-related hooks. In turn, tm-pgp.el loads tm-play.el. Poking around in tm-play.el, I found that evaluation led to two errors. First, this definition on line 271: (defvar mime-article/coding-system-alist (list (cons 'mh-show-mode *noconv*) (cons t (mime-charset-to-coding-system default-mime-charset)) )) produces the message "defvar treated as defconst". Second, everything above this point is defined; neither this variable nor anything below it is defined. Evaluating the body of this variable definition in *scratch* leads to the unsurprising result: ((mh-show-mode) (t . iso-8859-1)) However, look at the first part of this Lisp backtrace (manually wrapped): Signaling: (void-variable mime-charset-coding-system-alist) byte-code("..." [boundp mime-article/coding-system-alist mh-show-mode *noconv* t default-mime-charset nil lbt charset intern mime-charset-coding-system-alist cs format "%s-%s" CRLF dos LF unix CR mac find-coding-system mime-charset-to-coding-system-default-method current-load-list MULE mime-article::write-region #<compiled-function (start end file) "...(19)" [major-mode mime-article/coding-system-alist t file-coding-system write-region start end file] 4> featurep mule #<compiled-function (start end file) "...(19)" [major-mode mime-article/coding-system-alist t coding-system-for-write write-region start end file] 4> NEMACS #<compiled-function (start end file) "...(19)" [major-mode mime-article/kanji-code-alist t kanji-fileio-code write-region start end file] 4> defalias write-region] 10) load-internal("tm-play" nil t nil nil nil) load("tm-play" nil t nil) require(tm-play) load-internal("tm-pgp" nil t nil nil nil) load("tm-pgp" nil t nil) require(tm-pgp) It looks to me like this file was byte-compiled with a MULE-enabled XEmacs. Am I right? I'm not certain, because I tried to recompile it and got the same error message out of the byte compiler. Am I barking up the wrong tree? Any direction is much appreciated. Thanks, -- Jerry James Email: jerry(a)cs.ucsb.edu WWW: http://www.cs.ucsb.edu/~jerry/