nimlsp VS lsp-mode

Downloading https://github.com/PMunch/nimlsp using git

Cloning into '.'... From https://github.com/pmunch/nimlsp * tag v0.4.4 -> FETCH_HEAD + nimble build -y --localdeps Warning: Using project local deps mode Verifying dependencies for [email protected] Prompt: No local packages.json found, download it from internet? -> [forced yes] Downloading Official package list Success Package list downloaded. Installing jsonschema@>= 0.2.1 Downloading https://github.com/PMunch/jsonschema using git Verifying dependencies for [email protected] Installing ast_pattern_matching@any version Downloading https://github.com/nim-lang/ast-pattern-matching using git Verifying dependencies for [email protected] Installing [email protected] Success: ast_pattern_matching installed successfully. Installing [email protected] Success: jsonschema installed successfully. Installing asynctools@>= 0.1.1 Downloading https://github.com/cheatfate/asynctools using git Verifying dependencies for [email protected] Installing [email protected] Success: asynctools installed successfully. Building nimlsp/nimlsp_debug using c backend [1m/home/terrior/.local/share/nvim/mason/.packages/nimlsp/src/nimlsppkg/suggestlib.nim(3, 18) [0m[31mError: [0mcannot open file: nimsuggest/nimsuggest[36m[0m[0m Tip: 30 messages have been suppressed, use --verbose to show them. Error: Build failed for package: nimlsp ... Execution failed with exit code 1 ... Command: /usr/bin/nim c --colors:on --noNimblePath -d:NimblePkgVersion=0.4.4 --path:/home/terrior/.local/share/nvim/mason/.packages/nimlsp/nimbledeps/pkgs/ast_pattern_matching-1.0.0 --path:/home/terrior/.local/share/nvim/mason/.packages/nimlsp/nimbledeps/pkgs/jsonschema-0.2.1 --path:/home/terrior/.local/share/nvim/mason/.packages/nimlsp/nimbledeps/pkgs/asynctools-0.1.1 --hints:off -o:/home/terrior/.local/share/nvim/mason/.packages/nimlsp/nimlsp_debug /home/terrior/.local/share/nvim/mason/.packages/nimlsp/src/nimlsp_debug.nim spawn: bash failed with exit code 1 and signal 0.

nimlangserver is an implementation of Language Server Protocol with the goal to make nim IDE experience more mature. The main difference between nimlangserver and the existing nimlsp is that nimlangserver runs nimsuggest in a separate process and that nimlangserver is using a newly introduced version of nimsuggest v3(see bellow). nimlangserver is currently integrated in VScode via vscode-nim and in Emacs via lsp-mode but adding integraion with other editors should be trivial.

Downloading https://github.com/PMunch/nimlsp using gitTVerifying dependencies for [email protected]: Dependency on jsonschema@>= 0.2.1 already satisfiedVerifying dependencies for [email protected]: Dependency on ast_pattern_matching@any version already satisfiedVerifying dependencies for [email protected]: Dependency on asynctools@any version already satisfiedVerifying dependencies for [email protected] [email protected] nimlsp/nimlsp using c backend/tmp/nimble_153465/githubcom_PMunchnimlsp/src/nimlsppkg/baseprotocol.nim(2, 8) Warning: imported and not used: 'logger' [UnusedImport]/tmp/nimble_153465/githubcom_PMunchnimlsp/src/nimlsppkg/suggestlib.nim(11, 8) template/generic instantiation of `mImport` from here/tmp/nimble_153465/githubcom_PMunchnimlsp/src/nimlsppkg/suggestlib.nim(7, 14) Error: cannot open file: /usr/nimsuggest/nimsuggest.nimPrompt: Build failed for '[email protected]', would you like to try installing 'nimlsp@#head' (latest unstable)? [y/N]Answer: NTip: 10 messages have been suppressed, use --verbose to show them.Error: Aborting installation due to build failureimlsp using gitT Verifying dependencies for [email protected] Info: Dependency on jsonschema@>= 0.2.1 already satisfied Verifying dependencies for [email protected] Info: Dependency on ast_pattern_matching@any version already satisfied Verifying dependencies for [email protected] Info: Dependency on asynctools@any version already satisfied Verifying dependencies for [email protected] Installing [email protected] Building nimlsp/nimlsp using c backend /tmp/nimble_153465/githubcom_PMunchnimlsp/src/nimlsppkg/baseprotocol.nim(2, 8) Warning: imported and not used: 'logger' [UnusedImport] /tmp/nimble_153465/githubcom_PMunchnimlsp/src/nimlsppkg/suggestlib.nim(11, 8) template/generic instantiation of `mImport` from here /tmp/nimble_153465/githubcom_PMunchnimlsp/src/nimlsppkg/suggestlib.nim(7, 14) Error: cannot open file: /usr/nimsuggest/nimsuggest.nim Prompt: Build failed for '[email protected]', would you like to try installing 'nimlsp@#head' (latest unstable)? [y/N] Answer: N Tip: 10 messages have been suppressed, use --verbose to show them. Error: Aborting installation due to build failure

I also tried to the solutions suggested  and , but nothing worked. I moved the (setq lsp-keymap-...) line outside (and before) use-package. I also used :config (define-key lsp-load-map...) in my use-package block. But none of them worked.

Not sure how much this might help, but lsp-mode has lsp-yaml-select-buffer-schema and lsp-yaml-set-buffer-schema commands to pick schema from a list or set from a URI. Checking the source of them might give some hints about how the same could be implemented in eglot?

Beyond that you might as well embrace the suck and install autex with a language server: https://emacs-lsp.github.io/lsp-mode/

Smart completion these days is done primarily through LSP. eglot is fairly minimal but built-in as of 29, also available via GNU Elpa. lsp-mode is another option with more integrations and a bit more fleshed out.

lsp-mode: https://github.com/emacs-lsp/lsp-mode/issues/2080

Are you running emacs-29? It has numerous speed-ups compared to emacs-28 and older versions, many of them coded by Mattias Engdegård, e.g. commit def6fa4246. I have a fresh build of emacs-29 running on Linux and a new mac with an M1 CPU, and it's stupid fast. I don't use the native-comp feature. I rarely notice any hesitation or slowness. I don't use Elpy. I do use lsp mode.

Since you are doing code development, the first things to go for would be setting up your emacs packaging (installing use-package and melpa (use-package's documentation covers this) so you have more packages to choose from (do be careful to not just pick things willy nilly but research them a bit first)) and then setting up lsp-mode. lsp-mode lets you use LSP servers for the specific programming languages you work with in a somewhat unified fashion. You then need to install and setup the LSP servers for the languages you use, and possibly install language specific Emacs packages as support (note, Emacs has builtin functionality for many).

And first of all, I'm trying to understand, how is it connected to https://github.com/emacs-lsp/lsp-mode? I'm sure, that existed lsp implementations already parse source code. Why TreeSitter?