Khionu Sybiern

Hrmm... maybe similar enough to where it could be implemented the same way? Maybe similar enough to be redundant? Though there is a distinction between docs and explanations. Explanations would...

There is prior art for this, namely [rustc](https://doc.rust-lang.org/rustc/command-line-arguments.html#--explain-provide-a-detailed-explanation-of-an-error-message). I'm not familiar with Breezy, but Git is definitely a tool I think that could benefit from an explain command as well....

Not a suggestion I would want to block on, but it might be nice to deviate from the `remote: ` format, maybe box the message.

> Idk about boxing Yeah, that was just what first came to mind.

Oh, I didn't know about those git commands. Having checked them out, the git help subcommands demonstrate what I'm talking about wrt different forms, even though they use the same...

I could see strong value in having one of these commands mirror `jj help`, but at the same time, I can see wanting to bundle more than just doc-command pairings....

That is really nifty, and I'd love to work on that kind of thing.

My thoughts, in no particular order, and assuming no particular prior knowledge of the reader: - The flexibility that templates can provide is often very high. Sometimes that flexibility is...

Composing object literals shouldn't be a problem. In the case of structuring output, what I suggested would mean `string | List`, and a `json` function could take a nested map...

I didn't mean to suggest heterogeneous lists, I'm actually not a fan of those in general. I mispoke in my last, "s/return/take/ a nested map". > Mercurial has a nasty...