Christian Brabandt

yes agree, we should fix that one

You are right, it smells like a compiler bug. I am still slightly worried about the added performance overhead, which seems to happen at runtime. @LemonBoy what is the status...

I am sorry, I lost track a bit. What is the status of this one please? Did we reach an agreement here?

it's not only about performance. writing legacy vimscript can be rather messy and has several pitfalls (see the various restrictions introduce by `:scriptversion`) + plus some rather obscure vim commands/options...

why do you need this?

That is not so simple, because syn keyword modifies the global state of what characters are considered keyword characters. The second alternative, while possible will have impacts on priorities and...

Works for me using Python3.11

not reproducible

Hm, works for me with $TERM `xterm-256colors` and even on Windows gvim. Might be terminal related then?

how did you compile Vim/Python? This seems to be an error on the python side, according to [here](https://docs.python.org/3/c-api/exceptions.html#c.PyErr_GetRaisedException) this is part of python3.12, stable API.