Thanks for the pointer!

My quibble1 with this approach is that they tried to rewrite Vim rather than, as firenvim does, actually embedding Neovim in the application.

So, like, if I'm editing Github Discussions, I get all my Markdown mode enhancements including properly defined wrap margins, customized spell checking with my customized dictionary, enhanced syntax hacks, you name it. It's all there :)

It's one of the advantages of actual Neovim as opposed to some vimmish mode approximation. And it's made possible by Neovim's client/server nature.

But again, very cool thanks for the pointer!

Right? Mine too :) Where I work we use Github Discussions a LOT. In fact I work in them to write up my daily activity log/standup report.

And WOW does composing long form text in browser text boxes get OOOOLD :)

@dpiponi Couldn't agree more! The big reason I think is that a LOT of the operating systems and platforms we use are designed to maximize profit rather than create a great user experience.

There's no reason at all why EVERY application ever written can't say "Hi I need a text box please" which would then make a call to the generic text box maker. You like Neovim? Great! You get that. Want Sublime/VSCode/Emacs/whatever? No problem. You get that instead. Don't care and just want a generic textbox? You get the default. No problemmo.

It really could be that easy. We've even gone a long way towards doing things like this before.

Just ask anyone who ever used #AREXX back on the #amiga. But heck, we can't even get the tiniest bit of standards or agreement in the open source community!

Each Linux desktop flavor has its own varying degrees of abandoned scriptable component framework, but nobody bothers with them because they're all radically different.

:)