attribute name. I would prefer to have a variable to control this
| setting, say, 'nxml-indent-attribute-value', which when set to
| non-nil, would generate the following indentation:
|
|     <div tal:define="tabindex tabindex/next;
|                      error_workflow_action errors/workflow_action|nothing;
|                      objs request/ids|nothing;
|                      review_state_label string:No change;
|                      target python:test(objs, objs, here);"
|                      tal:attributes="class
| 	             python:test(error_workflow_action, 'field error', 'field')"
|          tal:condition="not:anonymous">
|
| Does that sound reasonable, or should I just get used to it?

Hmm, I've noticed the same thing, although I'd actually prefer:

      <div tal:define="tabindex tabindex/next;
                       error_workflow_action errors/workflow_action|nothing;
                       objs request/ids|nothing;
                       review_state_label string:No change;
                       target python:test(objs, objs, here);"
           tal:attributes="class
                           python:test(error_workflow_action, 'field error',
'field')"
           tal:condition="not:anonymous">

What I have noticed, as a workaround, is that if you ident the second line
of the attribute value by hand, nxml-mode indents all the rest of the lines
"correctly".

                                         Be seeing you,
                                           norm

--
Norman Walsh <normyahoo@...> | Simplicity is always a
http://nwalsh.com/                  | virtue.--Edward Abbey

hello all, I am not sure if someone already noticed this, but I just tried
nxml-mode-20030929, using the following stylesheet:

<paste>
<?xml version="1.0" encoding="utf-8" ?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="html" indent="yes" version="4.0"/>

<xsl:template match="x">
  <xsl:apply-templates select="Hello"/>
</xsl:template>

<xsl:template match="Hello">
  <xsl:param name="x" select="/x/count"/>
  <xsl:copy-of select="."/>
  <xsl:if test="$x > 1">
    <xsl:apply-templates select=".">
     <xsl:with-param name="x" select="$x - 1"/>
    </xsl:apply-templates>
  </xsl:if>
</xsl:template>
</paste>

and it kept giving me this error:

<paste>
[root@nike html]# java org.apache.xalan.xslt.Process -HTML -in
throwaway.xml -xsl throwaway.xsl -out throwaway.html
[Fatal Error] throwaway.xsl:27:1: XML document structures must start and
end within the same entity.
file:///var/www/html/throwaway.xsl; Line #27; Column #1; XSLT Error
(javax.xml.transform.TransformerConfigurationException):
javax.xml.transform.TransformerException: org.xml.sax.SAXParseException:
XML document structures must start and end within the same entity.
</paste>

then I realized I had forgotten the closing </xsl:stylesheet> tag and nxml
did not catch it !  There was no red underscore and I believe there should
be if an end tag is missing, what ?

On Fri, Jan 02, 2004 at 07:49:24AM -0800, tpc@... wrote:

|    hello all, I am not sure if someone already noticed this, but I just tried
|    nxml-mode-20030929, using the following stylesheet:
[deletia]
|    then I realized I had forgotten the closing </xsl:stylesheet> tag and nxml
|    did not catch it !  There was no red underscore and I believe there should
|    be if an end tag is missing, what ?

Hmm. Worksforme with the same version.

[I also get an error on the <?xml ...?> PI being on the second line
  ... specifically: "Processing instruction target is xml".]

...jsled

--
http://www.asynchronous.org - `a=jsled; b=asynchronous.org; echo ${a}@${b}`

hello all, I am not sure if someone already noticed this, but I just tried
| nxml-mode-20030929, using the following stylesheet:
|
| <paste>
| <?xml version="1.0" encoding="utf-8" ?>

I presume you added "<paste>" for the email message and the content actually
begins with the XML declaration and ends with </xsl:template>.

| then I realized I had forgotten the closing </xsl:stylesheet> tag and nxml
| did not catch it !  There was no red underscore and I believe there should
| be if an end tag is missing, what ?

If your document literally ends with the ">" in </xsl:template>, what can
nxml-mode underline? There's no content that's wrong to underline.

If you put a newline after the ">", it'll be underlined in red.

                                         Be seeing you,
                                           norm

--
Norman Walsh <normyahoo@...> | Formal symbolic representation of
http://nwalsh.com/                  | qualitative entities is doomed to
                                     | its rightful place of minor
                                     | significance in a world where
                                     | flowers and beautiful women
                                     | abound.--Albert Einstein

hi Josh,

I went to the document again, deleted the </xsl:stylesheet> and noticed
it does say "missing end tag," and only if you press Enter at the end of
the last line do you get the red underscore, but if you backspace delete the
newline then it disappears and just says "missing end tag," but as soon as
you scroll to any other part of the file there is no indication that you
are in need of an end stylesheet tag.

On Fri, 2 Jan 2004, Josh Sled wrote:

> On Fri, Jan 02, 2004 at 07:49:24AM -0800, tpc@... wrote:
>
> |    hello all, I am not sure if someone already noticed this, but I just
tried
> |    nxml-mode-20030929, using the following stylesheet:
> [deletia]
> |    then I realized I had forgotten the closing </xsl:stylesheet> tag and
nxml
> |    did not catch it !  There was no red underscore and I believe there
should
> |    be if an end tag is missing, what ?
>
> Hmm. Worksforme with the same version.
>
> [I also get an error on the <?xml ...?> PI being on the second line
>  ... specifically: "Processing instruction target is xml".]
>
> ...jsled
>
> --
> http://www.asynchronous.org - `a=jsled; b=asynchronous.org; echo ${a}@${b}`
>

Howdy,

I have a couple of programs which generate log files as a series of
simple xml expressions like this

<event>Something...</event>
<event>Something else...</event>

that are simply appended to a file.  Modifying these programs to output
XML expressions was easy as long as the semantics of simply appending
data was maintained but then the resulting file is not a valid XML
document as it does not contain a single root element.  Is there some
way I can work with these files using nxml-mode?  Is there an
xml-fragment schema that I could use or something similar?  At present
everything after the first element is treated as an error which is not
terribly useful.

Thanks!
-Eric

On Fri, 2004-01-02 at 23:37, tpc@... wrote:
> hi Josh,
>
> I went to the document again, deleted the </xsl:stylesheet> and noticed
> it does say "missing end tag," and only if you press Enter at the end of
> the last line do you get the red underscore, but if you backspace delete the
> newline then it disappears and just says "missing end tag," but as soon as
> you scroll to any other part of the file there is no indication that you
> are in need of an end stylesheet tag.

It will still say "Invalid" in the mode-line.  You can click on
"Invalid" to go to the error and see what it is.  There's no red
underline, because, as Norm said, there is nothing following to
underline (and underlining the start-tag in the case would be difficult
to implement).

James

Norman Walsh <normyahoo@...> writes:

> Hmm, I've noticed the same thing, although I'd actually prefer:
>
>      <div tal:define="tabindex tabindex/next;
>                       error_workflow_action errors/workflow_action|nothing;
>                       objs request/ids|nothing;
>                       review_state_label string:No change;
>                       target python:test(objs, objs, here);"
>           tal:attributes="class
>                           python:test(error_workflow_action, 'field error',
'field')"
>           tal:condition="not:anonymous">

Here's a patch against nxml-mode-20031031 that does this.

I also changed the behavior of indentation for end tags so that only
end tags that lie on the beginning of a line dedent.  Thus, instead of
this kind of indentation:

<h1 tal:define="some_variable some_expression;
                 some_other_variable some_other_expression;"
tal:content="here/title_or_id">Title</h1>

I now get this:

<h1 tal:define="some_variable some_expression;
                 some_other_variable some_other_expression;"
     tal:content="here/title_or_id">Title</h1>

Cheers,

Eric


--- /tmp/nxml-mode.el.orig31139iId 2004-01-10 12:20:17.422328536 -0500
+++ /tmp/nxml-mode.el31139vSj 2004-01-10 12:20:17.424328232 -0500
@@ -1503,7 +1503,7 @@
  Return nil if the indent of the current line should not be changed."
    (nxml-ensure-scan-up-to-date)
    (let ((indent 0)
- token-end target-line-start absolute)
+ token-start token-end token-type target-line-start absolute)
    (save-excursion
      (cond (;; First line: indent 0
 	    (save-excursion
@@ -1511,18 +1511,18 @@
 	      (eq (point) (point-min)))
 	    (setq indent 0)
 	    (setq absolute t))
-   (;; End-tag at the end of a line
+   (;; End-tag at the beginning of a line
 	    ;; If corresponding start-tag not too far away,
 	    ;; and at the start of its line, then use indentation
 	    ;; of start-tag.
 	    (progn
 	      (back-to-indentation)
-      (setq target-line-start (point))
-      (let ((inhibit-field-text-motion t))
-        (end-of-line))
-      (skip-chars-backward " \t")
-      (and (eq (nxml-token-before) (point))
- 	  (memq xmltok-type '(end-tag partial-end-tag))
+      (setq target-line-start (point)
+                   token-end (nxml-token-after)
+                   token-start xmltok-start
+                   token-type xmltok-type)
+             (goto-char token-end)
+      (and (memq token-type '(end-tag partial-end-tag))
 		   (nxml-scan-element-backward
 		    (point)
 		    nil
@@ -1538,9 +1538,8 @@
 	   ;; Use nxml-child-indent less than normal
 	   ((progn
 	      (goto-char target-line-start)
-      (setq token-end (nxml-token-after))
-      (and (eq xmltok-start (point))
- 	  (memq xmltok-type '(end-tag partial-end-tag))
+      (and (eq token-start (point))
+ 	  (memq token-type '(end-tag partial-end-tag))
 		   (save-excursion
 		     (goto-char token-end)
 		     (nxml-indent-at-end-of-line-p))))
@@ -1548,11 +1547,47 @@
 	    (setq indent (- nxml-child-indent)))
 	   ;; Comment close on its own line
 	   ;; Indent relative to comment open
-   ((and (eq xmltok-type 'comment)
+   ((and (eq token-type 'comment)
 		 (eq token-end (+ target-line-start 3)))
-    (goto-char xmltok-start)
+    (goto-char token-start)
 	    (setq indent (current-column))
-    (setq absolute t)))
+    (setq absolute t))
+          ;; Inside a multi-line tag
+          ((progn
+             (goto-char target-line-start)
+             (skip-chars-backward " \t\n\r")
+             (setq token-end (nxml-token-before))
+             (or (and (memq xmltok-type '(start-tag empty-element))
+                      (>= token-end target-line-start))
+                 (memq xmltok-type '(partial-empty-element
partial-start-tag))))
+           (let ((att (nxml-find-preceding-attribute))
+                 name-start value-start value-end)
+             (if att
+                 (progn
+                   (setq name-start (xmltok-attribute-name-start att))
+                   (setq value-start (xmltok-attribute-value-start att))
+                   (setq value-end (xmltok-attribute-value-end att))))
+             (cond (;; Inside a partial attribute value.
+                    (not value-end)
+                    (save-excursion
+                      (search-backward "\"" name-start nil)
+                      (setq indent (1+ (current-column)))))
+                   ;; Inside a complete attribute value
+                   ((<= target-line-start value-end)
+                    (save-excursion
+                      (goto-char value-start)
+                      (setq indent (current-column))))
+                   ;; Not in an attribute value.
+                   (t
+                    (setq indent
+                          (or (save-excursion
+                                (goto-char xmltok-start)
+                                (skip-chars-forward "^ \t\r\n")
+                                (skip-chars-forward " \t")
+                                (if (looking-at ".")
+                                    (current-column)))
+                              (+ (current-column) nxml-attribute-indent))))))
+           (setq absolute t)))
      (if absolute
 	 indent
        (skip-chars-backward " \r\n\t")
@@ -1578,31 +1613,6 @@
 		    (if (eq xmltok-type 'start-tag)
 		        nxml-child-indent
 		      0)))
-        ;; the second non-blank line of a multi-line tag
-        ((and (memq xmltok-type '(start-tag
- 				 empty-element
- 				 partial-empty-element
- 				 partial-start-tag))
- 	     (save-excursion
- 	       (goto-char xmltok-start)
- 	       (back-to-indentation)
- 	       (eq (point) xmltok-start))
- 	     (save-excursion
- 	       (goto-char target-line-start)
- 	       (skip-chars-backward " \t\r\n")
- 	       (back-to-indentation)
- 	       (eq (point) xmltok-start))
- 	     (<= target-line-start
- 		 (save-excursion
- 		   (goto-char token-end)
- 		   (skip-chars-forward " \t\r\n")
- 		   (point))))
-  (goto-char xmltok-start)
-  (or (save-excursion
- 	      (skip-chars-forward "^ \t\r\n")
- 	      (skip-chars-forward " \t")
- 	      (and (looking-at ".") (current-column)))
- 	    (+ (current-column) nxml-attribute-indent)))
 	        (;; second non-blank line of a multi-line comment
 		 (and (eq xmltok-type 'comment)
 		      (< target-line-start token-end)

On Sat, Jan 10, 2004 at 09:01:45PM -0500, Eric Mc Sween wrote:
| Here's a patch against nxml-mode-20031031 that does this.
|
| I also changed the behavior of indentation for end tags so that only
| end tags that lie on the beginning of a line dedent.  Thus, instead of
| this kind of indentation:
|
| <h1 tal:define="some_variable some_expression;
|                 some_other_variable some_other_expression;"
| tal:content="here/title_or_id">Title</h1>
|
| I now get this:
|
| <h1 tal:define="some_variable some_expression;
|                 some_other_variable some_other_expression;"
|     tal:content="here/title_or_id">Title</h1>

Sweet! It worked like a charm for me. I applied the patch to the
debian package and recompiled and now I'm happy again :) Can we get
this patch included in the next release?

--
Sidnei da Silva <sidnei@...>
http://awkly.org - dreamcatching :: making your dreams come true
http://plone.org/about/team#dreamcatcher

Linux is addictive, I'm hooked!
	 -- MaDsen Wikholm's .sig

| Sweet! It worked like a charm for me. I applied the patch to the
| debian package and recompiled and now I'm happy again :) Can we get
| this patch included in the next release?

Ugh. Not so fast :(

It seems to have broken identation of stuff like:

<configure
   xmlns="http://namespaces.zope.org/zope">

   <permission
     id="sqlobjectsupport.AddContent"
     title="[add-sample-permission] sqlobjectsupport - Add Content"
     />

   <grant
     permission="sqlobjectsupport.AddContent"
     role="zope.Manager" />

</configure>

Gets idented as:

<configure
   xmlns="http://namespaces.zope.org/zope">

   <permission
                                          id="sqlobjectsupport.AddContent"
                                                                           
title=\
"[add-sample-permission] sqlobjectsupport - Add Content"
                                                                                 
\
                                                           />

   <grant
                                                                                 
\
                                                        
permission="sqlobjectsupp\
ort.AddContent"
                                                                                 
\
                                                                                 
\
                  role="zope.Manager" />

</configure>


(I hope you can get the idea)

Also, if I press 'TAB' on the second line (xmlns:...) I get:

Search failed: "\""

on the minibuffer.

Hope that helps.

--
Sidnei da Silva <sidnei@...>
http://awkly.org - dreamcatching :: making your dreams come true
http://plone.org/about/team#dreamcatcher

If at first you don't succeed, you must be a programmer.

Hi,
I am trying to install nxml/emacs on my sons computer.
Try to download emacs but I can't find emacs 21 for windows anywhere.

Any idea where I can find a win version?
Thanks
Aaron

On Thu, Jan 15, 2004 at 08:23:36PM +0200, Aaron wrote:
| Hi,
| I am trying to install nxml/emacs on my sons computer.
| Try to download emacs but I can't find emacs 21 for windows anywhere.

I think it was removed from gnu.org ftp some time ago, because they
felt like it could have been trojaned. I dont know of any mirrors that
have it available. Maybe mail someone at gnu.org?

--
Sidnei da Silva <sidnei@...>
http://awkly.org - dreamcatching :: making your dreams come true
http://plone.org/about/team#dreamcatcher

Hackers are just a migratory lifeform with a tropism for computers.

Sidnei da Silva <sidnei@...> writes:

> It seems to have broken identation of stuff like:
>
> <configure
>   xmlns="http://namespaces.zope.org/zope">
>
>   <permission
>     id="sqlobjectsupport.AddContent"
>     title="[add-sample-permission] sqlobjectsupport - Add Content"
>     />
>
>   <grant
>     permission="sqlobjectsupport.AddContent"
>     role="zope.Manager" />
>
> </configure>
>
> Gets idented as:
>

[ snip example of bad indentation ]

Right.  Here's a fix.  This is still a patch against
nxml-mode-20031031.

There is another problem I discovered:

This:

   Some text
   <a href="..."><img src="..." alt="..."
                      tal:condition="..." /></a>
   Some other text
   And yet another line

gets indented like this:

   Some text
   <a href="..."><img src="..." alt="..."
                      tal:condition="..." /></a>
                      Some other text
                      And yet another line

I'll probably fix this later as well as I have grown very fond of nxml
after a couple of weeks of usage.

So here's the updated patch:

--- /tmp/nxml-mode.el.orig31837RDQ 2004-01-15 14:09:35.005799152 -0500
+++ /tmp/nxml-mode.el31837eNW 2004-01-15 14:09:35.017797328 -0500
@@ -1503,7 +1503,7 @@
  Return nil if the indent of the current line should not be changed."
    (nxml-ensure-scan-up-to-date)
    (let ((indent 0)
- token-end target-line-start absolute)
+ token-start token-end token-type target-line-start absolute)
    (save-excursion
      (cond (;; First line: indent 0
 	    (save-excursion
@@ -1511,18 +1511,18 @@
 	      (eq (point) (point-min)))
 	    (setq indent 0)
 	    (setq absolute t))
-   (;; End-tag at the end of a line
+   (;; End-tag at the beginning of a line
 	    ;; If corresponding start-tag not too far away,
 	    ;; and at the start of its line, then use indentation
 	    ;; of start-tag.
 	    (progn
 	      (back-to-indentation)
-      (setq target-line-start (point))
-      (let ((inhibit-field-text-motion t))
-        (end-of-line))
-      (skip-chars-backward " \t")
-      (and (eq (nxml-token-before) (point))
- 	  (memq xmltok-type '(end-tag partial-end-tag))
+      (setq target-line-start (point)
+                   token-end (nxml-token-after)
+                   token-start xmltok-start
+                   token-type xmltok-type)
+             (goto-char token-end)
+      (and (memq token-type '(end-tag partial-end-tag))
 		   (nxml-scan-element-backward
 		    (point)
 		    nil
@@ -1538,9 +1538,8 @@
 	   ;; Use nxml-child-indent less than normal
 	   ((progn
 	      (goto-char target-line-start)
-      (setq token-end (nxml-token-after))
-      (and (eq xmltok-start (point))
- 	  (memq xmltok-type '(end-tag partial-end-tag))
+      (and (eq token-start (point))
+ 	  (memq token-type '(end-tag partial-end-tag))
 		   (save-excursion
 		     (goto-char token-end)
 		     (nxml-indent-at-end-of-line-p))))
@@ -1548,11 +1547,46 @@
 	    (setq indent (- nxml-child-indent)))
 	   ;; Comment close on its own line
 	   ;; Indent relative to comment open
-   ((and (eq xmltok-type 'comment)
+   ((and (eq token-type 'comment)
 		 (eq token-end (+ target-line-start 3)))
-    (goto-char xmltok-start)
+    (goto-char token-start)
 	    (setq indent (current-column))
-    (setq absolute t)))
+    (setq absolute t))
+          ;; Inside a multi-line tag
+          ((progn
+             (goto-char target-line-start)
+             (skip-chars-backward " \t\n\r")
+             (setq token-end (nxml-token-before))
+             (or (and (memq xmltok-type '(start-tag empty-element))
+                      (>= token-end target-line-start))
+                 (memq xmltok-type '(partial-empty-element
partial-start-tag))))
+           (let ((att (nxml-find-preceding-attribute))
+                 name-start value-start value-end)
+             (when att
+               (setq name-start (xmltok-attribute-name-start att))
+               (setq value-start (xmltok-attribute-value-start att))
+               (setq value-end (xmltok-attribute-value-end att)))
+             (cond (;; Inside a partial attribute value.
+                    (and value-start (not value-end))
+                    (save-excursion
+                      (search-backward "\"" name-start nil)
+                      (setq indent (1+ (current-column)))))
+                   ;; Inside a complete attribute value
+                   ((and value-start (<= target-line-start value-end))
+                    (save-excursion
+                      (goto-char value-start)
+                      (setq indent (current-column))))
+                   ;; Not in an attribute value.
+                   (t
+                    (goto-char xmltok-start)
+                    (setq indent
+                          (or (save-excursion
+                                (skip-chars-forward "^ \t\r\n")
+                                (skip-chars-forward " \t")
+                                (if (looking-at ".")
+                                    (current-column)))
+                              (+ (current-column) nxml-attribute-indent))))))
+           (setq absolute t)))
      (if absolute
 	 indent
        (skip-chars-backward " \r\n\t")
@@ -1578,31 +1612,6 @@
 		    (if (eq xmltok-type 'start-tag)
 		        nxml-child-indent
 		      0)))
-        ;; the second non-blank line of a multi-line tag
-        ((and (memq xmltok-type '(start-tag
- 				 empty-element
- 				 partial-empty-element
- 				 partial-start-tag))
- 	     (save-excursion
- 	       (goto-char xmltok-start)
- 	       (back-to-indentation)
- 	       (eq (point) xmltok-start))
- 	     (save-excursion
- 	       (goto-char target-line-start)
- 	       (skip-chars-backward " \t\r\n")
- 	       (back-to-indentation)
- 	       (eq (point) xmltok-start))
- 	     (<= target-line-start
- 		 (save-excursion
- 		   (goto-char token-end)
- 		   (skip-chars-forward " \t\r\n")
- 		   (point))))
-  (goto-char xmltok-start)
-  (or (save-excursion
- 	      (skip-chars-forward "^ \t\r\n")
- 	      (skip-chars-forward " \t")
- 	      (and (looking-at ".") (current-column)))
- 	    (+ (current-column) nxml-attribute-indent)))
 	        (;; second non-blank line of a multi-line comment
 		 (and (eq xmltok-type 'comment)
 		      (< target-line-start token-end)

Aaron wrote:

>I am trying to install nxml/emacs on my sons computer.
>Try to download emacs but I can't find emacs 21 for windows anywhere.
>
>
>
http://www.tei-c.org/Software/tei-emacs has a complete emacs for Win32
setup,
with nxml all working. The normal distribution of Emacs seems to be
still wrecked.

Sebastian Rahtz

Hi,

Here is probably an illustration of the issue mentioned in the TODO
"Should completion pay attention to characters after point?  If so, how?"

After having stumbled several times on the following behaviour, my
answer to the first question is yes. I've unfortunately no answer to
the second one.

Let a test schema be :

   start = element test {
      attribute foo { text }
    |
      attribute bar { text }
    |
      element subtest { text }
    |
      text
   }

Documents recognised by this schema consist of one <test> element
containing either a foo attribute, or a bar attribute, or a subtest
element, or a text node.

Let's edit the following text with nxml,

   <test foo="foovalue" -|-

As expected, pressing C-Return doesn't mention bar as a possible
child attribute for test; ditto with this configuration:

   <test bar="barvalue" -|-

This feature of hiding invalid attributes before we even think of
adding them is of course very useful.

Now, if I edit this :

   <test -|-><subtest/></test>

or this :

   <test -|->Shouldn't I be the only one?</test>

I'd expect that nxml would hide both foo and bar so that I'm not
tempted to add them. Instead, it offers them for completion, only to
promptly underline whatever choice is made.

Xavier.

DuCharme, Bob (LNG-CHO) wrote:

>
> Which release of Emacs is the Win32 one?
>


21.3

The package is as uptodate as I can make it, but there are probably
flaws still.
It does all the XML/SGML tasks I can think of, and has all the utilities
I can
realistically provide. Why, it even has a copy of David's excellent
"rnv" included....

Sebastian

Thanks
I grabbed a copy and will install it tomorrow
Aaron

>
> >
> >
> http://www.tei-c.org/Software/tei-emacs has a complete emacs for Win32
> setup,
> with nxml all working. The normal distribution of Emacs seems to be
> still wrecked.
>
> Sebastian Rahtz
>
>
> ------------------------------------------------------------------------
> *Yahoo! Groups Links*
>
>     * To visit your group on the web, go to:
>       http://groups.yahoo.com/group/emacs-nxml-mode/
>
>     * To unsubscribe from this group, send an email to:
>       emacs-nxml-mode-unsubscribe@yahoogroups.com
>       <mailto:emacs-nxml-mode-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>
>     * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>       Service <http://docs.yahoo.com/info/terms/>.
>
>
>
> ------------------------------------------------------------------------
> *Yahoo! Groups Links*
>
>     * To visit your group on the web, go to:
>       http://groups.yahoo.com/group/emacs-nxml-mode/
>
>     * To unsubscribe from this group, send an email to:
>       emacs-nxml-mode-unsubscribe@yahoogroups.com
>       <mailto:emacs-nxml-mode-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>
>     * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>       Service <http://docs.yahoo.com/info/terms/>.
>
>

Hi,

I just installed nXML-mode on emacs 21.3 on SuSE Linux.  It seems to
be working well, except that syntax highlighting does not work with
the X version of emacs.  If I run emacs with the nw flag, syntax
highlighting works.  Is there anything special I have to do?

Thanks,
Victor Cardona

On Jan 19, 2004, at 12:47 AM, pug_henry wrote:

> It seems to be working well, except that syntax highlighting does not
> work with the X version of emacs. If I run emacs with the nw flag,
> syntax highlighting works. Is there anything special I have to do?

I'm pretty sure the docs explain nxml mode is only compatible with gnu
emacs.

Bruce

Bruce D'Arcus:
>
> On Jan 19, 2004, at 12:47 AM, pug_henry wrote:
>
> > It seems to be working well, except that syntax highlighting does not
> > work with the X version of emacs. If I run emacs with the nw flag,
> > syntax highlighting works. Is there anything special I have to do?
>
> I'm pretty sure the docs explain nxml mode is only compatible with gnu
> emacs.

I'm not sure but am guessing that the original poster is asking about
GNU Emacs (nxml work would not work well under XEmacs). X version of
Emacs is not XEmacs, it is GNU Emacs opening a separate window. nw is a
command-line
option to run it in a terminal window.

David Tolpin

--- In emacs-nxml-mode@yahoogroups.com, Bruce D'Arcus <bdarcus@f...>
wrote:
>
> On Jan 19, 2004, at 12:47 AM, pug_henry wrote:
>
> > It seems to be working well, except that syntax highlighting does not
> > work with the X version of emacs. If I run emacs with the nw flag,
> > syntax highlighting works. Is there anything special I have to do?
>
> I'm pretty sure the docs explain nxml mode is only compatible with gnu
> emacs.
>
> Bruce

I was referring to GNU emacs that runs as an X-window client. Not in a
terminal.

Victor

Hi,
I am writing an xhtml doc and I need to add the xmlns but can't remeber
the syntax or find it quickly.
could some send me the header stuff I need for a xhtml doc.

Thanks
Aaron

nevermind I found it
Thanks
Aaron

On Jan 19, 2004, at 6:00 PM, Aaron wrote:

> I am writing an xhtml doc and I need to add the xmlns but can't remeber
> the syntax or find it quickly.

Note that nxml will do completion for required namespace attribute
values.

Bruce

Hi all,
I was once using nxml and some keycombo gave me a list of the
keybindings in a buffer below the document I had opened.
I have never been able to find it again.

Any ideas?
Thanks
Aaron


Aa

On Tue, 20 Jan 2004, aamehl@... wrote:

> I was once using nxml and some keycombo gave me a list of the
> keybindings in a buffer below the document I had opened.
> I have never been able to find it again.

,----[ C-h k C-h m ]
| C-h m runs the command describe-mode
|    which is an interactive compiled Lisp function in `help'.
| (describe-mode)
|
| Display documentation of current major mode and minor modes.
| The major mode description comes first, followed by the minor modes,
| each on a separate page.
|
| For this to work correctly for a minor mode, the mode's indicator variable
| (listed in `minor-mode-alist') must also be a function whose documentation
| describes the minor mode.
`----


--
Regards,

joe
Joe Casadonte
jcasadonte@...

------------------------------------------------------------------------------
          Llama Fresh Farms => http://www.northbound-train.com
    Gay Media Resource List => http://www.northbound-train.com/gaymedia.html
             Perl for Win32 => http://www.northbound-train.com/perlwin32.html
                Emacs Stuff => http://www.northbound-train.com/emacs.html
           Music CD Trading => http://www.northbound-train.com/cdr.html
------------------------------------------------------------------------------
                        Live Free, that's the message!
------------------------------------------------------------------------------

Victor,

--- In emacs-nxml-mode@yahoogroups.com, "pug_henry" <pug_henry@y...>
wrote:
> Hi,
>
> I just installed nXML-mode on emacs 21.3 on SuSE Linux.  It seems to
> be working well, except that syntax highlighting does not work with
> the X version of emacs.  If I run emacs with the nw flag, syntax
> highlighting works.  Is there anything special I have to do?

I recently set a dark background in emacs, after that syntax
highlighting in nxml mode didn't work any more.
(I think this is because nxml mode only defines colors for light
background settings).
If this is the case, you can try setting colors via customize.
(nxml-delimited-data-face,nxml-name-face,nxml-ref-face and
nxml-delimiter-face should be enough to start)

lg,
     tom

On Mon, Jan 19, 2004 at 08:14:03PM -0500, Joe Casadonte spake thus:
> On Tue, 20 Jan 2004, aamehl@... wrote:
>
> > I was once using nxml and some keycombo gave me a list of the
> > keybindings in a buffer below the document I had opened.
> > I have never been able to find it again.
>
> ,----[ C-h k C-h m ]
> | C-h m runs the command describe-mode
> |    which is an interactive compiled Lisp function in `help'.
> | (describe-mode)
> |
> | Display documentation of current major mode and minor modes.
> | The major mode description comes first, followed by the minor modes,
> | each on a separate page.
> |
> | For this to work correctly for a minor mode, the mode's indicator variable
> | (listed in `minor-mode-alist') must also be a function whose documentation
> | describes the minor mode.
> `----

C-h b runs the command describe-bindings
    which is an interactive compiled Lisp function in `help'.
    (describe-bindings &optional PREFIX BUFFER)

    Show a list of all defined keys, and their definitions.
    We put that list in a buffer, and display the buffer.

    The optional argument PREFIX, if non-nil, should be a key sequence;
    then we display only bindings that start with that prefix.
    The optional argument BUFFER specifies which buffer's bindings
    to display (default, the current buffer).

--
a l a n   d.   s a l e w s k i             salewski@...
--------------------------------------------------------------------
   We have written an amazingly easy-to-use virtual-reality-based
                               suite.
--------------------------------------------------------------------
Generated from WWW Marketing Phrase gizmo:   www.lyra.org/phrase.cgi

I am using nxml-mode on GNU-Emacs 21.3.1, and it is complaining about
MULE-UCS.  Can someone tell me how I can disable MULE-UCS?

Thanks,
Victor