When it comes to Go editors (IMO Go is perfect language for such editors) I also need to mention https://anvil-editor.net
It's ACME inspired, open source (although I don't think it's published on GitHub, one needs to download), and it's actually quite nice to work with due to its composability).
Takes some time to use, but it's really fun to use for stuff like ad-hoc documentation, completion etc. Oh, and it also has REST API for interaction with external tools so you can Go (pun intended) crazy on it.
I know you haven't planned ahead, but have you thought about extensibility? One of the main benefit of Vim and Emacs is that the user can customize it exactly to fit their needs, and the large ecosystem that exists around that. I suppose it would be smart for any new editor nowadays to be able to leverage existing plugins from other ecosystems, rather than starting from scratch.
Like the color schemes! I myself am working on an app called https://vimgolf.ai to make it easier to learn how to use vim. Might copy what you did with copying the color schemes from the helix code editor.
Love it! I'm a big fan of code terminal ui code editors. Currently for that purpose Helix is my daily driver.
Will try out yours shortly and don't let anyone discourage you! Keep going. Adaption will follow.
This is incredible! It looks beautiful, with a perfect type of minimalism, and supports modern features out of the box. Very good job! If I used terminal editors anymore, I would certainly use this!
Show HN: McWig – A modal, Vim-like text editor written in Go
(github.com)139 points by andrew_bbb 12 June 2025 | 13 comments
Comments
It's ACME inspired, open source (although I don't think it's published on GitHub, one needs to download), and it's actually quite nice to work with due to its composability).
Takes some time to use, but it's really fun to use for stuff like ad-hoc documentation, completion etc. Oh, and it also has REST API for interaction with external tools so you can Go (pun intended) crazy on it.
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).
Awesome project man. I'll have to spend some time exploring the code base when I have time.
I know you haven't planned ahead, but have you thought about extensibility? One of the main benefit of Vim and Emacs is that the user can customize it exactly to fit their needs, and the large ecosystem that exists around that. I suppose it would be smart for any new editor nowadays to be able to leverage existing plugins from other ecosystems, rather than starting from scratch.