Do you have anything to improve remote (SSH?) development? Meaning: the frontend is GPU accelerated, and that is great, but if you are fetching pages from the server instead of caching the buffers and intelligently fetching the LSP (or whatever language backend is used) updates, we are bottlenecked by the SSH connection latency
Nice project! Curious why build a new front end instead of fixing (?) the behaviour in upstream Kakoune? I think the original author’s still working on Kakoune
the original kakoune is just cli; the binary has a json ui client option to allow communication with the kakoune server, with the intent of any gui or alternative client being separated from the kak binary/repo. that being said, this seems entirely ai-generated :( i had planned to write a kakoune frontend that supported rtl text (arabic in particular) + unicode, prop fonts, etc., and might look to how some things were done here, but i'd be blown away if this didn't have a great number of rough edges w.r.t. line wrap, unicode, rtl, etc. ...
To possibly save some clicks for others: repo did not exist a month ago and claude use seems extensive. Chances are it will be gone/unmaintained by July!
Do you have anything to improve remote (SSH?) development? Meaning: the frontend is GPU accelerated, and that is great, but if you are fetching pages from the server instead of caching the buffers and intelligently fetching the LSP (or whatever language backend is used) updates, we are bottlenecked by the SSH connection latency
Nice project! Curious why build a new front end instead of fixing (?) the behaviour in upstream Kakoune? I think the original author’s still working on Kakoune
the original kakoune is just cli; the binary has a json ui client option to allow communication with the kakoune server, with the intent of any gui or alternative client being separated from the kak binary/repo. that being said, this seems entirely ai-generated :( i had planned to write a kakoune frontend that supported rtl text (arabic in particular) + unicode, prop fonts, etc., and might look to how some things were done here, but i'd be blown away if this didn't have a great number of rough edges w.r.t. line wrap, unicode, rtl, etc. ...
I'm guessing part of it is design philosophy: mawww doesn't want splits embedded in the editor, for example.
To possibly save some clicks for others: repo did not exist a month ago and claude use seems extensive. Chances are it will be gone/unmaintained by July!