Re: Ask etags to stop language auto-detection from falling back to Fortran and C?

[Dmitry Gutov <dgutov@yandex.ru>]

On 1/12/18 12:41 PM, Eli Zaretskii wrote:

> OK, so next question: why do you care about the fallbacks?  At worst,
> they will generate tags that no one will ever try to find, right?
> 
> IOW, can you present a real-life use case where these fallbacks do any
> harm?

a) That increases the parsing time. Like, makes in 2-3 times longer in 
one example I had.

b) It creates very weird entries, like some multiline undisplayable byte 
sequence in one example (an OTF file, IIRC), and those do show up in the 
completions list, for xref-find-references. Or C-u xref-find-definitions.

c) It does create false positives for real names. For instance, I can 
search for the definition of 'push' (a method in Ruby or JS), and it 
will show me these as possible destinations:

/home/dgutov/xxx/yyy/zzz/public/app/less/bs-less/mixins/grid.less
  33: .make-xs-column-push(
  57: .make-sm-column-push(
  85: .make-md-column-push(
113: .make-lg-column-push(