diff options
author | Robin Haberkorn <robin.haberkorn@googlemail.com> | 2024-12-22 18:16:17 +0300 |
---|---|---|
committer | Robin Haberkorn <robin.haberkorn@googlemail.com> | 2024-12-22 19:33:48 +0300 |
commit | 6cd143f86d3c39be633c1dcf5a4165f2f06a04f6 (patch) | |
tree | f922eb2d979042c7a89da1a3dfc8851c90776d2d /src/view.c | |
parent | f4fd6de46a8d66032efd6fa86a5674edd0ec839f (diff) | |
download | sciteco-6cd143f86d3c39be633c1dcf5a4165f2f06a04f6.tar.gz |
fixed lexing (syntax highlighting) of the null-character (^@) in SciTECO code
* Apparently g_utf8_get_char_validated() sometimes(!) returns -2 for null-characters,
so it was considered an invalid byte sequence.
* What's strange and unexplainable is that other uses of the function, as are behind nA and nQq,
did not cause problems and returned 0 for null-bytes.
* This also fixes syntax higlighting of .teco_session files which use the null-byte as the
string terminator.
(.teco_session files are not highlighted automatically, though.)
Diffstat (limited to 'src/view.c')
-rw-r--r-- | src/view.c | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -657,7 +657,7 @@ teco_view_get_character(teco_view_t *ctx, gsize pos, gsize len) * The sign bit in UCS-4/UTF-32 is unused, so this will even * suffice if TECO_INTEGER == 32. */ - return (gint32)g_utf8_get_char_validated(buf, -1); + return *buf ? (gint32)g_utf8_get_char_validated(buf, -1) : 0; } void |