ela
Contents

ManualEditors

When ela --lsp says nothing

In the terminalela --spec when-ela-lsp-says-nothing

An editor that starts no server, or one that stops at once, usually has a PATH without ela.

  • The command on its own. Run in a terminal, ela --lsp waits for an editor's messages on stdin; ctrl-d ends its input, and it exits with status 1.
  • The path. An editor started from the desktop may not have the terminal's PATH. The setups above take a full path in place of ela: /usr/bin/ela for the package.

Each editor shows what passed between it and the server:

EditorThe server's log
Neovim:checkhealth vim.lsp lists the servers attached to the buffer and the log file; :lua vim.lsp.log.set_level("debug") logs every message
VS Code, VSCodiumSimple LSP Client: Show Status from the command palette, and the extension's channel in the Output panel; "simpleLspClient.servers" is read again when it changes
Helixhx --health ela says whether ela is found; hx -v backup.ela, then :log-open
EmacsM-x eglot-events-buffer for the messages, M-x eglot-stderr-buffer for what the server printed
Katethe Output tab of the LSP Client view; Kate started from a terminal with LSPCLIENT_DEBUG=1 prints every message
KAT800, GNOME Text Editorno server: ela --lint in a terminal