Re: docstrings vs Mule/no-Mule coexistence
>>>> "Bill" == William M Perry
<wmperry(a)aventail.com> writes:
Bill> Christoph Wedler <wedler(a)fmi.uni-passau.de> writes:
> Hi, I like to have both XEmacs-21.0/Mule and XEmacs-21.0/no-Mule.
I had
> hoped that this would be possible without two completly independent (=
> redundant) installations.
>
> I.e., I made both XEmacsen by
>
> 1. ./configure .... `--with-mule'
> 2. make
> 3. mv src/xemacs src/xemacs-mule
> 4. ./configure ....
> 5. make
>
> The problem now is that the docstrings are incorrect for XEmacs/Mule,
> e.g., I get
>
> `set-face-property' is a compiled Lisp function
> -- loaded from "/home/clstaff/wedler/xemacs/xemacs-21.0.59/lisp/faces.elc"
> (set-face-property FACE PROPERTY VALUE &optional LOCALE TAG-SET HOW-TO-ADD)
>
> Documentation:
> turned), 'all (all specifications will be
> returned), or nil (the actual specifier object will be returned).
>
> See `glyph-property' for more information.
>
> Any idea how I get correct docstrings in both XEmacs-21.0/Mule and
> XEmacs-21.0/no-Mule?
Bill> You need to install them in different directories. Emacs/XEmacs does not
Bill> deal well with _any_ differences in the DOC file. the documentation
Bill> strings are stored as offsets into the file, and if you add/remove a
Bill> function from a XEmacs (as building w/mule does) and remake the DOC file,
Bill> you lose.
If you're sufficiently clever, you *can* rename both the binaries and
the doc files.
make install
mv xemacs xemacs-mule
mv DOC DOC-mule
then build and install the non-mule xemacs.
THEN, you have to teach xemacs-mule to use DOC-mule as its doc file.
You can do that via something like:
(setq internal-doc-file-name "DOC-mule")
in some appropriate init file.
Martin