Document char-script-table's effect on word motion
* doc/lispref/positions.texi (Word Motion): Talk about char-script-table (Bug #10494).
This commit is contained in:
parent
e9ff4857cb
commit
8342e7481a
1 changed files with 10 additions and 7 deletions
|
@ -192,8 +192,9 @@ in the opposite direction.
|
||||||
@subsection Motion by Words
|
@subsection Motion by Words
|
||||||
|
|
||||||
The functions for parsing words described below use the syntax table
|
The functions for parsing words described below use the syntax table
|
||||||
to decide whether a given character is part of a word. @xref{Syntax
|
and @code{char-script-table} to decide whether a given character is
|
||||||
Tables}.
|
part of a word. @xref{Syntax Tables}, and see @ref{Character
|
||||||
|
Properties}.
|
||||||
|
|
||||||
@deffn Command forward-word &optional count
|
@deffn Command forward-word &optional count
|
||||||
This function moves point forward @var{count} words (or backward if
|
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
|
that begin and end words, known as @dfn{word boundaries}, are defined
|
||||||
by the current buffer's syntax table (@pxref{Syntax Class Table}), but
|
by the current buffer's syntax table (@pxref{Syntax Class Table}), but
|
||||||
modes can override that by setting up a suitable
|
modes can override that by setting up a suitable
|
||||||
@code{find-word-boundary-function-table}, described below. In any
|
@code{find-word-boundary-function-table}, described below. Characters
|
||||||
case, this function cannot move point past the boundary of the
|
that belong to different scripts (as defined by
|
||||||
accessible portion of the buffer, or across a field boundary
|
@code{char-syntax-table}), also define a word boundary
|
||||||
(@pxref{Fields}). The most common case of a field boundary is the end
|
(@pxref{Character Properties}). In any case, this function cannot
|
||||||
of the prompt in the minibuffer.
|
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
|
If it is possible to move @var{count} words, without being stopped
|
||||||
prematurely by the buffer boundary or a field boundary, the value is
|
prematurely by the buffer boundary or a field boundary, the value is
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue