Clk, Why Not Doing Parsing in Customcommands

Fleeting

clk, why not doing parsing in customcommands

I wanted for some time make customcommands put their docstring in a separate file. Then I realized I want the docstring construction to be as dynamic as clk is. In my case, the docstring is generally not a static string, but a dynamic string constructed out of several shell commands. That way, you get powerful suggestions and completion out of it.

Permalink