emacs-overlay VS lsp-mode

The project uses this overlay: https://github.com/nix-community/emacs-overlay

What that means is if something is broken in Emacs, the community will fix it, and all I need to do is run `nix flake update` to grab the latest commit and then `nix run .#build-switch` to alter my system. Easy.

Thanks for the heads-up on the 404s! I've fixed those links.

In re: to org-agenda, I don't use that as much anymore. But I heavily, heavily using org-roam w/ org-roam-dailies everyday to build my own networked graph of notes. For tasks, nowadays I just use simple docs for projects and Asana to keep a catalog of everything.

Im a newish NixOS user, Ive used it like 20 times before but always quit because I couldnt debug errors, trying not to give up for the 20th time this time lmao; so Ive been trying to learn how to use overlays & flakes for a couple of days now. The ones I want to use/enable are: - Emacs-Overlay - Spicetify-Nix

Nix offers the same advantage through the use of emacs-overlay. Besides, Nixpkgs contains more Linux packages than any other distros. Depending on the user's needs, Nix is another option.

You can use this overlay to get the latest https://github.com/nix-community/emacs-overlay

Depending on your goals, emacs-overlay is also worth a look.

{ pkgs ? import {} }: ((import (builtins.fetchTarball { url = "https://github.com/nix-community/emacs-overlay/archive/master.tar.gz"; })) pkgs pkgs).emacsGit

One option is to install Nix and use emacs-overlay.

You can install Nix on your mac and use https://github.com/nix-community/emacs-overlay/, which supports all the existing tree-sitter-based major modes OOB.

Its great to see both eglot and tree-sitter being merged. However, I am unhappy about the state of 'emacs configurations/distributions' right now. I have been using Doom Emacs, but the development is pretty much stalled there [0], and I don't think there is any distribution that is keeping up with these cutting-edge features (compared to the NeoVim ecosystem, let's say). Somehow it feels like I was seeing a lot more activity about Emacs configurations two-three years ago.

> Compile EmacsLisp files ahead of time

Ooh, this is interesting. Hoping to see a derivation in https://github.com/nix-community/emacs-overlay soon.

[0] I am not complaining though as Doom was the main author's personal config from the get-go. I am just pointing out a void.

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?