You never want to set the current build command, thats the point, why do<br>
you want to set a command in an unknown source?<br>
<br>
"Current" is a state, not a thing, it may be different after the next user<br>
input.  You then don't know what you set.<br>
<br>
On 12 September 2016 at 15:47, Matthew Brush <notifications@github.com><br>
wrote:<br>
<br>
> That set_current functionality should not be added is the main point.<br>
><br>
> It's the only way to set the current build command, that's the rationale :)<br>
><br>
> An alternative would be a function like build_get_current_source() to get<br>
> the current build source and then use that the set it.<br>
><br>
> —<br>
> You are receiving this because you commented.<br>
> Reply to this email directly, view it on GitHub<br>
> <https://github.com/geany/geany/pull/1225#issuecomment-246255156>, or mute<br>
> the thread<br>
> <https://github.com/notifications/unsubscribe-auth/AAxgTT3kIokRylbrJo60os1T6MidhAGMks5qpOd0gaJpZM4J6CEe><br>
> .<br>
><br>


<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/1225#issuecomment-246255517">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ2ct1ZTAvezvbblFyEp3bE89K6tUks5qpOhIgaJpZM4J6CEe">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ-V1nWfT-YW0T_g0RoQkctCnIT0aks5qpOhIgaJpZM4J6CEe.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/1225#issuecomment-246255517"></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":"@elextr in #1225: You never want to set the current build command, thats the point, why do\nyou want to set a command in an unknown source?\n\n\"Current\" is a state, not a thing, it may be different after the next user\ninput.  You then don't know what you set.\n\nOn 12 September 2016 at 15:47, Matthew Brush \u003cnotifications@github.com\u003e\nwrote:\n\n\u003e That set_current functionality should not be added is the main point.\n\u003e\n\u003e It's the only way to set the current build command, that's the rationale :)\n\u003e\n\u003e An alternative would be a function like build_get_current_source() to get\n\u003e the current build source and then use that the set it.\n\u003e\n\u003e —\n\u003e You are receiving this because you commented.\n\u003e Reply to this email directly, view it on GitHub\n\u003e \u003chttps://github.com/geany/geany/pull/1225#issuecomment-246255156\u003e, or mute\n\u003e the thread\n\u003e \u003chttps://github.com/notifications/unsubscribe-auth/AAxgTT3kIokRylbrJo60os1T6MidhAGMks5qpOd0gaJpZM4J6CEe\u003e\n\u003e .\n\u003e\n"}],"action":{"name":"View Pull Request","url":"https://github.com/geany/geany/pull/1225#issuecomment-246255517"}}}</script>