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

See [this ticket](https://github.com/unisonweb/unison/issues/849).

``` unison
x = 42

> x
```

``` 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`:
    
      x : Nat
  
  Now evaluating any watch expressions (lines starting with
  `>`)... Ctrl+C cancels.

    3 | > x
          ⧩
          42

```
fix #849 2019-10-07 22:55:01 +03:00			`See [this ticket](https://github.com/unisonweb/unison/issues/849).`

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
fix #849 2019-10-07 22:55:01 +03:00			`x = 42`

			`> x`
			```

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
fix #849 2019-10-07 22:55:01 +03:00
Adding a message for when ucm started reloading changes 2023-12-22 14:55:24 +03:00			`Loading changes detected in scratch.u.`

fix #849 2019-10-07 22:55:01 +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:`

			⍟ These new definitions are ok to `add`:

type based search uses suffixed input + regenerated transcripts 2019-11-14 00:57:51 +03:00			`x : Nat`
update transcripts 2020-04-08 21:25:19 +03:00
fix #849 2019-10-07 22:55:01 +03:00			`Now evaluating any watch expressions (lines starting with`
			`>`)... Ctrl+C cancels.

			`3 \| > x`
			`⧩`
			`42`

			```