Jonathan Daugherty

To get a bit more specific on my proposal: * Make `/help` and `/help ` launch `man` * Make the help UI rendering code emit `troff` instead of a `brick`...

Another benefit of this approach: it makes it possible to generate a static man page to be put into the releases and repo to be usable for the default Matterhorn...

Since I was thinking of it: https://cmd.inp.nsk.su/old/cmd2/manuals/unix/UNIX_Unleashed/ch08.htm

@benjaminselfridge and I talked and the first step on this is to start working on a `troff` Haskell package to represent and serialize Troff documents.

Thanks, @benjaminselfridge!

While merging `develop` into the branch mentioned above just now, I discovered that `pandoc` is licensed under the GPL. That's bad because it means that if we were to use...

Thinking about this a bit more, I think just moving to [commonmark](https://hackage.haskell.org/package/commonmark) as the help text representation would probably be adequate. (I.e. extended Markdown.) From Commonmark we can produce HTML...

As a follow-up note on `commonmark`, there's also [commonmark-pandoc](https://hackage.haskell.org/package/commonmark-pandoc) which allows Markdown to be parsed into the Pandoc types. That depends only on `pandoc-types`, which is BSD-licensed. If we're going...

Looking into this more, I'm not sure how much benefit `commonmark` can provide. What it gives us is an HTML renderer, but *only* if the markdown input text is parsed...

I'm going to close this as dormant and part of a large effort that would need to be undertaken. We don't get enough requests for this to make it a...