Shougo / deoplete.nvim

:stars: Dark powered asynchronous completion framework for neovim/Vim8
Other
5.94k stars 295 forks source link

`:write` saves `<Plug>_` instead of the current file #1107

Closed e-kwsm closed 4 years ago

e-kwsm commented 4 years ago

Warning: I will close the issue without the minimal init.vim and the reproduction instructions.

First of all, I'm sorry but I don't think I can show how-to-reproduce. I would appreciate any help.

Problems summary

Sometimes :w saves a new file named <Plug>_ instead of the current one, which implies :w <Plug>_ is executed.

I'm suspecting deoplete because only deoplete has <Plug>_ among plugins I'm using:

Expected

:w saves the current file.

Environment Information

health#deoplete#check

deoplete.nvim

health#nvim_lsp#check

Checking language server protocol configuration

health#nvim#check

Configuration

Performance

Remote Plugins

terminal

health#provider#check

Clipboard (optional)

Python 2 provider (optional)

Python 3 provider (optional)

Python virtualenv

Ruby provider (optional)

Node.js provider (optional)

Perl provider (optional)


## Provide a minimal init.vim/vimrc with less than 50 lines (Required!)

```vim
" Your minimal init.vim/vimrc
set runtimepath+=~/path/to/deoplete.nvim/
let g:deoplete#enable_at_startup = 1
" actually this is not minimal...

How to reproduce the problem from neovim/Vim startup (Required!)

Open a file, modify contents, and then :w; sometimes <Plug>_ is created.

e-kwsm commented 4 years ago

This time :<Plug>_w<Plug>_ is executed.

Shougo commented 4 years ago

OK. I think it is fixed.

e-kwsm commented 4 years ago

Thank you for your quick response, but sometimes E15: Invalid expression: is raised after updating to 437d117320c17f98dbe303ded6a90b7fd125b509.

Shougo commented 4 years ago

Please upload the screenshots

Shougo commented 4 years ago

Uh, I get the reason.

Shougo commented 4 years ago

Fixed. Please use the latest.

e-kwsm commented 4 years ago

Now it seems OK, thanks.