4 ms·

Despite the last-minute efforts of RMS: https://lists.gnu.org/archive/html/emacs-devel/2022-10/msg00029.html https://lists.gnu.org/archive/html/emacs-devel/2022

• sph 4y ago
  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.
  • bigbillheck 4y ago
    Here's him suggesting delaying the release until January: https://lists.gnu.org/archive/html/emacs-devel/2022-10/msg00181.html https://lists.gnu.org/archive/html/emacs-devel/2022-10/msg00...
    • sph 4y ago
      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.
      • vfclists 4y ago
        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
  • didibus 4y ago
    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.
• db48x 4y ago
  For those who don't follow the mailing list, it was actually Stefan who proposed renaming it. RMS agreed, saying that 'eglot-mode' didn't tell him anything about what it does (and that's even after recognizing the root "glot", which not everyone gets).