<p>All the Unix filters i know rarely fails, they just process <code>stdin</code> until they encounter the EOF, so i don't see the need to be that conservative.</p>

<p>I think the most user-friendly behavior would be discarding stderr completely and do the replacement in any case.<br>
If the user is unhappy with the replacement he/she can still undo it with a single command.</p>

<p>I've also tried <code>sh -c '/usr/bin/bc 2>/dev/null'</code> as suggested, but it does not seem to work.</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/issues/1118#issuecomment-231456345">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe/ABDrJ--UDgyA1Qu7WjI9u7HPV4JTtFFJks5qTqqQgaJpZM4JGRv0">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ16FlLgHo6dlBNsAbwQ0ALRZ3TUsks5qTqqQgaJpZM4JGRv0.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/issues/1118#issuecomment-231456345"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>