<p>I'd like to keep the notice because the command path in the template is the user input and so rather likely to be the cause. However, there is no "template path" here. The context is a custom command (<a href="http://geany.org/manual/#special-command-wildcard">http://geany.org/manual/#special-command-wildcard</a>) in a template has failed.</p>

<p>So maybe rather: "Hint: errors in the command path in the template are a common cause of problems" ?</p>

<p>Checking for <code>ENOENT</code> probably causes more problems because we first had to parse and somewhat interpret the command.<br>
In an ideal world, the error message from the subsystem would properly describe what went wrong and so we would not need to guess. But at least on Windows, error messages are sometimes rather random text than helpful, IMHO.</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/1166#issuecomment-243063113">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ943Esd3eFzOkZMxkIlQIkWXHhIGks5qkpf8gaJpZM4JegxR">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJyvQk7Ei4B-_gIx9fzDgo8fge6B_ks5qkpf8gaJpZM4JegxR.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/pull/1166#issuecomment-243063113"></link>
  <meta itemprop="name" content="View Pull Request"></meta>
</div>
<meta itemprop="description" content="View this Pull Request 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":"@eht16 in #1166: I'd like to keep the notice because the command path in the template is the user input and so rather likely to be the cause. However, there is no \"template path\" here. The context is a custom command (http://geany.org/manual/#special-command-wildcard) in a template has failed.\r\n\r\nSo maybe rather: \"Hint: errors in the command path in the template are a common cause of problems\" ?\r\n\r\nChecking for `ENOENT` probably causes more problems because we first had to parse and somewhat interpret the command.\r\nIn an ideal world, the error message from the subsystem would properly describe what went wrong and so we would not need to guess. But at least on Windows, error messages are sometimes rather random text than helpful, IMHO.\r\n"}],"action":{"name":"View Pull Request","url":"https://github.com/geany/geany/pull/1166#issuecomment-243063113"}}}</script>