aboutsummaryrefslogtreecommitdiff
path: root/runtime/syntax/python.vim
diff options
context:
space:
mode:
authorJan Edmund Lazo <janedmundlazo@hotmail.com>2026-08-29 10:01:08 -0400
committerJan Edmund Lazo <janedmundlazo@hotmail.com>2026-08-29 14:49:56 -0400
commit063c76f500883600b3a5be186a0bf98c25002063 (patch)
tree4e67f9e20a4da677d9aadfebb1ae35fd0e38f3c0 /runtime/syntax/python.vim
parentee19522048c0b607a2b2b379cdfc020f13bff95b (diff)
downloadrneovim-063c76f500883600b3a5be186a0bf98c25002063.tar.gz
rneovim-063c76f500883600b3a5be186a0bf98c25002063.tar.bz2
rneovim-063c76f500883600b3a5be186a0bf98c25002063.zip
build(vim-patch): v8.2.3068 is almost auto n/a
Nvim uses utf8proc or an older process involving "src/unicode/" and "download-unicode-files.sh" to decouple unicode characters from "mbyte.c". These unicode patches should be auto N/A but the diff hunk xfuncname is wrong for utf_char2cells(). Is it because of the `#ifdef`? Need a volunteer to inspect if these patches still have relevant changes Nvim ```c /// same as utf_composinglike but operating on UCS-4 values bool utf_iscomposing(int c1, int c2, GraphemeState *state) { return (!utf8proc_grapheme_break_stateful(c1, c2, state) || arabic_combine(c1, c2)); } ``` Vim ```c /* * Return TRUE if "c" is a composing UTF-8 character. This means it will be * drawn on top of the preceding character. * Based on code from Markus Kuhn. */ int utf_iscomposing(int c) { // Sorted list of non-overlapping intervals. // Generated by ../runtime/tools/unicode.vim. static struct interval combining[] = { {0x0300, 0x036f}, {0x0483, 0x0489}, {0x0591, 0x05bd}, // ... {0x0300, 0x036f}, {0x0483, 0x0489}, {0x0591, 0x05bd}, }; return intable(combining, sizeof(combining), c); } ```
Diffstat (limited to 'runtime/syntax/python.vim')
0 files changed, 0 insertions, 0 deletions