Not sure if you're still maintaining this plugin, but I'm still using vimfindsme and came across this recently:
When opening a very large filename I get an error in vimple#ls#new.
vim $(python3 -c 'print("x"*2000)')
The error seems to be because there is a truncation in the output of :ls! which means we don't get all things printed out for that buffer.
I hit this because my make output included a very long line that matched whatever errorformat was active, so vim used part of it as a very long filename (incorrectly).
That meant that vfm_browse_bufs started giving errors (and not working).
If you are still maintaining this repo I'd request either adding a filter option to vimple#associate that is used between the substitute and map actions and can be used to , and/or maybe introducing some fallback to use Neovim's vim.api.nvim_get_bufs (don't know if there is a standard vim equivalent).
Not sure if you're still maintaining this plugin, but I'm still using vimfindsme and came across this recently:
When opening a very large filename I get an error in
vimple#ls#new.The error seems to be because there is a truncation in the output of
:ls!which means we don't get all things printed out for that buffer.I hit this because my
makeoutput included a very long line that matched whatevererrorformatwas active, so vim used part of it as a very long filename (incorrectly).That meant that
vfm_browse_bufsstarted giving errors (and not working).If you are still maintaining this repo I'd request either adding a filter option to
vimple#associatethat is used between the substitute and map actions and can be used to , and/or maybe introducing some fallback to use Neovim'svim.api.nvim_get_bufs(don't know if there is a standard vim equivalent).