taylan97

Doh. I checked issues, but did not see this pull request. I have suffered from this today, https://github.com/nvim-lua/completion-nvim/issues/255, with a similar fix: https://github.com/taylan97/completion-nvim/pull/1 Seems it's kind of old and no...

I also spent a bit of time writing `assert.is_equal(type(some_table), type({})` or `asset.is_true(type(n) == type(1))`, wishing I could just write `assert.is.table(some_table)` or `assert.is.number(n)`. I was all ready to write my own...

Yes perhaps. Though your inspections in that thread talk about `nvim_win_set_buf`'s behavior with *unloaded* buffers, while this buffer is loaded (via `bufload` at least, which to me (and the docs)...

Also serendipitously, #12951 "Files in after/ftplugin not loaded". I wonder if it's an issue with `after/`* specifically. In that issue, you are instructed to setup the ftplugin, then run `:copen`...

Tried re-configuring the bug fixture. It presents identically, whether it's ftplugin is in `$RTP/ftplugin` or `$RTP/after/ftplugin`, so I don't think this is specific to `after` style plugins.