<p>I'd vote rather for a more generic phrasing.<br>
<code>/usr/share</code> should be right for most users as this is usually the path used by distro packages. <code>/usr/local/share</code> is the default if you compile from source yourself and do not specify an installation prefix, this is not the way <em>most</em> users do install Geany, I guess.<br>
Those users who install Geany from source and use a custom prefix, probably know what they are doing and so also can mentally replace the provided default path in the documentation/README with that they used for <code>./configure</code>.</p>
<p>In the documentation, we already have a few paragraphs about different config/resource file paths, see <a href="http://geany.org/manual/#configuration-file-paths">http://geany.org/manual/#configuration-file-paths</a>. Maybe we could just refer to this part of the docs in the README?</p>
<p>Something like "$PREFIX" could rather increase confusion for users rather than solving it.</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/1640#issuecomment-336640804">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ6qiSfd7SbhpMX8kQydmn1CPW63lks5ssM4HgaJpZM4P5FsS">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJy5kHa6jpC5DaTa5T8CI94Qa8l4dks5ssM4HgaJpZM4P5FsS.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/1640#issuecomment-336640804"></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":"@eht16 in #1640: I'd vote rather for a more generic phrasing.\r\n`/usr/share` should be right for most users as this is usually the path used by distro packages. `/usr/local/share` is the default if you compile from source yourself and do not specify an installation prefix, this is not the way *most* users do install Geany, I guess.\r\nThose users who install Geany from source and use a custom prefix, probably know what they are doing and so also can mentally replace the provided default path in the documentation/README with that they used for `./configure`.\r\n\r\nIn the documentation, we already have a few paragraphs about different config/resource file paths, see http://geany.org/manual/#configuration-file-paths. Maybe we could just refer to this part of the docs in the README?\r\n\r\nSomething like \"$PREFIX\" could rather increase confusion for users rather than solving it."}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/1640#issuecomment-336640804"}}}</script>