Using the rubocop reporter requires constant "reloading" of file

neoclide / coc-solargraph

Solargraph extension for coc.nvim

202 stars 10 forks source link

Using the rubocop reporter requires constant "reloading" of file #32

Closed thornomad closed 4 years ago

thornomad commented 4 years ago

I am not sure how to troubleshoot this and would love some help!

I have rubocop set as a solargraph reporter. I get great linting feedback this way:

However, almost constantly (while editing files) see this warning instead:

This happens very regularly while editing. In order to resolve it, I have to call :e to reload the file. After hitting :e the errors go away and the right linting information re-appears. Shortly after though, the errors come back.

I'm in the habit of constantly hitting :e<CR> in my workflow and wondering if there is a better way or something I might investigate with my setup?

Thanks.

chemzqm commented 4 years ago

We need connection log of coc.nvim to address this issue, please follow these steps:

Add let g:node_client_debug = 1 to your vimrc, save your vimrc and exit vim.
Restart your vim/neovim to make the issue happen.
Get the log filepath by :echo $NODE_CLIENT_LOG_FILE
Attach the log file or paste content from the log.

thornomad commented 4 years ago

@chemzqm - I was trying to get a clean "short" log for you and noticed that this problem does not repeat itself on a clean boot of vim. Usually I leave vim up for days ... but now that I was trying to reproduce it from start I am not able to. After a time, something else is happening and that problem begins .. but then if I restart and do the same actions it's not happening.

Anyway, I am going to try and track down a reproduceable case on my end and I will re-open a ticket. Having this debugging tool is very helpful. Thank you.