Deoplete.nvim: `:write` saves `<Plug>_` instead of the current file

Created on 21 Jun 2020  路  7Comments  路  Source: Shougo/deoplete.nvim

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

  • deoplete version (SHA1): 1a49407cf3eff03359de158151be174956b2ccbc

  • OS: Debian 10.4

  • neovim :version output: v0.5.0-563-ge628a05b5

  • :checkhealth or :CheckHealth result(neovim only):

health#deoplete#check
========================================================================
## deoplete.nvim
  - OK: exists("v:t_list") was successful
  - OK: has("timers") was successful
  - OK: has("python3") was successful
  - OK: Require Python 3.6.1+ was successful
  - OK: Require msgpack 1.0.0+ was successful
  - INFO: If you're still having problems, try the following commands:
    $ export NVIM_PYTHON_LOG_FILE=/tmp/log
    $ export NVIM_PYTHON_LOG_LEVEL=DEBUG
    $ nvim
    $ cat /tmp/log_{PID}
    and then create an issue on github

health#nvim_lsp#check
========================================================================
## Checking language server protocol configuration
  - INFO: clangd: configuration checked.
  - INFO: pyls: configuration checked.

health#nvim#check
========================================================================
## Configuration
  - OK: no issues found

## Performance
  - OK: Build type: RelWithDebInfo

## Remote Plugins
  - OK: Up to date

## terminal
  - INFO: key_backspace (kbs) terminfo entry: key_backspace=\177
  - INFO: key_dc (kdch1) terminfo entry: key_dc=\E[3~
  - INFO: $VTE_VERSION='5402'
  - INFO: $COLORTERM='truecolor'

health#provider#check
========================================================================
## Clipboard (optional)
  - OK: Clipboard tool found: xsel

## Python 2 provider (optional)
  - INFO: Disabled (g:loaded_python_provider=1).  This might be due to some previous error.
  - WARNING: No Python executable found that can `import neovim`. Using the first available executable for diagnostics.
  - ERROR: Python provider error:
    - ADVICE:
      - provider/pythonx: Could not load Python 2:
          /usr/bin/python2 does not have the "neovim" module. :help |provider-python|
          /usr/bin/python2.7 does not have the "neovim" module. :help |provider-python|
          python2.6 not found in search path or not executable.
          /usr/bin/python does not have the "neovim" module. :help |provider-python|
  - INFO: Executable: Not found

## Python 3 provider (optional)
  - INFO: Using: g:python3_host_prog = "/usr/bin/python3.7"
  - INFO: Executable: /usr/bin/python3.7
  - INFO: Python version: 3.7.3
  - INFO: pynvim version: 0.4.1
  - OK: Latest pynvim is installed.

## Python virtualenv
  - OK: no $VIRTUAL_ENV

## Ruby provider (optional)
  - WARNING: `ruby` and `gem` must be in $PATH.
    - ADVICE:
      - Install Ruby and verify that `ruby` and `gem` commands work.

## Node.js provider (optional)
  - WARNING: `node` and `npm` (or `yarn`) must be in $PATH.
    - ADVICE:
      - Install Node.js and verify that `node` and `npm` (or `yarn`) commands work.

## Perl provider (optional)
  - WARNING: `perl` and `cpanm` must be in $PATH.
    - ADVICE:
      - Install Perl and cpanminus and verify that `perl` and `cpanm` commands work.


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

" 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.

Most helpful comment

Now it seems OK, thanks.

All 7 comments

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

OK. I think it is fixed.

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

Please upload the screenshots

Uh, I get the reason.

Fixed.
Please use the latest.

Now it seems OK, thanks.

Was this page helpful?
0 / 5 - 0 ratings