Showing command hint on error is much harder in v2

[alecthomas]

Showing command hint on error is much harder in v2

[alecthomas]

Hi there.

Believe it or not, this will get much simpler in v2, but it's not quite ready yet. v2 splits parsing and execution into multiple passes, building an intermediate structure that contains the result of the parse. This contains the exact flags, commands and arguments that the parser sees, so you will not need to use heuristics to figure out what the args[]string contains.

However, there are some things holding up progress:

1. I'm trying to figure out a better way to display help. As you mention, dumping the full list of commands is a bit overwhelming. My current thought is to just dump each level of the tree as each command is encountered.
2. I want to expose the internal command tree structure publicly, and use text/template to generate the help from that structure. This would allow users to override the help in any way they like. This looks like it will require a fair bit of work though.

So, basically, it's not ready yet, but it should hopefully be much better than v1.

[xealot]

Having tried what must be dozens of these types of libs having a text template is something I've always wanted. It seems like a very natural approach and I'm somewhat surprised it's not more common.

I agree that if you can descend into the subcommands and show relevant help it would be much more intuitive.

[xealot]

👍 NOICE!