From: Eli Zaretskii <eliz@gnu.org>
Date: Sat, 4 Nov 2023 15:46:27 +0000 (+0200)
Subject: ; * lisp/bindings.el (right-word, left-word): Doc fix.
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=18e2de1bec9c2d49a9d7352db04b44deeea6a22b;p=emacs.git

; * lisp/bindings.el (right-word, left-word): Doc fix.
---

diff --git a/lisp/bindings.el b/lisp/bindings.el
index e118fa1a35c..084e3a2060c 100644
--- a/lisp/bindings.el
+++ b/lisp/bindings.el
@@ -942,6 +942,14 @@ or backward in the buffer.  This is in contrast with \\[forward-word]
 and \\[backward-word], which see.
 
 Value is normally t.
+
+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 `forward-word-strictly'
+instead.  See Info node `(elisp) Word Motion' for details.
+
 If an edge of the buffer or a field boundary is reached, point is left there
 and the function returns nil.  Field boundaries are not noticed
 if `inhibit-field-text-motion' is non-nil."
@@ -958,6 +966,14 @@ or forward in the buffer.  This is in contrast with \\[backward-word]
 and \\[forward-word], which see.
 
 Value is normally t.
+
+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 `forward-word-strictly'
+instead.  See Info node `(elisp) Word Motion' for details.
+
 If an edge of the buffer or a field boundary is reached, point is left there
 and the function returns nil.  Field boundaries are not noticed
 if `inhibit-field-text-motion' is non-nil."