vscode-intelephense VS lsp-mode

I'm going to use intelephense to show the minimal configuration needed to setup a language server in Neovim.

This is the most important extension to install for PHP support. It provides a fast language server that adds code completion, go to definition, formatting, and more. You can also purchase a license at Intelephense, which I highly recommend. It adds some additional features like renaming symbols and other code actions.

I'm quite happy with Emacs, coming from PhpStorm, using intelephense.com premium. I highly recommend.

Follow this guide to configure and add PHP Intelephense.

Furthermore, depending on which integrated development environment (IDE) you use, your editor detects the strict_types and warns you inside the editor before running your code. For example, I use the Intelephense extension inside Visual Studio Code, which warns me about wrong parameters before I run the code, like so:

Helix should use Intelephense by default, so if you install that, it should work out of the box. You can find installation instructions here 🙂

PhpStorm is probably the best solution if the license cost doesn't matter to you. Though I think that Visual Studio Code with either Intelephense or Devsense is incredibly Intelephense or Devsense is incredible competent for the price.

I'm using LSP + Intelephense. Works in 90% of cases.

My IDE — VSCode with intelephense doesn't have "bad/incorrect" auto completion for array_reduce. It gives phenomenal auto-completion and min-reference documentation that changes several times as I progress through writing the line of code - only showing the reference relevant for the argument I'm typing now.

More generally - With a little work you can get VScode to have decent intellisense for php and there are some laravel plugins to enable click on strings to access views and stuff. (For a little cash you can get the refactoring features of INTELEPHENSE in vscode which IMO is worth the small cost if you're mostly VScoding php, although not really laravel specific).

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.

I love emacs for the fact that I can use it with many different languages. I get my IDE like features (auto-complete, linting, formatting etc.) from lsp-mode. You can configure emacs by writing elisp in your .emac dotfile in your home directory. Here is my messy config file. The general tactic is to copy snippets from other people. I don't know a good starting point for configuring, but maybe this video can give you a glimpse of what it is like. Picking a feature and getting it working was what helped me when I first started out with emacs. evil-mode was the first thing I installed, because I like vim.

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?

Debugging (kind of an IDE feature) is a little harder. Out of the box, Emacs can at least debug emacs-lisp (with built-in features) and C (via gdb integration). Beyond that, take a look at dap-mode for other language options. Similarly, take a look at lsp-mode or eglot for code completion, more advanced linting, etc.