<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=37348338" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/js361014">@js361014</a> it's not <em>my</em> philosophy per se, just a sort of convention.</p>
<p>Examples of plugins which improve, extend, or replace builtin features, which one could equally argue ought to be in core:</p>
<ul>
<li><a href="https://plugins.geany.org/addons.html" rel="nofollow">Addons</a> has quite a few little things.</li>
<li><a href="https://plugins.geany.org/autoclose.html" rel="nofollow">Autoclose</a> fixes Geany's not great brace closing to make it more like other editors.</li>
<li><a href="https://plugins.geany.org/automark.html" rel="nofollow">Automark</a> fixes Geany's "Mark All" feature to work more like other editors.</li>
<li><a href="https://plugins.geany.org/commander.html" rel="nofollow">Commander</a> extends traditional menus/bindings with a "palette" thing like VSCode, Sublime, and others have builtin.</li>
<li>These ones try to fix/improve Geany's project management:
<ul>
<li><a href="https://plugins.geany.org/geanyprj.html" rel="nofollow">Geanyprj</a></li>
<li><a href="https://plugins.geany.org/projectorganizer.html" rel="nofollow">ProjectOrganizer</a></li>
<li><a href="https://plugins.geany.org/workbench.html" rel="nofollow">Workbench</a></li>
</ul>
</li>
<li><a href="https://plugins.geany.org/multiterm.html" rel="nofollow">Multiterm</a> tries to fix/improve the builtin terminal.</li>
<li><a href="https://plugins.geany.org/treebrowser.html" rel="nofollow">TreeBrowser</a> tries to fix/improve the builtin FileBrowser, which is itself a plugin (shipped with core).</li>
<li><a href="https://plugins.geany.org/vimode.html" rel="nofollow">VimMode</a> replaces/extends the builtin keybindings/navigation to be more like Vim.</li>
</ul>
<p>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 <a href="https://github.com/geany/geany-plugins">Geany-Plugins</a> project, or even try to get it added as a core plugin.</p>
<p>I just don't see how the feature/functionality of this PR is any different than many plugins.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/geany/geany/pull/2220?email_source=notifications&email_token=AAIOWJ2D4LZPBWX6QQ52I6TQBSZ2VA5CNFSM4IEKN7D2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD26STOA#issuecomment-515713464">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAIOWJ32VYLC4YSHZCERQKLQBSZ2VANCNFSM4IEKN7DQ">mute the thread</a>.<img src="https://github.com/notifications/beacon/AAIOWJ5ZYEXEJR7D536FLFTQBSZ2VA5CNFSM4IEKN7D2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD26STOA.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/geany/geany/pull/2220?email_source=notifications\u0026email_token=AAIOWJ2D4LZPBWX6QQ52I6TQBSZ2VA5CNFSM4IEKN7D2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD26STOA#issuecomment-515713464",
"url": "https://github.com/geany/geany/pull/2220?email_source=notifications\u0026email_token=AAIOWJ2D4LZPBWX6QQ52I6TQBSZ2VA5CNFSM4IEKN7D2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD26STOA#issuecomment-515713464",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>