Show HN: Vim-like text editor in go. (LSP, TreeSitter, Themes)

Re:Show HN: Vim-like text editor in go. (LSP, TreeSitter, Th... by paddy_m on Thursday June 12, 2025 @06:55PM (#44264079)

That's a lot of code for a toy project, impressive commitment!

How does the VIM family generally handle extensibility?

Do you have any unique takes there?

I use Emacs, and I get how emacs does it (smallish runtime for text display and lisp interpreter, everything else in lisp).

[ Parent | on HN ]

Re:Show HN: Vim-like text editor in go. (LSP, TreeSitter, Th... by fgonzag on Friday June 13, 2025 @10:04PM (#44273729)

Traditionally (classic vim), horribly well. Fully extensible, but Vimscript is quirky to say the least.

Recently (neovim), delightfully. It just uses Lua and exposes APIs for absolutely everything.

[ Parent | on HN ]

Re:Show HN: Vim-like text editor in go. (LSP, TreeSitter, Th... by andrew_bbb on Saturday June 14, 2025 @01:53PM (#44277726)

Hey Paddy. Vim uses horrible vimscrip, neovim - cool lua. I have two idea for plugins: - 1. Rich events system on backend side. e.g. write golang code for plugins, recomplire editor. done. pros: good performance, autocomplete for plugins out-of-the-box. golang. cons: feedback loop is lonfer. recomplier, restart, repeat. - 2. Use lua. pros: fast development cycle. cons: harder to implement. two languages, communication overhead.

I also use Emacs, btw.

[ Parent | on HN ]

Re:Show HN: Vim-like text editor in go. (LSP, TreeSitter, Th... by icar on Sunday June 15, 2025 @04:42PM (#44284824)

You could consider WASM.

[ Parent | on HN ]