user-configured preferences for symbolic vs alphanumeric term names

[ceedubs]

There are many higher priorities, but I just had this thought about a neat little feature that Unison makes pretty easy.

There are many battles about "symbolic" names (like <>) vs alphanumeric names (like combine). If both <> and combine exist as term names for a referenced hash, maybe the pretty printer could use a user-configured "symbolic" preference to determine which name to show.

This is similar in spirit to #499 but I think that it's much lighter weight and could be implemented with or without a general pluggable syntax.

Something similar could be done for ASCII vs Unicode operators (ex: ≡ vs ===).

[nmcb]

lifting from this (already elevated top-down -and might i say, meta-) level of cooperative dialogue on an ux-ui topic: which codebase/namespace should be responsible for the rendering of ligatures from "symbolic" names: a unison code-base, the ucm, or a gpu spec even - perhaps. ref screenshots.

layout (edited)