fix: Improve duplicated help from clk.plugin.* commands

[sjoubert]

No description provided.

[Konubinix]

Thank you :-). May I ask if you actually used plugins?

[sjoubert]

Thank you :-). May I ask if you actually used plugins?

No. I found the help mismatch mostly by browsing commands and looking at their help.

Not yet?
I'm trying to see what plugins are and how they work, so far I've created one, it is loaded but no luck getting a new command being recognized (the plugin test only deals with the load part).
This is mostly curiosity so far, unless I discover a nice potential in them I don't think I have a use case for now.

[Konubinix]

Hi, Sylvain Joubert ***@***.***> writes: [...]

I'm trying to see what plugins are and how they work, so far I've created one, it is loaded but no luck getting a new command being recognized (the plugin test only deals with the load part).

A long long time ago, plugins where used to create new commands. But now, clk has several builtin ways to add new commands, one of which is described here https://clk-project.org/doc/use_cases/dynamic_parameters_and_exposed_class.html. If you want to try a parricular way of creating commands, please come forward. I would be very glad to hear of it, and possibly extend the documentation (and clk ?) to show how to do this.

[Konubinix]

In fact, this is at the heart of the clk cli. By itself, it is useless. But once you add commands, it becomes more and more awesome. I currently have 605 commands in my global setup, without using plugins. I actually don't know of any practical use case involving plugins. Hence my initial question :-).

[sjoubert]

I ended up having a marginal use case for a custom command, I did it with the relevant command (clk.command.{create,...}). I don't think plugins will be useful.