I've used neovim for a couple years now, but had trouble using it professionally because package managers often break in certain environments like docker containers or remote servers. Rather than go with the graybeard option of using plain vim in unusual environments, I experimented with not using any package managers and just directly controlling the environment.
This worked surprisingly well, so I reworked my dotfiles into a shareable format - which is freak.nvim
Hope other vim appreciators enjoy =)
Yep - I do it in the scripted version.
The main challenge is dealing with dynamic data in a way that won't mess up merge conflicts. Sort order is the main one and it's pretty bad because a merge conflict will result in multiple tickets with the same sort order. The best way I could think of in the slightly less strict paradigm of the plainban project was to keep a
data.ymlfile for each column which records the sort order of tickets by storing them as a list of uuids and making their name a comment. That way it's very easy to keep track of the order of tickets on merge conflict in a way that's not possible in a central data source like a csv file.Will change current, less merge-friendly implementation to this when I get to it.