News for hackers. Stuff that matters.

A comment on The values of Emacs, the Neovim revolution, and the VSCode gorilla. Parent comment

Re:The values of Emacs, the Neovim revolution, and the VSCod... by thom on Sunday January 17, 2021 @10:55AM (#25811693)
Have you found that other extension authors have this in mind? Most extensions don't seem to be built with hooks in mind so you're kinda stuck with either the existing extension or rolling your own. There also aren't very good primitives for most use cases because of this. I assume VSCode will get there though.
[ Parent | on HN ]
Re:The values of Emacs, the Neovim revolution, and the VSCod... by qppo on Sunday January 17, 2021 @12:43PM (#25812848)
VSCode extensions are driven through "commands" that are exposed through the package.json of the plugin (which can be parsed by other plugins if you wanted) and issuable through another plugin, or using a task (this is kind of annoying though and not a first class use of tasks).
[ Parent | on HN ]