@elextr yes, I know but maybe someone knows why this happened, will try to find myself also, but how I understand it is better to move to Peasy plugin (just compiled) with Libpeas support. Is Geanylua planned to be removed from Geany plugins ?

Well clearly nobody needs it urgently enough to be willing to support it.

There is no specific policy for removing plugins from the plugins collection, in fact sometimes the threat of removal results in individual PRs to keep an almost dead plugin going (usually something like moving to a new library version as happened to Geanylua and whatever changes that needs). But that is individual PRs, it often does not result in a rush of offers to take up ownership of the plugin.

I don't know how many geanylua issues there are, but in the past many scripts have worked just fine, guess they didn't use your troublesome function. So that makes it even harder to let it go, even if its no longer perfect. I suspect it will limp along until either some major issue occurs or the oldest version of lua that is provided by distros is not compatible with the newest version of lua that geanylua uses. Or a white knight thunders in on a massive horse and takes over maintenance. :horse_racing:

Merging Peasy to Geany-plugins is an issue because Peasy uses its own compile and build system, not Autotools. And also if the creator does not want to include it in Geany-plugins thats entirely their right, and its not unusual. Of course "somebody" could make a copy of Peasy and include it in Geany-plugins, thats GPL, but having done that for a plugin in the past myself, I would say its not a happy position to be, even if the originator didn't mind.

Unfortunately for Peasy it appears only Arch AUR seems to supply it as a package, not Ubuntu and dependants or Fedora (dunno about Debian, the package search is down, but its likely that Ubuntu would have it if Debian did). So Peasy is not really an option for those who don't compile stuff even though its a technical improvement.