Greg Pfeil

Ah, this one is a perfect example of https://github.com/unisonweb/unison/pull/4962#discussion_r1617594164 `dependents` returns `Reference`s as its numbered args (but prints based on the `HashQualified Name`). Then `delete.term` expects a name of some...

It actually had to do with `unison:added-by-ucm` stanzas, and was fixed in #5290.

I think I discovered the intended semantics in another issue from @ceedubs: #3314. The description there implies that `transcript.fork` is meant to run the transcript on a copy of whatever...

Ok, that makes sense. There are also tradeoffs with how `-c`/`-C` are interpreted when `transcript*` is used. It can be nice to make options orthogonal, so that `-c` has the...

I would like to see some options like `cabal-plan why-depends --dot --tred dep [deps…]`, taking advantage of the existing implementations of the `tred` and `dot` subcommands after having pruned the...

I just ran into this, and wanted to make the workaround/fix more explicit in case anyone else still has an ancient .cabal/config around. Basically, the `remote-repo` field in Cabal config...

I don’t understand – Current and Root always need to be directories. What does the second version buy you?

Two suggestions relative to @ceedubs concrete proposal: First, > ## Codebase > > Currently this is stored in `~/.unison`, though the `-c` and `-C` flags can be used to override...

Hrmm, I might be able to do something like that. The data type is also a pattern functor for recursion schemes, so it's used like ```haskell newtype HFix f a...

This is issue #10, which I had actually fixed in my fork ages ago, but somehow never pushed a PR for. In any case, I endorse this PR … a...