unison/unison-src/transcripts/fix4280.output.md

``` unison
foo.bar._baz = 5

bonk : Nat
bonk =
  use foo.bar _baz
  _baz
```

``` ucm

  Loading changes detected in scratch.u.

  I found and typechecked these definitions in scratch.u. If you
  do an `add` or `update`, here's how your codebase would
  change:
  
    ⍟ These new definitions are ok to `add`:
    
      bonk         : Nat
      foo.bar._baz : Nat

```
Update the transcripts with `cmark` `cmark`’s pretty-printer matches our output pretty well, with a few differences: - it puts a space between the fence and the info string for in code blocks; - it prefers `-` over `` for bulleted lists (as do I) and it indents them; - it `\`-escapes certain chars very conservatively; - it prefers indented/unfenced code blocks if there is no info string; and - it prefers `` over `_` (unlike any sane person). This also shows how the change fixes a number of issues: - fix2158-1.output.md also illustrates how this change fixes #1809; - alias-many.output.md and input-parse-errors.output.md show how fenced code blocks without an info string would use the beginning of the content as the info string; - transcripts-round-trip/main.output.md shows how output blocks for generated `unison` stanzas (which could contain nested fenced blocks) might not have long-enough fences; and - error-messages.output.md and generic-parse-errors.output.md show how Unison errors were reported on the wrong line number (and thus the printed error lines were also incorrect). 2024-07-10 17:46:18 +03:00			``` unison
Add transcript demonstrating #4280 2024-01-30 23:11:44 +03:00			`foo.bar._baz = 5`

			`bonk : Nat`
			`bonk =`
			`use foo.bar _baz`
			`_baz`
			```

Add a space before code block info strings This is for consistency with the `cmark` style. Now the blocks we still pretty-print ourselves will match the bulk of them that `cmark` produces. 2024-07-10 19:17:15 +03:00			``` ucm
Add transcript demonstrating #4280 2024-01-30 23:11:44 +03:00
			`Loading changes detected in scratch.u.`

fix #4280 2024-01-30 23:21:52 +03:00			`I found and typechecked these definitions in scratch.u. If you`
			do an `add` or `update`, here's how your codebase would
			`change:`
Add transcript demonstrating #4280 2024-01-30 23:11:44 +03:00
fix #4280 2024-01-30 23:21:52 +03:00			⍟ These new definitions are ok to `add`:

			`bonk : Nat`
			`foo.bar._baz : Nat`
Add transcript demonstrating #4280 2024-01-30 23:11:44 +03:00
			```