Sigilante

Working! ``` > ..~1.3_.~2.4_ «.~1.3 .~2.4» > ..1.3_.2.4_ > ..~~1.3_.~~2.4_ ≺.~~1.3 .~~2.4≻ > ..~~~1.3_.~~~2.4_ ⋘.~~~1.3 .~~~2.4⋙ ```

What remains: - [x] special case parsing - [x] `@lms` parsing

Question: shouldn't auras _not_ nest by default? ``` > `@lvs`..1.2_.3.4_ > `@lvd`..1.2_.3.4_ «.~102.40003957748414» ``` (that latter one should be impossible)

> These look like they're not ASCII. Hoon literals need to all be ASCII. That's an output convention I'm using for the pretty-printer, easy to revert to `

I'm adding in `@lmd` as well for completeness, then a cleanup pass.

That's fine. I'll leave some kind of export wrapper to `tape`, maybe to CSV or similar then.

Status update: - I've changed the pretty-printer format to just match the atom syntax. - I've written the parser for @lmd type. All pieces work separately, and the whole works,...

Hmm, the plot thickens. ``` > =test -build-file /===/sys/hoon/hoon > (lago-base-md:so:test [[1 1] ".~1_.~2__.~3_.~4__"]) [p=[p=1 q=19] q=[~ u=[p=~[~[.~1 .~2] ~[.~3 .~4]] q=[p=[p=1 q=19] q=~]]]] ```

So my guess right now is that there is some sort of collision with the @lmd format that breaks compilation. `!:` doesn't narrow it down, it's just a flat `[7...

~master-morzod said that it's breaking on parsing `..ride` so that's the next rabbit hole for this... closer. I may have to revisit the atom literal syntax for matrices if this...