summaryrefslogtreecommitdiff
path: root/lisp/nxml
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2018-04-01 12:45:37 +0300
committerEli Zaretskii <eliz@gnu.org>2018-04-01 12:45:37 +0300
commitf759c5cfe4651af5f64fac2492fa362f8d383bd5 (patch)
tree19577f2308aa42dc05a052354334eca0a595d8d8 /lisp/nxml
parent02e4b05c9d274e278581e811a4e935f922db402b (diff)
downloademacs-f759c5cfe4651af5f64fac2492fa362f8d383bd5.tar.gz
Followup to last change
* etc/NEWS: Mark nxml-sexp-element-flag entry as not needing documentation updates. * lisp/nxml/nxml-mode.el (nxml-mode, nxml-forward-balanced-item): Doc fixes.
Diffstat (limited to 'lisp/nxml')
-rw-r--r--lisp/nxml/nxml-mode.el32
1 files changed, 16 insertions, 16 deletions
diff --git a/lisp/nxml/nxml-mode.el b/lisp/nxml/nxml-mode.el
index 554b5acfb20..a9298be4fb4 100644
--- a/lisp/nxml/nxml-mode.el
+++ b/lisp/nxml/nxml-mode.el
@@ -471,11 +471,10 @@ The Emacs commands that normally operate on balanced expressions will
operate on XML markup items. Thus \\[forward-sexp] will move forward
across one markup item; \\[backward-sexp] will move backward across
one markup item; \\[kill-sexp] will kill the following markup item;
-\\[mark-sexp] will mark the following markup item. By default, each
-tag each treated as a single markup item; to make the complete element
-be treated as a single markup item, set the variable
-`nxml-sexp-element-flag' to t. For more details, see the function
-`nxml-forward-balanced-item'.
+\\[mark-sexp] will mark the following markup item. By default, the
+complete element is treated as a single markup item; to make each tag be
+treated as a separate markup item, set the variable `nxml-sexp-element-flag'
+to nil. For more details, see the function `nxml-forward-balanced-item'.
\\[nxml-backward-up-element] and \\[nxml-down-element] move up and down the element structure.
@@ -1510,17 +1509,18 @@ With ARG, do it that many times. Negative arg -N means
move backward across N balanced expressions.
This is the equivalent of `forward-sexp' for XML.
-An element contains as items strings with no markup, tags, processing
-instructions, comments, CDATA sections, entity references and
-characters references. However, if the variable
-`nxml-sexp-element-flag' is non-nil, then an element is treated as a
-single markup item. A start-tag contains an element name followed by
-one or more attributes. An end-tag contains just an element name.
-An attribute value literals contains strings with no markup, entity
-references and character references. A processing instruction
-consists of a target and a content string. A comment or a CDATA
-section contains a single string. An entity reference contains a
-single name. A character reference contains a character number."
+An element is by default treated as a single markup item.
+However, if the variable `nxml-sexp-element-flag' is nil, then an
+element contains as items strings with no markup, tags,
+processing instructions, comments, CDATA sections, entity
+references and character references. A start-tag contains an
+element name followed by one or more attributes. An end-tag
+contains just an element name. An attribute value literals
+contains strings with no markup, entity references and character
+references. A processing instruction consists of a target and a
+content string. A comment or a CDATA section contains a single
+string. An entity reference contains a single name. A character
+reference contains a character number."
(interactive "^p")
(or arg (setq arg 1))
(cond ((> arg 0)