Added new Docs page to describe Plugins.

[alecthegeek]

TODO:

1. Add a section to the reference for wezterm.plugins
2. Create a plugin starter project NOTE: Seperate project at https://gitlab.com/alecthegeek/wezterm-plugin-mgr

#6177

[MLFlexer]

There are some details described in the docs included in #5820 about the names derived from the url, which might be useful for this PR

[alecthegeek]

There are some details described in the docs included in #5820 about the names derived from the url, which might be useful for this PR

Thanks fot the review @MLFlexer -- much appreciated.

I assume you are referring to the URL encoding to derive the plugin dir?

I did consider that, but decided it was easier to leave it out. It's not really needed as users and developers can use list function to get the plugin location.

Also one less thing to update if it changes in the future.

Is there some use case I have not considered?

Cheers

[MLFlexer]

Thanks fot the review @MLFlexer -- much appreciated.

I assume you are referring to the URL encoding to derive the plugin dir?

I did consider that, but decided it was easier to leave it out. It's not really needed as users and developers can use list function to get the plugin location.

Also one less thing to update if it changes in the future.

Is there some use case I have not considered?

Cheers

The only thing I as a plugin developer could have benefited from was knowing how the directory name was computed, as it is useful for adding sub-modules to the plugins via. adding the plugin directory to the lua path. However thinking more about it, I agree that it should be left out, as it does not provide a good solution to the sub-module problem anyways.

I'm also of the belief that the docs should be keeps simple, stupid, as to keep them readable and to not confuse others. So I agree with leaving it out.

[MLFlexer]

Looks good, there are some very nice examples and tips which would have helped me when developing plugins 😄