bfredl

I took a stab at implementing an omnifunc. So with `set omnifunc=IPyOmniFunc` it should work if SuperTab is set to use omnifunc. But for an async framework like Deoplete using...

Yes. root cause is not related to TUI (but internal inconsistency of ext_messages memory handling)

`utf_tolower` actually allows the behavior to be configurable, `casemap` can be set to `keepascii` to use vims own ASCII-safe functions for `c < 128`, and if not, the locale specific...

It seems a common pattern in vim, somewhat simplified ``` #ifdef FEAT_MBYTE if( c > 128) { // or mb_ptr2len(p) > 1 // use multi-byte function } else #endif {...

Hmm setting `LANG=tr_TR.UTF-8` gives interesting behavior, doing `gu`/`gU` leaves ascii `iI` completely unchanged, thus _neither_ the ASCII nor the indended locale behavior (same in latest vim), unsetting `casemap` makes `utf_tolower`...

Posted tr_TR issue to vim-dev: https://groups.google.com/forum/#!topic/vim_dev/sn0MDYfETCs

Yes, that's _exactly_ what I want. Including lpeg specifically, I discovered and had to work around the `zig fetch` bug yesterday myself :sweat_smile: .

Thanks. Just one more piece of information in case if it useful for anyone: I also needed to get the lua include path as a `LazyPath` as well (this is...

hmm, I think the current code assumes that the error object is a string. all builtin errors are strings, but `error()` can be called with any object, or no arg...

> Run nvim_input("y") and neovim will send the following message to clear the confirm prompt: [ "msg_showcmd", [] ] No, a `msg_showcmd` must never be interpreted to "clear" a `msg_show`...