Class
LspClient
Description
class Lsp.Client : GObject.Object
{
/* No available fields */
}The JSON-RPC client. Exposes methods and notifications that should be called from server code. If you want to implement a LSP editor, use LspEditor.
This is a wrapper over JsonrpcClient that supports LSP-specific operations, and is created internally by LspServer.
Instance methods
lsp_client_show_message_async
The show message notification is sent from a server to a client to ask the client to display a particular message in the user interface.
lsp_client_ask_message_async
The show message request allows to pass actions and to wait for an answer from the client.
lsp_client_show_document_async
The show document request is sent from a server to a client to ask the client to display a particular document in the user interface.
lsp_client_publish_diagnostics_async
Diagnostics notifications are sent from the server to the client to signal results of validation runs.
lsp_client_log_trace_async
A notification to log the trace of the server’s execution. The amount and content of these notifications depends on the current trace configuration. If trace is ‘off’, the server should not send any logTrace notification. If trace is ‘messages’, the server should not add the ‘verbose’ field in the LogTraceParams. $/logTrace should be used for systematic trace reporting. For single debugging messages, the server should send window/logMessage notifications.
lsp_client_log_message_async
The log message notification is sent from the server to the client to ask the client to log a particular message.
lsp_client_apply_edit_async
The workspace/applyEdit request is sent from the server to the client to apply a workspace edit.
Signals
Signals inherited from GObject (1)
GObject::notify
The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.