@js361014 it's not _my_ philosophy per se, just a sort of convention. Examples of plugins which improve, extend, or replace builtin features, which one could equally argue ought to be in core: * [Addons](https://plugins.geany.org/addons.html) has quite a few little things. * [Autoclose](https://plugins.geany.org/autoclose.html) fixes Geany's not great brace closing to make it more like other editors. * [Automark](https://plugins.geany.org/automark.html) fixes Geany's "Mark All" feature to work more like other editors. * [Commander](https://plugins.geany.org/commander.html) extends traditional menus/bindings with a "palette" thing like VSCode, Sublime, and others have builtin. * These ones try to fix/improve Geany's project management: - [Geanyprj](https://plugins.geany.org/geanyprj.html) - [ProjectOrganizer](https://plugins.geany.org/projectorganizer.html) - [Workbench](https://plugins.geany.org/workbench.html) * [Multiterm](https://plugins.geany.org/multiterm.html) tries to fix/improve the builtin terminal. * [TreeBrowser](https://plugins.geany.org/treebrowser.html) tries to fix/improve the builtin FileBrowser, which is itself a plugin (shipped with core). * [VimMode](https://plugins.geany.org/vimode.html) replaces/extends the builtin keybindings/navigation to be more like Vim.
The pattern/tradition here, is that if you don't like something in Geany core (especially if it's a matter of taste, and optional anyway, like this PR), then you make a plugin, and ideally add it to the [Geany-Plugins](https://github.com/geany/geany-plugins) project, or even try to get it added as a core plugin. I just don't see how the feature/functionality of this PR is any different than many plugins. -- 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/pull/2220#issuecomment-515713464
