[Unison-hackers] [unison-users] Unison aborts all the synchronization after a permission issue

[Benjamin Pierce]

> But this is mainly a UI issue.  For the text UI, I use a difference
> arrow "--?->" to indicate a partial synchronization (feel free to
> change it if you have a better idea).  The "show details" key will
> list all update detection errors.  For the GTK UI, I use an orange
> arrow and their is a new "Details" button on the tool bar to get the
> list of errors.  For both UIs, the number of partially transferred
> directories is also reported after transport.  The Mac OS UI does not
> allow partial synchronization yet.

--?-> and the orange arrow both seem a little too subtle -- I don't  
think most people will notice.

What about err-> for the text UI?

>>> - Overwriting (or deleting) a directory with deep errors will fail
>>> during propagation.  We should either forbid the user from
>>> attempting to overwrite such a directory, or relax the checks in
>>> function Update.checkNoUpdates. (Or implement partial deletion.)
>>
>> Although we've already got a lot of switches, I wonder if we should
>> add one more to control this.  But I think the default should be the
>> more convenient and slightly less safe way.  Partial deletion seems
>> confusing.
>
> At the moment, I have not addressed this: deleting a directory with
> deep errors will fail during propagation.  Maybe this is good enough?
> Unison will fail late, but the user still has a clear explanation of
> what went wrong.

Yes, this is probably OK for the moment.  Deletion is pretty fast, so  
making people redo it from scratch is not a big deal.

     - B