Hacker News new | ask | show | jobs
by embedding-shape 156 days ago
> Near all editors have a VS code plugin compatible layer

Huh, never heard about this before, and took a look at emacs and vim/neovim as those are the two most popular editors I know of, neither can run VS code plugins, that'd be crazy if true.
2 comments
WorldMaker 156 days ago
If you count LSP (Language Server Protocol) as a VSCode plugin-compatible layer as LSP was built and standardized by the VSCode team (so many do), then Emacs and Neovim are full of VSCode-compatible plugins today. One of Neovim's selling points right now over bare Vim is better/more direct LSP support.
link
embedding-shape 156 days ago
Ah, if LSP is what parent meant with "VS code plugin compatible layer" then what you say makes sense, I personally also moved from vim to neovim mainly because of better LSP support.

But I understood "VS code plugin compatible layer" to mean there is something that lets you run VSCode plugins with other editors, which is what I haven't seen anywhere (yet?).

link
iLemming 156 days ago
Except Emacs doesn't have "plugins". They are called "packages" and not plugins for specific reasons - they are more like libraries than plugins. In Emacs, one can change/override the behavior of any function (built-in or third party) with some enormous flexibility not easily achievable in other editors.
link
freedomben 156 days ago
Very long time vim/neovim user here. I can't remember names atm and can't check, but I have definitely seen plugins that run a headless or subset of VScode in the background to pull info from it. It may not be super common, but it is being done
link
devsda 156 days ago
You are probably referring to language support plug-ins.

IIRC, debugger support for java needed a component from one of the official plug-ins.

link