<blockquote>
<p>I believe (without testing) that you could replace <code>auto</code> with <code>yes</code> <a href="https://github.com/geany/geany-plugins/blob/1.32.0/build/scope.m4#L3">here</a>.</p>
</blockquote>
<p>Almost, yet it's actually misleading and the second value is whether to <em>enabled</em> or not the plugin, so it would be changing this to <code>no</code>.</p>
<p>However, I wonder whether if we want to force people to make a decision we shouldn't actually go hackier than that and add e.g. an option <code>--yes-i-am-sure-i-want-to-enable-the-debugger-plugin-and-i-know-about-the-glib-hanging-issue</code>, so that people that went the extra mile of adding <code>--enable-debugger</code> because they are packaging it have to notice and take action.</p>
<p>Anyway… I'm don't really know what to do here, because on one hand I agree that it's fairly bad not to have the fix that already exist for a while, but I'm not 100% sure it's totally trivial (yet it seems to just be less optimized when it kicks in)</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-plugins/issues/688#issuecomment-365747424">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJwI-sJX_jkjkrviXPAsrpdCAKHW8ks5tU0z4gaJpZM4R4Y_y">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ-mXo1vhLMoQXvfHx0jw5VVFMRTtks5tU0z4gaJpZM4R4Y_y.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/geany/geany-plugins/issues/688#issuecomment-365747424"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/geany/geany-plugins","title":"geany/geany-plugins","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/geany/geany-plugins"}},"updates":{"snippets":[{"icon":"PERSON","message":"@b4n in #688: \u003e I believe (without testing) that you could replace `auto` with `yes` [here](https://github.com/geany/geany-plugins/blob/1.32.0/build/scope.m4#L3).\r\n\r\nAlmost, yet it's actually misleading and the second value is whether to *enabled* or not the plugin, so it would be changing this to `no`.\r\n\r\nHowever, I wonder whether if we want to force people to make a decision we shouldn't actually go hackier than that and add e.g. an option `--yes-i-am-sure-i-want-to-enable-the-debugger-plugin-and-i-know-about-the-glib-hanging-issue`, so that people that went the extra mile of adding `--enable-debugger` because they are packaging it have to notice and take action.\r\n\r\nAnyway… I'm don't really know what to do here, because on one hand I agree that it's fairly bad not to have the fix that already exist for a while, but I'm not 100% sure it's totally trivial (yet it seems to just be less optimized when it kicks in)"}],"action":{"name":"View Issue","url":"https://github.com/geany/geany-plugins/issues/688#issuecomment-365747424"}}}</script>