Thoughts on not attaching the lsp client to the assembly/decompiled buffer? about omnisharp-extended-lsp.nvim HOT 2 CLOSED

I am not 100% now, since it's been a while since I worked on this, but if the buffer is not attached to LSP client, then no LSP commands will work. To begin with, it uses clients that are attached to current buffer at the start of lsp_definitions. Then, if I am not mistaken, the file is loaded using LSP protocol to the LSP server, so when any command is executed in the file at certain position, LSP server has to have this file loaded. So for metadata files this maybe could be circumvented, by explicitly going with 'o#/v2/gotodefinition call, instead of regular LSP textDocument/definition.

So overall, I believe it is not as simple as not attaching the client to the buffer, as that breaks definition lookup from inside metadata files. It maybe could be worked around by using custom command and not lsp handler, but at this moment I haven't felt that current behavior causes me issues, so I don't feel like spending time on this.

from omnisharp-extended-lsp.nvim.

I appreciate your thoughts on this. I haven't felt a need for definition lookups inside the metadata file since disabling LSP on them, but if I change my mind and spend time on getting it working like you're suggesting I'll submit a PR. Thanks again for creating this plugin and putting it out into the world!

from omnisharp-extended-lsp.nvim.