Custom method trigger/event listener

[Propfend]

Issues

• I have checked existing issues and there are no existing ones with the same request.

Feature description

Hello. Congrats for this nice project.

I am in a situation where i would like to build the diagnostics which depends on external prompt from user. I can read this prompt from a global var, but the diagnostics method should also be triggered when the prompt changes.

I do wonder if there is some out of the box way of doing this without workarounds like sending didChange events, registering a different trigger for the method besides the one when buffer content changes, or even registering a method itself, i know that is not the natural way LSP works.

Help

Yes

Implementation help

No response

[mochaaP]

do you have a detailed scenario for this? i kinda get the point but im not sure if im getting it right.

[Propfend]

The scenario is that one i just described. Basically i want a source which builds diagnostics based on user prompt:

• I do have an inference server running.
• I do have an user function which takes the user prompt and updates it somewhere somehow which im still not sure, that is the problem.
• I do have a none-ls source whose generator will get this prompt and request the inference server with the buffer content and return the response.
• The remaining are implementation details.

I can register this prompt globally, that will be accessible through the generator. The thing is that the source should be re-building the diagnostics when the prompt is updated as well, not only with didChange requests. I can see some two alternatives:

• Send some didChange requests with empty payload to the none-ls client whenever the prompt changes, which will redirect to the server. But that is not ideal, of course.
• Allow the users to customize the LSP protocol/interface. That can be registering some custom event listener to the source. So that could watch for external vars etc. Or allowing to register methods itself. It could trigger an standard command (diagnostics, completion etc. That can maybe be limited somehow using the enums).

[mochaaP]

maybe none-ls isn't the correct tool for you.

you shall try textDocument/publishDiagnostics. our diagnostics are bound to certain event triggers (didChange/didSave/didOpen) then set via vim.diagnostic, which does not conform to the regular lsp c/s model.

[Propfend]

you shall try textDocument/publishDiagnostics. our diagnostics are bound to certain event triggers (didChange/didSave/didOpen) then set via vim.diagnostic, which does not conform to the regular lsp c/s model.

Yes, for this case it does not make a difference if it sends the textDocument/publishDiagnostics request to the client or writes to the buffer directly.

That is basically what im doing, i'm currently just triggering the diagnostics write on the server sending empty requests.

maybe none-ls isn't the correct tool for you.

Still, despite all of that, none-ls was the best tool i have found so far to solve that. So i do not need to write CLI tools which does the processing and convert output to specific format.

which does not conform to the regular lsp c/s model.

Considering that. Do we have some motivation to add that custom trigger or something among those lines, since that none-ls is not compliant with the LSP server exactly as it is in-process?