neovide VS xi-editor

- have a “graphical” user interface: https://github.com/neovide/neovide

The process above works fine, though, depending on your setup and project, you might appreciate the benefits of a lean editor like Neovide. So, let’s see how to configure Neovim to run with Unreal Engine.

EDIT: I found this just now -> https://github.com/neovide/neovide/issues/1902 and disabling relative line numbers does indeed make the problem more or less disappear.

Not Emacs, but perhaps https://github.com/neovide/neovide will be of interest to you.

im certainly not a programmer , but NVIM with SOME gui like neovide it looks amazing and great,

Yes it is neovide: https://github.com/neovide/neovide

iTerm2, since Terminal.app doesn't support 24-bit colors and I used Neovim for some time. I now use Neovide for Neovim, so all I use iTerm2 for now is the UI (I have a theme I like, plus dark mode actually works).

I feel this smooth cursor should be everywhere by default, as it gives so much better user experience. I have also been looking for a solution for neovim as well, but based on what I know, only Neovide has support for this. And most plugins do smooth scrolling only, rather than smooth cursor.

Was confused until I realised I'd confused Zed, with Xi[1] which is also rust based, and which incidentally has a frontend called "Xim"..

Also there's a wiki-editor (like Tomboy[2]) called "Zim"[3].

[1] https://github.com/xi-editor/xi-editor

Project site linked from the GitHub[0] is https://xi-editor.io. Linked doc is a mirror of this[1], which was afaik originally written by Raph Linus.

[0]: https://github.com/xi-editor/xi-editor

[1]: https://xi-editor.io/docs/rope_science_01.html

> thing that gets deleted when you hit backspace

Is there a canonical source for this part, by the way? Xi copied the logic from Android[1] (as per the issue you linked downthread), and I vaguely remember that CLDR had something to say about this too, but I don’t know if there’s any sort of consensus here that’s actually written down anywhere.

[1] https://github.com/xi-editor/xi-editor/pull/837

This is pretty much how copy-on-write ropes work. Check out xi-rope, Ropey or crop, they're all built using B-trees and implement the behavior you described.

Helix is awesome, though once Lapce (spiritual successor to Xi editor) gets the Helix/Kakoune editing model, I may have to jump ship

Home (xi-editor.io)

Maybe take a look at the Xi editor (https://xi-editor.io/) (written in rust I think) that uses a client server architecture.

Have a look at what Lapce uses. The editor is coming along nicely, and iirc, they use the Xi editor as a plug-in.

Raph Levien posted a retrospective about using CRDT’s for collaborative editing in xi-editor here [1]. His conclusion is

“I come to the conclusion that the CRDT is not pulling its (considerable) weight. When I think about a future evolution of xi-editor, I see a much brighter future with a simpler, largely synchronous model, that still of course has enough revision tracking to get good results with asynchronous peers like the language server.”

[1]https://github.com/xi-editor/xi-editor/issues/1187#issuecomm...