[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#53260: char-syntax differs in interpreter and bytecode [PATCH]
From: |
Mattias Engdegård |
Subject: |
bug#53260: char-syntax differs in interpreter and bytecode [PATCH] |
Date: |
Sun, 16 Jan 2022 12:04:51 +0100 |
15 jan. 2022 kl. 23.51 skrev Stefan Monnier <monnier@iro.umontreal.ca>:
> Doesn't sound right: char tables are indexed by chars (i.e. Unicode code
> points) not by bytes, so we need to convert the byte into a char
> before indexing.
Sure, I'm happy to do it either way. Chars retrieved from unibyte buffers or
strings really should be converted to multibyte before used with char-syntax;
unibyte buffers are not very common but strings slightly more so.
0001-Fix-Fchar_syntax-for-non-ASCII-in-unibyte-buffers.patch
Description: Binary data
- bug#53260: char-syntax differs in interpreter and bytecode, Mattias Engdegård, 2022/01/14
- bug#53260: char-syntax differs in interpreter and bytecode, Lars Ingebrigtsen, 2022/01/15
- bug#53260: char-syntax differs in interpreter and bytecode, Stefan Monnier, 2022/01/15
- bug#53260: char-syntax differs in interpreter and bytecode, Mattias Engdegård, 2022/01/15
- bug#53260: char-syntax differs in interpreter and bytecode, Eli Zaretskii, 2022/01/15
- bug#53260: char-syntax differs in interpreter and bytecode, Stefan Monnier, 2022/01/15
- bug#53260: char-syntax differs in interpreter and bytecode [PATCH],
Mattias Engdegård <=
- bug#53260: char-syntax differs in interpreter and bytecode [PATCH], Lars Ingebrigtsen, 2022/01/20
- bug#53260: char-syntax differs in interpreter and bytecode [PATCH], Mattias Engdegård, 2022/01/20