<p>IMO, it would be better as more verbatim text explaining what each command is doing and why, rather than some magic incantation people blindly poke into the terminal, but I'm not sure HACKING is the appropriate place for that (hence the suggestion for a wiki page).</p>
<p>Without more verbatim explanations, I would personally recommend something more like this:</p>
<div class="highlight highlight-source-shell"><pre><span class="pl-k">export</span> GEANY_DEV=<span class="pl-smi">$HOME</span>/geany-dev

<span class="pl-c"><span class="pl-c">#</span> one-time setup</span>
mkdir -p <span class="pl-smi">$GEANY_DEV</span>/build <span class="pl-smi">$GEANY_DEV</span>/prefix
<span class="pl-c1">cd</span> <span class="pl-smi">$GEANY_DEV</span>
git clone https://github.com/geany/geany.git <span class="pl-c1">source</span>
<span class="pl-c1">cd</span> <span class="pl-c1">source</span>
NOCONFIGURE=1 ./autogen.sh

<span class="pl-c"><span class="pl-c">#</span> configuring the build and when updating from Git</span>
<span class="pl-c1">cd</span> <span class="pl-smi">$GEANY_DEV</span>/build
../source/configure --prefix=<span class="pl-smi">$GEANY_DEV</span>/prefix

<span class="pl-c"><span class="pl-c">#</span> each rebuild/install/test</span>
make install

<span class="pl-c"><span class="pl-c">#</span> running with a local config directory</span>
<span class="pl-smi">$GEANY_DEV</span>/prefix/bin/geany -c <span class="pl-smi">$GEANY_DEV</span>/config</pre></div>
<p>Which results in a much more friendly directory structure like:</p>
<pre><code>$HOME/geany-dev
├── build
│   ├── ...build artifacts...
├── config
│   ├── ...local config...
├── prefix
│   ├── ...install artifacts...
└── source
    ├── ...source tree...
</code></pre>

<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/1690#issuecomment-344779949">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJxYegHSOqvmb9PNIb0F6KvPTcxRlks5s24gQgaJpZM4QeeXN">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ2_6fQtQoCe5owz4UHMx_yJ18pARks5s24gQgaJpZM4QeeXN.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/1690#issuecomment-344779949"></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":"@codebrainz in #1690: IMO, it would be better as more verbatim text explaining what each command is doing and why, rather than some magic incantation people blindly poke into the terminal, but I'm not sure HACKING is the appropriate place for that (hence the suggestion for a wiki page).\r\n\r\nWithout more verbatim explanations, I would personally recommend something more like this:\r\n\r\n```bash\r\nexport GEANY_DEV=$HOME/geany-dev\r\n\r\n# one-time setup\r\nmkdir -p $GEANY_DEV/build $GEANY_DEV/prefix\r\ncd $GEANY_DEV\r\ngit clone https://github.com/geany/geany.git source\r\ncd source\r\nNOCONFIGURE=1 ./autogen.sh\r\n\r\n# configuring the build and when updating from Git\r\ncd $GEANY_DEV/build\r\n../source/configure --prefix=$GEANY_DEV/prefix\r\n\r\n# each rebuild/install/test\r\nmake install\r\n\r\n# running with a local config directory\r\n$GEANY_DEV/prefix/bin/geany -c $GEANY_DEV/config\r\n```\r\n\r\nWhich results in a much more friendly directory structure like:\r\n\r\n```\r\n$HOME/geany-dev\r\n├── build\r\n│   ├── ...build artifacts...\r\n├── config\r\n│   ├── ...local config...\r\n├── prefix\r\n│   ├── ...install artifacts...\r\n└── source\r\n    ├── ...source tree...\r\n```"}],"action":{"name":"View Pull Request","url":"https://github.com/geany/geany/pull/1690#issuecomment-344779949"}}}</script>