summaryrefslogtreecommitdiff
path: root/lisp/simple.el
diff options
context:
space:
mode:
authorNoam Postavsky <npostavs@gmail.com>2018-03-13 22:17:43 -0400
committerNoam Postavsky <npostavs@gmail.com>2018-03-16 19:51:28 -0400
commit10bd3b3af8acfc226acadc654298865cffc19cc9 (patch)
tree7ef51cc5e2e671b415984365c9cfa93d374d72da /lisp/simple.el
parent2b8507fbdce8228ccdbcbc31fe545a50330ddd51 (diff)
downloademacs-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.
Diffstat (limited to 'lisp/simple.el')
-rw-r--r--lisp/simple.el12
1 files changed, 7 insertions, 5 deletions
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))))