From 2972d9264b3de9dbd024f719e4746bb6bea36e30 Mon Sep 17 00:00:00 2001 From: William Boman Date: Sun, 22 May 2022 15:39:16 +0200 Subject: feat: add :LspLog command #1917 --- README.md | 2 +- doc/lspconfig.txt | 2 +- lua/lspconfig.lua | 7 +++++++ 3 files changed, 9 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index d7a25bf4..a8537791 100644 --- a/README.md +++ b/README.md @@ -140,7 +140,7 @@ vim.lsp.set_log_level("debug") Attempt to run the language server, and open the log with: ``` -:lua vim.cmd('e'..vim.lsp.get_log_path()) +:LspLog ``` Most of the time, the reason for failure is present in the logs. diff --git a/doc/lspconfig.txt b/doc/lspconfig.txt index d1d9103c..ffb738f4 100644 --- a/doc/lspconfig.txt +++ b/doc/lspconfig.txt @@ -608,7 +608,7 @@ the built-in client, specifically considering the RPC logs. Example: Attempt to run the language server, and open the log with: > - :lua vim.cmd('e'..vim.lsp.get_log_path()) + :LspLog < Note that `ERROR` messages containing `stderr` only indicate that the log was sent to `stderr`. Many servers counter-intuitively send harmless messages diff --git a/lua/lspconfig.lua b/lua/lspconfig.lua index 8404632d..b99aa6ea 100644 --- a/lua/lspconfig.lua +++ b/lua/lspconfig.lua @@ -21,6 +21,13 @@ function M._root._setup() '-nargs=0', description = '`:LspInfo` Displays attached, active, and configured language servers', }, + LspLog = { + function() + vim.cmd(string.format('tabnew %s', vim.lsp.get_log_path())) + end, + '-nargs=0', + description = "`:LspLog` Opens the Nvim LSP client log.", + }, LspStart = { function(server_name) if server_name then -- cgit v1.2.3-70-g09d2