[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: |
Sat, 13 Aug 2016 14:14:49 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Eli Zaretskii <eliz@gnu.org> writes:
>> From: npostavs@users.sourceforge.net
>> Cc: 10494@debbugs.gnu.org, aaronecay@gmail.com
>> Date: Sat, 13 Aug 2016 10:19:34 -0400
>>
>> >> (modify-syntax-entry ?’ "w" text-mode-syntax-table)
>> >> (defconst my-text-char-script-table
>> >> (let ((table (copy-sequence char-script-table)))
>> >> (aset table ?’ 'latin)
>> >> table))
>> >>
>> >> (defun my-text-mode-hook ()
>> >> (set (make-local-variable 'char-script-table)
>> >> my-text-char-script-table))
>> >> (add-hook 'text-mode-hook 'my-text-mode-hook)
>> >
>> > Are you sure nothing in text-mode will ever want to use \s_ in any
>> > regexp?
>>
>> Did you mean \> (word boundary) or \s. (punctation)? \s_ doesn't match
>> ’ regardless because its syntax class is punctuation, not symbol.
>
> Sorry, I guess I was thinking of \cl. It will not match ’, although
> it might be expected.
Which could be fixed by (modify-category-entry ?’ ?l).
I would suggest this additional docstring patch, because I was confused
at first as to what CATEGORY was supposed to be (I looked around a bit
for how to create some kind of "category object"):
diff --git i/src/category.c w/src/category.c
index 4397f66..31ac2ec 100644
--- i/src/category.c
+++ w/src/category.c
@@ -336,6 +336,7 @@ DEFUN ("modify-category-entry", Fmodify_category_entry,
the current buffer's category table.
CHARACTER can be either a single character or a cons representing the
lower and upper ends of an inclusive character range to modify.
+CATEGORY must be a category name (a character between ` ' and `~').
If optional fourth argument RESET is non-nil,
then delete CATEGORY from the category set instead of adding it. */)
(Lisp_Object character, Lisp_Object category, Lisp_Object table, Lisp_Object
reset)
>
> Anyway, my point is that these char-tables should really be treated as
> read-only by Lisp applications.
Right, but I think this bug is about the user modifying stuff.
- 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, 2016/08/12
- 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 <=
- 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