What should be expected behavior of --html builtin option ?

[siteshwar]

All builtins support --html option that outputs a html help page on terminal. This is not very helpful. I would expect it to automatically show help page in browser. We need something similar to what fish does with help command. Comments ?

[krader1961]

I concur. Having an option to emit HTML output is borderline useless and greatly complicates the getopt() implementation. It's one of the reasons I'd like to see the documentation switched to something like Sphinx. Producing a HTML version of the documentation should be done at build time not run time. See #507.

[krader1961]

Any reason not to close this as a dup of #507? Once we resolve that issue we will be able to automatically generate a HTML version of each command's documentation. Which can then be used by a hypothetical help command such as the fish implementation. I also want to see the DocOpt based documentation/flag parsing via optget() replaced with the borg standard getopt_long() so that we can eliminate the src/lib/libast/misc/optget.c module.

[krader1961]

Once we extricate the documentation from the source and switch to a more modern markup language this becomes moot. So closing as a duplicate of #507.