Terminal closing message about fzf-preview.vim

[yuki-yano]

Solved by changing the buffer's bdelete to bdelete!.
Please update plugin.

[duanmuq]

I have the same question.
Now, I remove the "set confirm" form the init.vim, it works.

But I still want to find way to get the "set confirm" back, it's useful for remender me to save buffer

[yuki-yano]

I cant reproduce.
Please write the version of neovim and fzf.

[yuki-yano]

A similar problem has also occurred in fzf.vim, so it may not be a problem with this plugin.
mhinz/neovim-remote#47

[ubmarco]

Version:

$ fzf --version
0.17.4 (f0fe79d)

$ nvim --version
NVIM v0.4.3
Build type: Release
LuaJIT 2.0.5
Compilation: /usr/bin/cc -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -O2 -DNDEBUG -DMIN_LOG_LEVEL=3 -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fdiagnostics-color=always -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -I/build/neovim/src/build/config -I/build/neovim/src/neovim-0.4.3/src -I/usr/include -I/build/neovim/src/build/src/nvim/auto -I/build/neovim/src/build/include
Compiled by builduser

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"

Run :checkhealth for more info

[ubmarco]

For me, commenting out set confirm from the thinkvim config also fixes the issue.

[yuki-yano]

0.17.4 was released in 2018. https://github.com/junegunn/fzf/releases/tag/0.17.4
Try the latest release.

[ubmarco]

I updated to 0.20.0, same issue.

[ubmarco]

I actually don't understand where this issue could come from. Is that related to fzf, fzf.vim, fzf-preview.vim, my xfce4-terminal or neovim? It looks like fzf-preview.vim calls fzf to get the file list and displays it. The call to fzf goes through a shell which is closed at the end for which nvim asks for confirmation.

[jemag]

This issue appeared for me when I updated my plugins (including fzf and fzf-preview). I did not update neovim however, so I am guessing that this behavior appeared from one of the updated plugins.

[glepnir]

This issue appeared for me when I updated my plugins (including fzf and fzf-preview).

yes .when update ,i aslo get this problem.

[ubmarco]

Thanks a lot, it works.