Greg Pfeil

> I'm about ready to merge this, but still just trying to wrap my head around and document the new organization. Let me know if I have this right. >...

> And this PR mainly is to let us reduce how many files we've got, and also to reduce friction in submitting transcripts with bug reports. Yeah, I would say...

I still have to resolve some conflicts, but I pushed a change that tidies up the blank lines in UCM blocks. The one thing I’m unsure of is that it...

> Probably having no blank lines is better in `ucm :hide`, but it's not a big deal; I'm eager to merge the PR if only because it continues to accumulate...

> Can you confirm what's the "right" way to add transcripts in new and open PRs now? I think I tried just throwing one `fix-blah.md` into `transcripts/idempotent/` and that didn't...

> Can you confirm what's the "right" way to add transcripts in new and open PRs now? I think I tried just throwing one `fix-blah.md` into `transcripts/idempotent/` and that didn't...

There are related changes suggested in #5199, in terms of what flags should exist.

It seems like there’s [a](https://talk.commonmark.org/t/generic-directives-plugins-syntax/444) [light](https://pandoc.org/MANUAL.html#extension-fenced_code_attributes) [consensus](https://michelf.ca/projects/php-markdown/extra/#fenced-code-blocks) toward something like ````markdown ```ucm {hide=all} scratch/main> builtins.merge ``` ```unison {error=intentional file="skritch.u"} foo = bar ``` ```` A starting point for discussing the...

In #5394, I added both `:failure` and `:incorrect` to the set of info string tags. It made me wonder if perhaps `result` in the proposal above should be split into...

To get back to basics, all that is really required for this is inserting a space, so that ````markdown ``` unison:hide:error file ```` becomes ````markdown ``` unison :hide:error file ````...