Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Your comment makes it sound like RMS tried to stop it from getting merged into core.

Whereas the mail in your link just shows that RMS wanted to discuss whether it should have a generic "LSP" name or not (i.e. retain the original eglot name), which is a valid concern.



I actually feel the name is the worst part of eglot, it's not like it's a generic polyglot thing, it's really an lsp mode, it'll be one more of those hard to discover Emacs features because of this.


Here's him suggesting delaying the release until January: https://lists.gnu.org/archive/html/emacs-devel/2022-10/msg00...


Again, it's because of naming consistency, which one can agree with or not.

My issue was your comment just pointed at RMS without specifying what he was being boneheaded about this time, which I thought was a little flamebaity.


There only two hard things in computer science:

This first is naming things

The second is getting emacs-lisp to hold hands with the rest of the world




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: