<p>The idea sounds useful, for languages that don't have to put every class in its own file.  My current project has <code>parse()</code> in each of ten classes.</p>
<p>Maybe replace the filename with the scope otherwise where the scope is a nested thing (eg <code>my_namespace::my_sub_namespace::my_class::my_nested_class</code>) the popup may get a bit big.</p>
<p>Or have preferences that allow the user to choose one or both and can then the list be expanded to add any other potential disambiguating information.</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/1398#issuecomment-280180672">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ1RJLbvDxnrK53dZD5FVwHLc6CeNks5rc48_gaJpZM4MCYy_">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ8o3fL5cz18cnrrObIbPZhVbT69pks5rc48_gaJpZM4MCYy_.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/1398#issuecomment-280180672"></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":"@elextr in #1398: The idea sounds useful, for languages that don't have to put every class in its own file.  My current project has `parse()` in each of ten classes.\r\n\r\nMaybe replace the filename with the scope otherwise where the scope is a nested thing (eg `my_namespace::my_sub_namespace::my_class::my_nested_class`) the popup may get a bit big.  \r\n\r\nOr have preferences that allow the user to choose one or both and can then the list be expanded to add any other potential disambiguating information."}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/1398#issuecomment-280180672"}}}</script>