I created basic Snap package for Kakoune. It’s avaliabe on snap branch at my GH.
Disclaimer:
I’m not big fan of Snaps. They are supported on all major distributions tho. That is a lot of potential users who could use Kakoune without compiling it manually.
It needs some testing. I haven’t created snap before so I don’t know If I packaged it correctly.
For now it needs to be built manually. I guess Snaps could be build on Travis and uploaded to GH releases. I’m not sure how Snap store submission process looks like (It’s a classic Snap so it would require manual verification), also I’m not sure if it’s worth a hassle.
What about AppImage or Flatpack? I don’t know much about these package systems, since I don’t need them, but quick look at this table makes me think that AppImage is more appropriate format. Maybe I’m wrong though.
Okay I give up - Snaps are pile of garbage, builds break randomly, documentation is incomplete and often out of sync with actual state of things and I don’t feel like it’s worth the trouble.
In case anybody is interested, I build a static binary, install it in to a subfolder in $HOME. I can rsync this folder to any linux host and run kakoune with all the plugins and everything. For me using kakoune means that I quickly loose my vim skills, so if I need an editor on a remote for longer periods I switch to kakoune.
I’m using sshfs for that. Basically mounting remote server to some directory, that using local installation of any editor to work with those files. But I think it would be nice if Kakoune had something like Emacs TRAMP
I have had terrible experience with sshfs and similar. I tend to work on mid-sized projects (10s of thousands of files) and whenever I do something like ripgrep or run certain tools, I always get into a weird place with lag and frustration.
Do you have any tricks for making this work well, more aggressive caching, etc?