diff options
author | Noam Postavsky <npostavs@gmail.com> | 2018-03-13 22:17:43 -0400 |
---|---|---|
committer | Noam Postavsky <npostavs@gmail.com> | 2018-03-16 19:51:28 -0400 |
commit | 10bd3b3af8acfc226acadc654298865cffc19cc9 (patch) | |
tree | 7ef51cc5e2e671b415984365c9cfa93d374d72da | |
parent | 2b8507fbdce8228ccdbcbc31fe545a50330ddd51 (diff) | |
download | emacs-10bd3b3af8acfc226acadc654298865cffc19cc9.tar.gz |
Improve word motion docs (Bug#30815)
* doc/lispref/positions.texi (Word Motion): Fix reference to
`char-script-table'.
* lisp/simple.el (backward-word):
* src/syntax.c (forward-word): Mention `char-script-table' and add
link to the 'Word Motion' manual section.
-rw-r--r-- | doc/lispref/positions.texi | 2 | ||||
-rw-r--r-- | lisp/simple.el | 12 | ||||
-rw-r--r-- | src/syntax.c | 9 |
3 files changed, 13 insertions, 10 deletions
diff --git a/doc/lispref/positions.texi b/doc/lispref/positions.texi index 0a03e246c01..fdc8bb96ae9 100644 --- a/doc/lispref/positions.texi +++ b/doc/lispref/positions.texi @@ -210,7 +210,7 @@ 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. Characters that belong to different scripts (as defined by -@code{char-syntax-table}), also define a word boundary +@code{char-script-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 diff --git a/lisp/simple.el b/lisp/simple.el index b7ad6ebd799..d8abeb30004 100644 --- a/lisp/simple.el +++ b/lisp/simple.el @@ -7027,11 +7027,13 @@ current object." With argument ARG, do this that many times. If ARG is omitted or nil, move point backward one word. -The word boundaries are normally determined by the buffer's syntax -table, but `find-word-boundary-function-table', such as set up -by `subword-mode', can change that. If a Lisp program needs to -move by words determined strictly by the syntax table, it should -use `backward-word-strictly' instead." +The word boundaries are normally determined by the buffer's +syntax table and character script (according to +`char-script-table'), but `find-word-boundary-function-table', +such as set up by `subword-mode', can change that. If a Lisp +program needs to move by words determined strictly by the syntax +table, it should use `backward-word-strictly' instead. See Info +node `(elisp) Word Motion' for details." (interactive "^p") (forward-word (- (or arg 1)))) diff --git a/src/syntax.c b/src/syntax.c index 378064611cc..e54325589f3 100644 --- a/src/syntax.c +++ b/src/syntax.c @@ -1552,10 +1552,11 @@ left there and the function returns nil. Field boundaries are not noticed if `inhibit-field-text-motion' is non-nil. The word boundaries are normally determined by the buffer's syntax -table, but `find-word-boundary-function-table', such as set up -by `subword-mode', can change that. If a Lisp program needs to -move by words determined strictly by the syntax table, it should -use `forward-word-strictly' instead. */) +table and character script (according to `char-script-table'), but +`find-word-boundary-function-table', such as set up by `subword-mode', +can change that. If a Lisp program needs to move by words determined +strictly by the syntax table, it should use `forward-word-strictly' +instead. See Info node `(elisp) Word Motion' for details. */) (Lisp_Object arg) { Lisp_Object tmp; |