At Sun, 23 Jun 2002 21:30:52 -0400,
James LewisMoss <[EMAIL PROTECTED]> wrote:
> Tatsuya> I found a bug of mew package that mew doesn't work on
> Tatsuya> xemacs21-nomule. (Bug#150432)
>
> If a package depends on the mule capabilities of xemacs then it should
> depend on xemacs21-mule | xemacs21-mule-canna-wnn |
> xemacs21-gnome-mule | xemacs21-gnome-mule-canna-wnn (looking at this
> now it seems a bit long, but that's the current state).
Mew uses Mule feature, but Mew considers non-Mule also. Mew
doesn't use Mule feature directly.
For instance,
mew-mule3.el:
(defmacro mew-piolet (read write &rest body)
`(let ((coding-system-for-read ,read)
(coding-system-for-write ,write))
,@body))
mew-mule0.el:
(defmacro mew-piolet (input output &rest body)
`(progn ,@body))
The above defines the mew-piolet macro. If (featurep 'mule),
then mew-mule3.el is used. If (not (featurep 'mule)), then
mew-mule0.el is used. So Mew works for both Mule and non-Mule.
However, Mule-compiled *.elc require Mule feature. Also,
non-Mule-compiled *.elc lack Mule feature.
That's `incompatibility of *.elc', I said.
--
Tatsuya Kinoshita
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
