Error detected while processing function fish#Complete

[MaxGyver83]

When I edit fish files, I often get error messages like this one:

Error detected while processing function fish#Complete:
line    8:
E484: Can't open file /tmp/vxL0vJq/2
Press ENTER or type command to continue

I use:

• vim 8.2.2398
• fish 3.2.1 (but I had this issue before)
• vim-mucomplete commit 83cd9b3

My mucomplete settings in ~/.vimrc:

let g:mucomplete#enable_auto_at_startup = 1
let g:mucomplete#always_use_completeopt = 1

How to reproduce:

vim /tmp/x.fish
iecho "te

But I can't reproduce it with a minimal config:

~/.vim/troubleshooting_vimrc.vim:

...
" Optionally add additional configuration below this line
set runtimepath+=~/.vim/pack/plugins/start/vim-fish
let g:mucomplete#enable_auto_at_startup = 1
let g:mucomplete#always_use_completeopt = 1

vim -u ~/.vim/troubleshooting_vimrc.vim /tmp/z.fish

I can't even reproduce it when I append the whole content of my ~/.vimrc to ~/.vim/troubleshooting_vimrc.vim.

Btw, this is my .vimrc. And this is the function mentioned in the error message: https://github.com/dag/vim-fish/blob/master/autoload/fish.vim#L44

[lifepillar]

This looks to me as an issue independent of MUcomplete. To verify that, execute :MUcompleteAutoOff and try completing by pressing CTRL-X CTRL-O. If the issue is still there, then the cause of the problem is not MUcomplete.

[MaxGyver83]

Thanks for your answer! I have tested it and you are right. The issue still occurs with ctrl-x ctrl-o. Sorry for bothering you.

[lifepillar]

If you think that the issue is a setting in your vimrc, I suggest that you perform a binary search by commenting out half of your vimrc, test this issue, then comment/uncomment another fourth according to the result. Iterate until find the offending line.

[MaxGyver83]

Thanks! Meanwhile, I can tell for sure that this issue is not caused by my .vimrc. I could reproduce this error with a minimal .vimrc and only the plugin vim-fish loaded. This is my issue for that plugin: dag/vim-fish#50 (But unfortunately, that project seems to be dead.)