JonP

Here's an example of each format so you have a better idea of what it looks like: EDIT: links were wrong https://github.com/urbit/urbit/blob/jon/doccords/pkg/arvo/lib/dprint.hoon#L58-L64 https://github.com/urbit/urbit/blob/jon/doccords/pkg/arvo/lib/dprint.hoon#L66-L69

So there isn't a real problem with "wrong doccords" if someone goes through and fixes them all. I'm probably the right person to do it. So maybe "wrong doccords" is...

Per conversation with @zalberico we're going to try to divide and conquer the comment formatting in parallel with a swarm of folks. My opinion that having only one longform doccords...

Here is a simple outline of the proposed spacing style for comments that live on their own line. Informal comments are any comments thrown away by the whitespace parser. Formal...

`+swel` is from `lib/pill.hoon`, all I did was move it into `hoon.hoon.` I'm a bit confused about the CI issue - I'm guessing its trying to build a pill with...

I renamed `+swel` to `+sock` but CI is still complaining about there being multiple `+swel` arms, even though there are no longer any arms named `+swel` in the whole branch....

Oops, I misread `+slew` as `+swel`. Nevermind.

I renamed `+slew` to `+sock`, but it looks like `lull.hoon` already has a `$sock`, though it appears to be completely unused. I picked "sock" since it has a similar meaning...

Ideas for colonizing namespace over here... ``` vase arm | (trap vase) arm slap | beat slop | bump slam | bang slap+slop | bash (currently +swel) ``` Surprisingly, none...

FYI I only picked `#` for the dojo help syntax since I was told `#` has been used just to mean "placeholder" in the past.