4 ms·
> Run ucm init to initialize a Unison codebase in $HOME/.unison Ugh, this conflicts with my favorite file sync tool: https://www.cis.upenn.edu/~bcpierce/unison
by sdfjkl 5y ago
> Run ucm init to initialize a Unison codebase in $HOME/.unison
Ugh, this conflicts with my favorite file sync tool: https://www.cis.upenn.edu/~bcpierce/unison/ https://www.cis.upenn.edu/~bcpierce/unison/
- carapace 5y agoUnison (the file sync tool) is so awesome!
- zepearl 5y agoIt's great when it works, but different versions of <OCAML? and/or Unison?> on different hosts/VMs screw it up. I never understood the real reason why (but I never really investigated, lazy) => it's a pity.
- pchiusano 5y agoFYI you can do ‘ucm -codebase /someplace/else init’ to initialize a codebase in another directory. And then ‘ucm -codebase /somewhere/else’ to launch ucm. Also I’m not sure what Unison the file sync tool stashes in .unison or how it uses that directory but there might not be any conflict. UCM will just create a .unison/v2/unison.sqlite3 file.