The \? command already printed help for all available commands, but it also should support subcommands for options and variables. This PR implements them and adds autocomplete.
Things to look at:
Options are always printed to stdout, ignoring the handler's settings.
All variable names and descriptions are kept in lists but converted to a string, it might as well be just one big string. I did not attempt to refactor the code so they're all defined in a single place.
I did not attempt to address #379 since the README is big enough already and variables are also already referenced in a few places. I'm not convinced copying the output of \? variables there would help.
Resolves #384 and partially resolves #258
BTW I noticed the release plugin gathers release notes from PRs so I'll try to avoid committing important changes directly to the default branch.
The
\?command already printed help for all available commands, but it also should support subcommands for options and variables. This PR implements them and adds autocomplete.Things to look at:
\? variablesthere would help.Resolves #384 and partially resolves #258
BTW I noticed the release plugin gathers release notes from PRs so I'll try to avoid committing important changes directly to the default branch.