Sean Dewar

Looks like it's being interpreted as `:win[size] 30 10`. This should be an error. Sounds like you wanted to use `vim.fn.win_getid(30, 10)` (instead of `vim.cmd.*`)

Moreso a limitation of `:move` and `:copy` than a bug. They're hardcoded to work on curbuf, and as such, only accept uppercase mark `{address}`es referring to curbuf. Would potentially be...

> Doesn't include support for highlight-start, highlight-stop, highlight-ctermul, highlight-term, highlight-font since they aren't available in neovim . Should I mark it as partial port ? iirc `highlight-term` is deprecated and...

Problem is `check_timestamps` in that commit reloading the fifo file (skipping W11 prompt if `autoread` is set), which results in an empty buffer. Similar behaviour is observed in Vim with...

Thanks for the PR! Addressing your observations: > 1. The colon (:) no longer counted as a keyword character for syntax highlighting. What's happening here is that syntax/sh.vim is `syn...

To fix this for 0.10, I've pushed my suggested change and fixed the failing test. I've left the `:syn include` for syntax/sh.vim alone; it's not so important to address now....

Can `tv_list_uidx()` be used?

Adding to @Penaz91's comment, if you're using Nvim v0.8+, `filetype.lua` is already enabled by default, so there is no need to add the suggested lines to your configuration.

> I think the commit that triggers this behavior is https://github.com/vim/vim/commit/bf44b69d1f91d9778ae1887128c63d35d9a3d19b. If that's indeed the commit, it _may_ not indicate a bug in Vim; `:wincmd p` beeping when there's no...

> Any idea how to proceed? Is this a Vim issue or a CtrlP issue? If things are happening as I assume, I'd consider the old behaviour a bug (and...