<blockquote>
<p>IMO if the new Python lexer is far off at all, it might be good to squelch that warning as it is just noise in the context of someone typing a necessarily - at times - broken source file.</p>
</blockquote>

<p>Hopefully not far - I believe <a href="https://github.com/geany/geany/pull/1160" class="issue-link js-issue-link" data-url="https://github.com/geany/geany/issues/1160" data-id="169007391" data-error-text="Failed to load issue title" data-permission-text="Issue title is private">#1160</a> is ready to be merged and then the new Python parser can be just copied with minimal changes.</p>

<p>Upstream ctags also reports line number in the warning so it's more descriptive (should get backported to Geany). Null tag names shouldn't be generated no matter what the user has typed and this message helps to detect an error in the parser which would otherwise be undetected.</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/357#issuecomment-243715608">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ76rRISWZPCKYf_pViHPplErm8Q3ks5qlU7jgaJpZM4CwWTi">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJwIeDX6Yx42h2xasb8p_X4QM9wAjks5qlU7jgaJpZM4CwWTi.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/357#issuecomment-243715608"></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":"@techee in #357: \u003e IMO if the new Python lexer is far off at all, it might be good to squelch that warning as it is just noise in the context of someone typing a necessarily - at times - broken source file.\r\n\r\nHopefully not far - I believe #1160 is ready to be merged and then the new Python parser can be just copied with minimal changes.\r\n\r\nUpstream ctags also reports line number in the warning so it's more descriptive (should get backported to Geany). Null tag names shouldn't be generated no matter what the user has typed and this message helps to detect an error in the parser which would otherwise be undetected."}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/357#issuecomment-243715608"}}}</script>