<p>As <a href="https://github.com/codebrainz" class="user-mention">@codebrainz</a> said, it's to handle filename encoding implicitly.  We could duplicate this (it's used in several places), even with just a mere copy to ensure it uses the same libc, but it should probably only be done if we find an actual issue with this.  AFAIK we never got bitten by this, so I'd rather assess the actual possibilities before going ahead and copying some code over.</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/1271#issuecomment-255514237">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ_EEY3G3RCPVeZdnnSaS1tmuz2U2ks5q2cTGgaJpZM4KdtAF">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ9up5qdZccn9jnq8PEQItmAK6aDiks5q2cTGgaJpZM4KdtAF.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/1271#issuecomment-255514237"></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","title":"geany/geany","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"}},"updates":{"snippets":[{"icon":"PERSON","message":"@b4n in #1271: As @codebrainz said, it's to handle filename encoding implicitly.  We could duplicate this (it's used in several places), even with just a mere copy to ensure it uses the same libc, but it should probably only be done if we find an actual issue with this.  AFAIK we never got bitten by this, so I'd rather assess the actual possibilities before going ahead and copying some code over."}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/1271#issuecomment-255514237"}}}</script>