Hello, I'm not sure where this bug lies, so I thought I'd ask for advice here. The general issue is that the loaded files seem to be inconsistent between libraries included with xemacs and separate add-on files. Specifically, XEmacs includes a version of a Haskell mode in /usr/share/xemacs21/xemacs-packages/lisp/haskell-mode , while I also have installed a different (more recent) version from the haskell-mode package in /usr/share/emacs/site-lisp/haskell-mode . When I start a fresh XEmacs (with '-no-init-file' to be safe) I get a message turn-on-haskell-font-lock is obsolete. Use turn-on-font-lock instead. on the mode line. I haven't investigated completely, but this message seems to come from the file /usr/share/emacs/site-lisp/haskell-mode/haskell-mode.el (in the haskell-mode library), while the call to 'turn-on-haskell-font-lock' seems to come from the autoloads generated from the version included in XEmacs, where this call was not declared obsolete. Whose bug is this? Is it haskell-mode's bug, for stepping on the toes of a package included in XEmacs? It might be a consequence of this interaction, but the font-lock mode does not in fact work when editing a literate Haskell file (ending with .lhs): there are constant complaints of the form (5) (warning/warning) Error caught in `font-lock-pre-idle-hook': (error No such face haskell-default-face) Peace, Dylan
Attachment:
signature.asc
Description: Digital signature