[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#10494: 24.0.92; Syntax table and non-ASCII character interaction
From: |
npostavs |
Subject: |
bug#10494: 24.0.92; Syntax table and non-ASCII character interaction |
Date: |
Fri, 12 Aug 2016 18:37:56 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Eli Zaretskii <eliz@gnu.org> writes:
> Indeed. This is a feature:
Ah, so doing
(modify-syntax-entry ?’ "w" text-mode-syntax-table)
(aset char-script-table ?’ 'latin)
does let word motion skip over ’ as OP wanted.
>
> Maybe we should document this somewhere, like the ELisp manual.
`(elisp) Word Motion' looks like a good place for it:
>From 03dbee2bf6bae29b21ea36ff3d73bce773458f78 Mon Sep 17 00:00:00 2001
From: Noam Postavsky <npostavs@gmail.com>
Date: Fri, 12 Aug 2016 18:33:17 -0400
Subject: [PATCH v1] Document char-script-table's effect on word motion
* doc/lispref/positions.texi (Word Motion): Talk about
char-script-table (Bug #10494).
---
doc/lispref/positions.texi | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/doc/lispref/positions.texi b/doc/lispref/positions.texi
index 1d748b8..3359ced 100644
--- a/doc/lispref/positions.texi
+++ b/doc/lispref/positions.texi
@@ -192,8 +192,8 @@ Word Motion
@subsection Motion by Words
The functions for parsing words described below use the syntax table
-to decide whether a given character is part of a word. @xref{Syntax
-Tables}.
+and @code{char-script-table} to decide whether a given character is
+part of a word. @xref{Syntax Tables} and @xref{Character Properties}.
@deffn Command forward-word &optional count
This function moves point forward @var{count} words (or backward if
@@ -207,11 +207,13 @@ Word Motion
that begin and end words, known as @dfn{word boundaries}, are defined
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. 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 a field boundary is the end
-of the prompt in the minibuffer.
+@code{find-word-boundary-function-table}, described below. Characters
+that belong to a different script (as defined by
+@code{char-syntax-table}), also mark 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 a field boundary
+is the end of the prompt in the minibuffer.
If it is possible to move @var{count} words, without being stopped
prematurely by the buffer boundary or a field boundary, the value is
--
2.9.2
- bug#10494: 24.0.92; Syntax table and non-ASCII character interaction, npostavs, 2016/08/10
- bug#10494: 24.0.92; Syntax table and non-ASCII character interaction, Eli Zaretskii, 2016/08/11
- bug#10494: 24.0.92; Syntax table and non-ASCII character interaction,
npostavs <=
- bug#10494: 24.0.92; Syntax table and non-ASCII character interaction, Eli Zaretskii, 2016/08/13
- bug#10494: 24.0.92; Syntax table and non-ASCII character interaction, npostavs, 2016/08/13
- bug#10494: 24.0.92; Syntax table and non-ASCII character interaction, Eli Zaretskii, 2016/08/13
- bug#10494: 24.0.92; Syntax table and non-ASCII character interaction, npostavs, 2016/08/13
- bug#10494: 24.0.92; Syntax table and non-ASCII character interaction, Eli Zaretskii, 2016/08/13
- bug#10494: 24.0.92; Syntax table and non-ASCII character interaction, Eli Zaretskii, 2016/08/13
- bug#10494: 24.0.92; Syntax table and non-ASCII character interaction, npostavs, 2016/08/13
- bug#10494: 24.0.92; Syntax table and non-ASCII character interaction, Eli Zaretskii, 2016/08/13
- bug#10494: 24.0.92; Syntax table and non-ASCII character interaction, npostavs, 2016/08/13
- bug#10494: 24.0.92; Syntax table and non-ASCII character interaction, Eli Zaretskii, 2016/08/13