-
-
Notifications
You must be signed in to change notification settings - Fork 805
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add documentation on Wezterm plugins #6177
Comments
If you'd like to make a start on this, the way to go about it is:
eg:
Once you've added that entry to
(docker is required to run that script) That will build the docs (takes a few seconds), then run an http server and print out a URL that you can open in your browser and then navigate to your new page. As you make changes to doc files, the docs will be rebuilt and the browser will automatically reload. |
Thanks @wez . I'll give it a burl |
WIP for review TODO: 1. Add a section to the reference for `wezterm.plugins` 2. Create a plugin starter project wez#6177
What page or section of the docs have an issue?
Needs a new section?
Describe the issue
Wezterm plugins have no documentation. It would be useful to have some.
Initially we can use paraphrse the content of the original change at e4ae8a8
However we need to add more details on how to update plugins and discover where they are located.
A more substantial section is also needed to explain how to setup a plugin development project.
The text was updated successfully, but these errors were encountered: