[Unison-hackers] list of unison issues / todo list

[Benjamin C. Pierce]

> Anyway, perhaps if somebody with
> write access to Unison could indicate agreement with some or all of
> the items on the list, then that would be a first step to getting them
> worked on.

Yes, these all seem like worthwhile improvements.  If someone wants to implement them, I’ll be happy to consider patches.

Best,

   - Benjamin



> 
> Hello Unison Hackers,
> 
> I've been using Unison successfully in spite of the path.ml bug (which
> perhaps only affects single-file roots?). It mostly works fine for me,
> but I figured that it might be useful for me to make a list of minor
> problems that I run into, in case someone decides to continue with
> Unison development. I'm attaching my list to this message and also
> made a 'gist' on github.com as an experiment:
> 
> https://gist.github.com/70dfb7ff01d86fd8f300
> 
> I'm not sure how helpful that "gist" URL is... Also, I'm not sure how
> helpful it is to make a TODO list, I hope it encourages rather than
> discourages further work on Unison. Anyway, perhaps if somebody with
> write access to Unison could indicate agreement with some or all of
> the items on the list, then that would be a first step to getting them
> worked on.
> 
> Thank you!
> 
> Frederick
> 
> P.S. I wrote this without first reading TODO.txt in the Unison
> tarball:
> 
> https://webdav.seas.upenn.edu/viewvc/unison/trunk/src/TODO.txt?revision=506&view=markup
> 
> but I don't see any of the issues I've identified in there...
> <unison-todo.md>_______________________________________________
> Unison-hackers mailing list
> Unison-hackers at lists.seas.upenn.edu
> http://lists.seas.upenn.edu/mailman/listinfo/unison-hackers