Hi, folks.
Lex, thanks for your comments. I have heard before about
GeanyLua's future being uncertain, and I did email the
list suggesting that I would be willing to be an
emergency backup maintainer. Ie I don't generally have
the time, but given a choice between fixing a severe
problem and losing the plugin, I'd step up.
Just tonight I've uploaded another script to the Geany
Wiki, for surrounding the current selection with
brackets, tags, etc. That fulfils another item from the
plugin wishlist. It took about 40 lines (including
comments and debug lines) and 15 minutes.
I strongly urge that GeanyLua be retained. I think that
it and GeanyPy are the way of the future for plugin
development, and since GeanyPy isn't available
precompiled, GeanyLua is the only out-of-the-box
candidate for developing a useful feature (that would
normally involve a plugin) in an hour or less. The
documentation is clear; the API is simple but effective;
there's no boilerplate (no import statements, no class
declarations, no metadata, just code); deployment is
just a matter of copying the script into the geanylua
directory and restarting/rescanning; and it integrates
nicely with the keybinding system.
Anyone who wants to develop a plugin, or wishes for a
feature that some other editor has, should consider
GeanyLua. It might not do what they need, but if it
does, they'll be able to do it within an afternoon. I'm
already maintaining 6 different Lua-powered features
(some of which involve multiple scripts), with a 7th to
be uploaded soon, and it's easy. |