https://whynothugo.nl/tags/lsp/Recent content in Lsp on WhyNotHugoHugo -- gohugo.ioenFri, 22 Sep 2023 17:43:51 +0200https://whynothugo.nl/journal/2023/09/05/debugging-a-non-functional-pylsp/Tue, 05 Sep 2023 00:00:00 +0000https://whynothugo.nl/journal/2023/09/05/debugging-a-non-functional-pylsp/pylsp wasn’t working today for some reason. It wasn’t jumping to definitions, offering any auto-completions, nor formatting code. I had to figure out why. Usually, LSPs are executed directly by the IDE with stdin/stdout piped directly into an LSP client, which means that logging to stdout/stderr is not as simple as usual. Running the LSP manually on a TCP port makes following logs nice and simple. The following command should be executed in the root of a python project: