Kurtis Rader

This is another issue likely to be affected by any change made as a result of this issue: https://github.com/elves/elvish/issues/1503.

We already have code written to extract the Elvish var and command documentation and convert it to HTML using `pandoc` (see website/tools/md-to-html). Building on that to generate plain text embedded...

@crinklywrappr and @hanche: Supporting introspection of builtins has already been requested, see #680.

@hanche and @crinklywrappr, I decided to start working on this. Introspection of builtins as requested by issue #680 might be useful for providing a simple one line command "usage" help...

See issue #738 for some important background regarding the current situation. I was hoping to leave the text in Markdown format and have Elvish directly render the Markdown. However, importing...

@crinklywrappr, Thanks for the feedback. Plugins require Cgo and don't work on Windows. So that is not a viable solution. Requiring the user to feed the `help` output through another...

Something not already discussed is what should be the result of `help unknown-command`. Should it explicitly fail? Should it run `man unknown-command`? Something else?

I've been chipping away at implementing a `help` command by focusing on the transformation of Github flavored Markdown to raw text suitable for display in a terminal using ANSI X3.64...

> What do you think about using the edit module to make the help searchable & scrollable? Maybe bind to Ctrl+h? That is a good question and proposal but outside...

> I am under the impression the help command is non-interactive. It's interactive in the sense the output is meant to be displayed on a terminal and read by a...