Popsicle VS xi-editor

popsicle

I'd use Etcher primarily due to it simplicity, and it's available on several platforms. Popsicle next if you have a linux system.

There is also a project called Popsicle that lets you image multiple drives https://github.com/pop-os/popsicle

https://github.com/pop-os/popsicle worked for me across multiple systems

AppImage: https://github.com/pop-os/popsicle/releases

Rust projects that need more recognition imo are: * Zola * Spot * Popsicle * Plume

https://github.com/system76/firmware-open/files/6728054/galp5-disable-me.zip https://github.com/system76/firmware-open/files/6728055/lemp10-disable-me.zip -> Extract .img file, flash to a USB flash drive with Popsicle (https://github.com/pop-os/popsicle, btw it is installed in pop os as "usb flasher") , and then boot from the USB flash drive to flash the firmware.

Not sure how you get a raw request to that URL. It's a directory. This weekend I've made the CLI translatable as well. Translations are stored in https://github.com/pop-os/popsicle/tree/master/i18n

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...