I just want to say (I believe) I have finally got multiple major modes
to work woth nxhtml-mode (derivated from nxml-mode). I had to sacrifice
the nxml way of fontifying the xhtml code. Instead I use
sgml-mode/html-mode for that. I can see no way around this (without
chaning nxml-mode quite heavily). IMO there is however no big drawback
using sgml-mode/html-mode for fontifying.
I guess most of the lurkers here does not mix pure XHTML mode with
embedded modes very often, but you can now also use nxhtml-mode with php
for example. Links are here:
http://ourcomments.org/Emacs/nXhtml/doc/nxhtml.html
http://www.emacswiki.org/cgi-bin/wiki/MuMaMo
I am however not quite satisfied with this when using php. My
recommended approach right now is to use nxhtml-part-mode for this, but
I wish this was a bit better written. I would be glad for some hints here.
The problem is that the headers needed to get nxml-mode happy enough for
completion is seldom there in a php file. Currently I solve this by
adding those headers (hidden) and then remove them when saving the file.
A much better approach IMO would be to tell the rng parser to start from
another state. Can someone see any simple way to do this?
I have been thinking about having another buffer with the headers and
then get the initial state for parsing the php buffer from that buffer.
I had not looked into the details - eh, mostly because they are
complicated. Has someone of you tried this? Or do you have any hints?
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/emacs-nxml-mode/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/emacs-nxml-mode/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:emacs-nxml-mode-digest@xxxxxxxxxxxxxxx
mailto:emacs-nxml-mode-fullfeatured@xxxxxxxxxxxxxxx
<*> To unsubscribe from this group, send an email to:
emacs-nxml-mode-unsubscribe@xxxxxxxxxxxxxxx
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|
