Lets move the build tool discussion elsewhere rather than polluting this FR
which has pointed to your plugin, but users have to compile it themselves.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1282#issuecomment-2080655894
You are
I'm new to meson, but switched my preview plugin over to it. One way it could
be done...
* Each plugin would have its own `meson.build` and `meson.options` that can be
built independently.
* The files should require minimal changes between plugins.
* Building and testing individual
@xiota it would be great if you are willing to be maintainer for those plugins,
in that case simply make a PR changing the MAINTAINERS file with your details
for them. Geanylua is orphaned so thats no problem, and codebrainz has not
contributed to Geany or Geany-plugins for many years so
The "freeze" isn't by explicit policy, but is what has effectively happened to
plugins that aren't of primary interest to developers with commit privileges.
If it helps facilitate bug fixes and minor improvements, I'm willing to be
(interim) maintainer for the Markdown and GeanyLua plugins. I
Geany plugins doesn't "freeze" changes, but yes it does slow them down with
reviews etc.
The benefit though is that it gets access to the Geany packagers to put it in
distros if its part of the plugins collection.
The real problem is plugins where there is no maintainer for the plugin to
Submitting a plugin to the geany-plugins collection would require freezing the
code, even for bug fixes. I'm not willing to do that for a plugin I actively
use, so never submitted it.
--
Reply to this email directly or view it on GitHub:
@manueljordan The procedure would be... to build and install it yourself. It
uses webkit2gtk-4.0 or webkit2gtk-4.1. If you use 4.1, it will conflict with
some other plugins: webhelper, markdown, updatechecker, geniuspaste. They are
being updated, but I wouldn't expect rebuilds on most
As @xiota says, the plugin is still a work in progress, but I'm sure they would
be happy to have someone testing it.
When it is complete they may wish to add it to the plugins collection, in which
case they need to raise a PR to add it, like #1331 or #1337, or they may decide
to keep it
Sounds great and thanks for your efforts. I am not sure what is the procedure
of the official project about this specific situation
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1282#issuecomment-2078247569
You are receiving this because you
I have a plugin that shows a [preview](https://github.com/xiota/geany-preview)
of several lightweight markup types... It needs refactoring... but works well
enough.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1282#issuecomment-2077438240
Thanks for the reply. I will try with them too. Thank You.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1282#issuecomment-1766503676
You are receiving this because you are subscribed to this thread.
Message ID:
Geany has some support for asciidoc built in.
If "somebody" was willing to contribute a plugin for Geany to provide a preview
it would probably be accepted.
Note that the plugin for Vscode is provided by `asciidoctor.org` so maybe you
could ask there.
--
Reply to this email directly or view
12 matches
Mail list logo
