Colin> I hadn't thought of it that way. Now you've got me thinking about a Colin> good way to specify the doc-file name. Colin> Maybe a configure option? There are a lot of options already, but I Colin> really don't want to generate a unique doc-file name unnecessarily. Colin> On the other hand, most people don't even realize this is a problem, Colin> so maybe this really should be a forced option. Colin> So I create a bitmask of all the configure options set, generate a Colin> uuencoded string, and the doc-file name is XL4J.DOC. This may Colin> actually work. If I'm only allowed [A-Z0-9], I can sqeeze in 5 Colin> options per character. With an 8+3 filename limit, that's 40 options. Sun already tried to deal with the multiple DOC file issue. Check out this tidbit from sunpro/sunpro-init.el: ;; Sunpro ships the mule version as a 2-file addition to the ;; non-mule distribution - the binary and the doc file. ;; ;; This is a quick hack, I know... ;; There ought to be a better way to do this. ;; Perhaps a --xemacs-flavor=mule flag? (if (featurep 'mule) (let ((mule-doc-file-name (concat internal-doc-file-name "-mule"))) (if (file-exists-p (concat doc-directory mule-doc-file-name)) (setq internal-doc-file-name mule-doc-file-name)))) I've implemented Colin's addition to site-start.el, taking the above hack into account. Isaac