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

``` unison

lexicalScopeEx: [Text]
lexicalScopeEx =
  parent = "outer"
  inner1 = let
    child1 = "child1"
    inner2 : [Text]
    inner2 = let
      child2 = "child2"
      [parent, child1, child2]
    inner2
  inner1

```

``` 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`:
    
      lexicalScopeEx : [Text]

```
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
transcripts: Don’t trim spaces from Unison blocks This was making it impossible to write a transcript replicating #5179. 2024-10-07 09:41:50 +03:00
Avoid another variable-renaming let case 2021-08-04 17:31:54 +03:00			`lexicalScopeEx: [Text]`
cleanup 2024-04-15 03:01:39 +03:00			`lexicalScopeEx =`
Avoid another variable-renaming let case 2021-08-04 17:31:54 +03:00			`parent = "outer"`
cleanup 2024-04-15 03:01:39 +03:00			`inner1 = let`
Avoid another variable-renaming let case 2021-08-04 17:31:54 +03:00			`child1 = "child1"`
			`inner2 : [Text]`
cleanup 2024-04-15 03:01:39 +03:00			`inner2 = let`
Avoid another variable-renaming let case 2021-08-04 17:31:54 +03:00			`child2 = "child2"`
			`[parent, child1, child2]`
			`inner2`
			`inner1`

			```

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
Avoid another variable-renaming let case 2021-08-04 17:31:54 +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.`

Avoid another variable-renaming let case 2021-08-04 17:31:54 +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`:

			`lexicalScopeEx : [Text]`

			```