Emacs Eglot / LSP Not Working

How to fix it

Try these in order — the most common fix is first.

1. 1. Fix the PATH Emacs sees

   Copy steps
   1. Install exec-path-from-shell from MELPA
   2. Call (exec-path-from-shell-initialize) early in init
   3. Restart Emacs completely
   Did this fix it? Yes No

2. 2. Check the server is installed

   Copy steps
   1. Run the server in a terminal, for example pylsp or typescript-language-server --stdio
   2. Install it with your language's package manager
   Did this fix it? Yes No

3. 3. Set the server command explicitly

   Copy steps
   1. Customize eglot-server-programs
   2. Use the full absolute path to the server
   Did this fix it? Yes No

4. 4. Read the events buffer

   Copy steps
   1. Open the *EGLOT events* buffer
   2. Look for the actual error from the server
   Did this fix it? Yes No

Symptoms

M-x eglot says it cannot find or start a server, no completion or diagnostics appear, or it works in a terminal Emacs but not in the GUI app.

Why it happens

• GUI Emacs on macOS does not inherit your shell PATH
• The language server is not installed
• No entry in eglot-server-programs for the major mode
• PATH exports placed in the wrong shell startup file

This guide also covers

• emacs eglot not working
• emacs lsp-mode not starting
• eglot server not found

Other GNU Emacs errors

• Emacs Failed to Verify Signature (ELPA Package Install Error)
• Emacs Slow Startup
• Emacs Native Compilation Warnings Popping Up
• Emacs Slow or Freezing With Large Files
• Emacs macOS Operation Not Permitted (Documents, Desktop, iCloud)
• Doom Emacs Errors After Update or doom sync
• Emacs package-install Fails (Package Not Found or Archive Error)