Funny timing of this post. This past weekend, I dedicated myself to creating a comprehensive set of tools for integrating Pijul seamlessly into Emacs. This includes collaboration features through org-mode, which I believe will be refreshing. I'm eager to share it with the community shortly. For fellow Emacs & Pijul enthusiasts, keep an eye out!
As probably the person in the entire world who has been wanting this for the longest, thank you!
Please share on Pijul's Zulip, and ask for any help you may need.
I'll try to allocate some time this weekend and also sign up for Zulip. Currently, I'm considering the best way to distribute it. Given that users are familiar with use-package and MELPA, it seems I may need to incorporate Git as well.
I'm just starting to explore Pijul, to be honest. My interest was sparked when I revisited an old Haskell project and remembered using Darcs years ago, which led me to research Pijul. I'll be able to share more insights in a few weekends, once the remote communication components of vc-pijul are established.
Darcs has rebase & Pijul doesn’t which can really help ergonomics for fixups or if you do a lot of WIPs that need amending. Darcs also has a send command for easily mailing patches to others. Darcs also lets you override the diff output which is compatible with decades-old tooling rather than something bespoke. Pijul despite better performance, an awesome user identity system, & channels is still not a Darcs replacement IMO. That isn’t to say folks shouldn’t use or follow the Pijul project (they should) more than it is to say one should still feel okay using Darcs today too as it’s still getting updates & has features Pijul doesn’t; what’s wrong is folks calling Pijul a ‘successor’ as if the Darcs project had died. You could still use Darcs in 2024.
