unison/unison-src/transcripts/add-test-watch-roundtrip.output.md

``` unison
test> foo : [Test.Result]
foo = []
```

Apparently when we add a test watch, we add a type annotation to it, even if it already has one. We don't want this to happen though\!

``` ucm
scratch/main> add

  ⍟ I've added these definitions:
  
    foo : [Result]

scratch/main> view foo

  foo : [Result]
  foo : [Result]
  foo = []

```
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 two transcripts a failing transcript `add-test-watch-roundtrip` and an ok-looking transcript for `update-test-watch-roundtrip`; though noting that the test gains a type signature. 2023-11-21 17:44:33 +03:00			`test> foo : [Test.Result]`
			`foo = []`
			```

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			`Apparently when we add a test watch, we add a type annotation to it, even if it already has one. We don't want this to happen though\!`
Add two transcripts a failing transcript `add-test-watch-roundtrip` and an ok-looking transcript for `update-test-watch-roundtrip`; though noting that the test gains a type signature. 2023-11-21 17:44:33 +03:00
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
Replace '.' references with scratch/main 2024-06-12 01:22:09 +03:00			`scratch/main> add`
Add two transcripts a failing transcript `add-test-watch-roundtrip` and an ok-looking transcript for `update-test-watch-roundtrip`; though noting that the test gains a type signature. 2023-11-21 17:44:33 +03:00
			`⍟ I've added these definitions:`
why do the transcripts' white space change? 2023-11-22 05:52:57 +03:00
Add two transcripts a failing transcript `add-test-watch-roundtrip` and an ok-looking transcript for `update-test-watch-roundtrip`; though noting that the test gains a type signature. 2023-11-21 17:44:33 +03:00			`foo : [Result]`

Replace '.' references with scratch/main 2024-06-12 01:22:09 +03:00			`scratch/main> view foo`
Add two transcripts a failing transcript `add-test-watch-roundtrip` and an ok-looking transcript for `update-test-watch-roundtrip`; though noting that the test gains a type signature. 2023-11-21 17:44:33 +03:00
			`foo : [Result]`
			`foo : [Result]`
			`foo = []`

			```