summaryrefslogtreecommitdiff
path: root/doc/lispref/positions.texi
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2016-08-22 14:38:49 -0700
committerPaul Eggert <eggert@cs.ucla.edu>2016-08-22 14:38:49 -0700
commit590dab5a68f4283d53ce79d4633fe1503131baea (patch)
tree2e2452d22d54826cb84e2c5dc976abbb2ed40322 /doc/lispref/positions.texi
parentcaa2770d1d79f9c8013d6dddcd9e86d05230b26d (diff)
parent8c2946e29b38fa3e0dff6b4d402ba0fda0e03c9b (diff)
downloademacs-590dab5a68f4283d53ce79d4633fe1503131baea.tar.gz
Merge from origin/emacs-25
8c2946e In NEWS describe new handling of window margins (Bug#24193) 0cee66c Facultatively ignore margins when splitting and resizing wind... 8d68147 Document CATEGORY arg to modify-category-entry 8342e74 Document char-script-table's effect on word motion e9ff485 Further fix for 'url-http-create-request' and multibyte strings 0695235 Fix docstring of eval-expression 98b01dd Clarify when 'cursor' property is in effect 75f1882 Convert the remaining strings to unibyte before concatenating d2db5dd Fix bug with handling the bidi cache ccd0e92 * doc/lispref/text.texi (Change Hooks): Minor copyedits. f785ff4 Clarify documentation of before/after-change-functions 3c9cb57 Document use of vectors in keymaps # Conflicts: # src/xdisp.c
Diffstat (limited to 'doc/lispref/positions.texi')
-rw-r--r--doc/lispref/positions.texi17
1 files changed, 10 insertions, 7 deletions
diff --git a/doc/lispref/positions.texi b/doc/lispref/positions.texi
index 796a06615ae..a56ab5ef307 100644
--- a/doc/lispref/positions.texi
+++ b/doc/lispref/positions.texi
@@ -192,8 +192,9 @@ in the opposite direction.
@subsection Motion by Words
The functions for parsing words described below use the syntax table
-to decide whether a given character is part of a word. @xref{Syntax
-Tables}.
+and @code{char-script-table} to decide whether a given character is
+part of a word. @xref{Syntax Tables}, and see @ref{Character
+Properties}.
@deffn Command forward-word &optional count
This function moves point forward @var{count} words (or backward if
@@ -207,11 +208,13 @@ and then continue moving until the word ends. By default, characters
that begin and end words, known as @dfn{word boundaries}, are defined
by the current buffer's syntax table (@pxref{Syntax Class Table}), but
modes can override that by setting up a suitable
-@code{find-word-boundary-function-table}, described below. In any
-case, this function cannot move point past the boundary of the
-accessible portion of the buffer, or across a field boundary
-(@pxref{Fields}). The most common case of a field boundary is the end
-of the prompt in the minibuffer.
+@code{find-word-boundary-function-table}, described below. Characters
+that belong to different scripts (as defined by
+@code{char-syntax-table}), also define a word boundary
+(@pxref{Character Properties}). In any case, this function cannot
+move point past the boundary of the accessible portion of the buffer,
+or across a field boundary (@pxref{Fields}). The most common case of
+a field boundary is the end of the prompt in the minibuffer.
If it is possible to move @var{count} words, without being stopped
prematurely by the buffer boundary or a field boundary, the value is