As I noted above, Geany and current plugins are C, they have to be compiled, they are not an interpreted language like Python that sublime uses, so Geany plugins cannot be just downloaded and run.
Geany is an entirely volunteer project, when someone contributes a capability for non-C plugins things may change (there are external projects that do that, but they have not been contributed to the main project, its entirely up to the external project to make that decision). Most Linux distributions have Geany and the Geany-plugins collection available to install using their standard package management tools (but note such packages are not made by this project directly) and Windows and OSX builds are available in the downloads page so its not normally necessary to compile them yourself unless you are developing a new plugin. > however, some plugins does not have the "configure" and "Makefile" present to > do that Where are you getting those plugins from? All the Geany-Plugins collection should have `makefile.am` and `Makefile` is created by `configure` which is created for the whole collection by `autogen.sh` if you use the git repository see [here](https://github.com/geany/geany#installing-from-a-git-clone), or should exist if you use the tarball see [here](https://github.com/geany/geany#installing-from-a-release-tarball). This is the standard autotools build methodology. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2782#issuecomment-819338332
