I have written two plugins. It's easy enough to add one to Leo via a pull request. That alone does not put it into LeoPyRef, but the plugin will be available anyway since it will be in Leo's plugins directory. IIRC, @ekr added one of them to LeoPyRef on his own, and added the other after I noticed it wasn't there and asked him to.
On Friday, January 7, 2022 at 1:56:20 PM UTC-5 [email protected] wrote: > What is the cooperative way to write a plugin? The documentation for > writing plugins mentions leoPy.leo, but it is not in the repository - does > one copy LeoPyRef.leo to leoPy.leo and make changes there? If so, how does > one contribute back? Adding a plugin to LeoPyRef.leo works, but does a > rewrite/reordering of that file when using the development version of Leo. > Is there a particular version of Leo one uses to edit LeoPyRef.leo, or is > there some other workflow? > > A pull request to support elixir @doc is available for consideration, but > it may not be appropriate for all or have deficiencies such as a lack of > unit tests. Perhaps it could be a plugin that monkey-patched class AtFile. > > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/f181cfd0-79e7-4261-b052-255a0155056en%40googlegroups.com.
