emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] emacs-26 10bd3b3: Improve word motion docs (Bug#30815)


From: Noam Postavsky
Subject: [Emacs-diffs] emacs-26 10bd3b3: Improve word motion docs (Bug#30815)
Date: Fri, 16 Mar 2018 21:04:47 -0400 (EDT)

branch: emacs-26
commit 10bd3b3af8acfc226acadc654298865cffc19cc9
Author: Noam Postavsky <address@hidden>
Commit: Noam Postavsky <address@hidden>

    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.
---
 doc/lispref/positions.texi |  2 +-
 lisp/simple.el             | 12 +++++++-----
 src/syntax.c               |  9 +++++----
 3 files changed, 13 insertions(+), 10 deletions(-)

diff --git a/doc/lispref/positions.texi b/doc/lispref/positions.texi
index 0a03e24..fdc8bb9 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
address@hidden), also define a word boundary
address@hidden), 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 b7ad6eb..d8abeb3 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 3780646..e543255 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;



reply via email to

[Prev in Thread] Current Thread [Next in Thread]