Is there a working nxml-mode in XEmacs?

[FKtPp]

--- "Stephen J. Turnbull" <stephen at xemacs.org> wrote:

> It's me FKtPp ;) writes:
> 
>  > just run into problem of "can not redefine coding system
> 'us-ascii'"
>  > error while byte-compiling the xemacs-enc.el.
> 
> That's bad.  Who wrote xemacs-enc.el?

well, the problem is coding-system-p in XEmacs always return nil when
invoked using the form of:

(coding-system-p 'us-ascii)
(coding-system-p 'cn-gb-2312)

How should it be invoked? Or, in other words, how can I pass a OBJECT
to a function? Is it a coding-system-p bug or a invoking method bug?

> 
>  > I've also tried change xemacs-related make-coding-system call into
> a
>  > nil.
> 
> That's not going to be acceptable, and it's unlikely to work, anyway.
> 

Don't worry, I just want to see what was left preventing me to
byte-compile all the source files.

>  > And then all this code will byte-compiled, and then if I trying to
>  > run the byte-compiled nxml-mode It then complains of no such a
>  > function #'overlays ...
> 
> (require 'fsf-compat)
> 
> But your troubles are just starting, because (unless things have
> changed dramatically) you're going to find lots of dependencies on
> the
> GNU way of doing font-lock which has diverged substantially from
> ours.

Good news :D


      ____________________________________________________________________________________
Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping