mirror of
https://github.com/unisonweb/unison.git
synced 2024-09-11 02:25:39 +03:00
0031542faf
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.
57 lines
1018 B
Markdown
57 lines
1018 B
Markdown
We were seeing an issue where (it seemed) that every namespace that was visited during a propagate would get a new history node, even when it didn't contain any dependents.
|
|
|
|
Example:
|
|
|
|
``` unison
|
|
a = "a term"
|
|
X.foo = "a namespace"
|
|
```
|
|
|
|
``` ucm
|
|
scratch/main> add
|
|
|
|
⍟ I've added these definitions:
|
|
|
|
X.foo : ##Text
|
|
a : ##Text
|
|
|
|
```
|
|
Here is an update which should not affect `X`:
|
|
|
|
``` unison
|
|
a = "an update"
|
|
```
|
|
|
|
``` ucm
|
|
scratch/main> update
|
|
|
|
Okay, I'm searching the branch for code that needs to be
|
|
updated...
|
|
|
|
Done.
|
|
|
|
```
|
|
As of the time of this writing, the history for `X` should be a single node, `#4eeuo5bsfr`;
|
|
|
|
``` ucm
|
|
scratch/main> history X
|
|
|
|
Note: The most recent namespace hash is immediately below this
|
|
message.
|
|
|
|
|
|
|
|
□ 1. #das1se4g2i (start of history)
|
|
|
|
```
|
|
however, as of release/M1i, we saw an extraneous node appear. If your `ucm` is fixed, you won't see it below:
|
|
|
|
``` ucm
|
|
scratch/main> history #7nl6ppokhg
|
|
|
|
😶
|
|
|
|
I don't know of a namespace with that hash.
|
|
|
|
```
|