Re: Differences that aren't ?

On Sun, 15 Jun 2025 at 07:22, "Head Geek (伟思礼)" <[email protected]> wrote:
>
> Apparently unison reads composed characters on one side and decomposed characters on the other and considers them the same.

This is true. The documentation also somewhat mentions this for the
preference "unicode". It states: "When Unison runs in case sensitive
mode, this flag only makes a difference if one host is running Mac OS
X. Under Mac OS X, it selects whether comparing the filenames up to
decomposition, or byte-for-byte." What it doesn't say explicitly is
that under other OS the case sensitive comparison is always
byte-for-byte. At least that's according to my quick reading of
https://urldefense.com/v3/__https://github.com/bcpierce00/unison/blob/master/src/case.ml__;!!IBzWLUs!SvFeQBWtO2GTrtZCcV0pNDrIcOrjLnHV5sMHTmuXFScMXDrcGGIVSccYHO2n8tyz--vIUZfydbW9v7o7seb9Rg$ 

When creating new dirs/files, Unison in macOS uses the composed form
if the "unicode" preference is set. macOS may or may not change what
bytes are actually written to the disk.

To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].