As did I, maybe a PR to remove it from Geany? [ducks] grin
While I realize that was written in jest, from a user perspective, I would prefer that auto close be removed from Geany and improvements redirected toward the auto-close plugin.
* The Geany implementation doesn't do anything that can't be done in a plugin. * The preferences dialog is complicated. It's difficult to find features I know exist. Removing features that are implemented in plugins would make other features easier to find. * The auto-close plugin is clearly named, so users who want it are likely to find it. Chances are good that people who have seen the plugin manager know that the auto-close plugin exists, but don't know about the Geany implementation. * The plugin implementation is more capable than the Geany implementation. * Even if the Geany implementation is improved, it will be disabled by people who *still* think it's broken or who want the more advanced features that the plugin provides.
From the perspective of someone who has looked at the source (but is *not* a developer)... removing auto close from Geany would make the source easier to understand and work with, while the plugin ensures that no functionality is lost.