Languageclient-neovim: no notification handler registered for "/home/vagrant/.local/share/nvim/plugged/LanguageClient-neovim/rplugin/python3/LanguageClient:autocmd:CursorMoved:*"

[allan-simon]

If you are still seeing an error or other types of issue, please create ticket with

• neovim/vim version NVIM v0.2.2
• Plugin version (git SHA) bbb92f5ebbebc44d5a3e2333f4b01d1eb92495e0
• Minimal vimrc (e.g. https://github.com/autozimu/LanguageClient-neovim/blob/next/min-init.vim)

call plug#begin('~/.local/share/nvim/plugged')

Plug 'autozimu/LanguageClient-neovim', {
    \ 'branch': 'next',
    \ 'do': 'bash install.sh',
    \ }

Plug 'Shougo/deoplete.nvim', { 'do': ':UpdateRemotePlugins' }

let g:LanguageClient_loggingLevel = 'DEBUG

• Language server name/link and version
  pyls

• Reproduction steps (from clean state)

  1. open a file with nvim, can be any file (even a new one)
  2. the error no notification handler registered for "/home/vagrant/.local/share/nvim/plugged/LanguageClient-neovim/rplugin/python3/LanguageClient:autocmd:CursorMoved:*" appears everytime you try to move the cursor
  3. no step 3

• Logs. Ensure let g:LanguageClient_loggingLevel = 'DEBUG' is in minimal
  vimrc. Follow previous provided reproduction steps to reproduce the bug.
  Attach contents of /tmp/LanguageClient.log and /tmp/LanguageServer.log.

2018-03-27T10:34:15.272756589+00:00 DEBUG languageclient::vim - state.id: 3 ==> 4
2018-03-27T10:34:15.273030238+00:00 INFO languageclient::vim - => {"jsonrpc":"2.0","method":"eval","params":["[!!get(g:, 'LanguageClient_autoStart', 1), get(g:, 'LanguageClient_serverCommands', {}), get(g:, 'LanguageClient_selectionUI', v:null), get(g:, 'LanguageClient_trace', v:null), get(g:, 'LanguageClient_settingsPath', '.vim/settings.json'), !!get(g:, 'LanguageClient_loadSettings', 1), get(g:, 'LanguageClient_rootMarkers', v:null), get(g:, 'LanguageClient_changeThrottle', v:null), !!get(g:, 'LanguageClient_diagnosticsEnable', 1), get(g:, 'LanguageClient_diagnosticsList', v:null), get(g:, 'LanguageClient_diagnosticsDisplay', {}), get(g:, 'LanguageClient_windowLogMessageLevel', 'Warning')]"],"id":4}
2018-03-27T10:34:15.273633411+00:00 INFO languageclient::vim - <= {"id": 4, "jsonrpc": "2.0", "result": [1, {"python": ["/tmp/virtualenv/bin/pyls"]}, null, null, ".vim/settings.json", 1, null, null, 1, null, {}, "Warning"]}
2018-03-27T10:34:15.275598873+00:00 DEBUG languageclient::vim - state.id: 4 ==> 5
2018-03-27T10:34:15.275765295+00:00 INFO languageclient::vim - => {"jsonrpc":"2.0","method":"eval","params":["get(g:, 'loaded_fzf')"],"id":5}
2018-03-27T10:34:15.276267371+00:00 INFO languageclient::vim - <= {"id": 5, "jsonrpc": "2.0", "result": 0}
2018-03-27T10:34:15.277421773+00:00 DEBUG languageclient::vim - state.serverCommands.python: null ==> ["/tmp/virtualenv/bin/pyls"]
2018-03-27T10:34:15.277461808+00:00 DEBUG languageclient::vim - state.trace: null ==> "off"
2018-03-27T10:34:15.277474108+00:00 DEBUG languageclient::vim - state.loadSettings: false ==> true
2018-03-27T10:34:15.277502118+00:00 WARN languageclient::languageclient - No language server command found for type: text.
2018-03-27T10:34:15.277513854+00:00 INFO languageclient::languageclient - End languageClient/handleBufReadPost

[autozimu]

Did you run :UpdateRemotePlugins?

[allan-simon]

no, it fixed the issue, thanks, is there anyway to put in the do: section like it used to be ? (I don't know if vim-plug permit several instructions in do as there's already the bash install.sh now ... )

[Shokodemon]

my issue was a permission issue in /tmp

/tmp/LanguageClient.log is written by the system's nvim.

if you a system-install of nvim, and do stuff with root (ive done a million things as root that day, so i cant say what exactly triggered that write / permission change)
it would write LanguageClient into /tmp as root, and then your non root user will be a bit upset about that.

this was on linux ubuntu 18, MacOs folks issues may vary, i find it a bit daft honestly.

Nvim us often needlessly frustrating. (this issue, needing to set providers by hand, etc)

[KillTheMule]

Nvim us often needlessly frustrating.

This isn't a neovim issue though, but one of lcn.

[Shokodemon]

its only ironic that this causes weirdnesses in neovim and its underlying
components / plugins. nvim came to solve this issue as a mission.

community is not being watchful.

On Mon, Oct 1, 2018 at 9:51 AM KillTheMule [e-mail] wrote:

Nvim us often needlessly frustrating.

This isn't a neovim issue though, but one of lcn.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/autozimu/LanguageClient-neovim/issues/346#issuecomment-425818647,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB-MpKVRD2jb4p-4Dlj-KQ7lzC-iX0Taks5ugcmGgaJpZM4S8rSW
.

[KillTheMule]

I don't understand what you're arguing here. Your issue was solely caused by lcn using a predetermined uniform file name for its log, there's nothing here that vim or nvim could do about that.

(e) Seems I went into arguing on a unrelated issue on a repo from someone else. Sorry for that, let's cut this short.