From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: Ask etags to stop language auto-detection from falling back to Fortran and C?
Date: Fri, 12 Jan 2018 12:41:15 +0200 [thread overview]
Message-ID: <83efmv2wc4.fsf@gnu.org> (raw)
In-Reply-To: <70cbd666-ef0a-364c-4a6f-91ce88f1a819@yandex.ru> (message from Dmitry Gutov on Fri, 12 Jan 2018 13:03:44 +0300)
> Cc: emacs-devel@gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Fri, 12 Jan 2018 13:03:44 +0300
>
> 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(
Thanks. I consider these weak reasons, so it doesn't look a very
urgent issue, especially since running etags on all the files in a
tree is not a very wise thing to do anyway (as mentioned in
http://lists.gnu.org/archive/html/emacs-devel/2018-01/msg00383.html).
However, feel free to file a feature request on debbugs, the
implementation shouldn't be hard.
next prev parent reply other threads:[~2018-01-12 10:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 0:07 Ask etags to stop language auto-detection from falling back to Fortran and C? Dmitry Gutov
2018-01-11 16:41 ` Eli Zaretskii
2018-01-11 21:49 ` Dmitry Gutov
2018-01-12 8:16 ` Eli Zaretskii
2018-01-12 8:23 ` Dmitry Gutov
2018-01-12 9:41 ` Eli Zaretskii
2018-01-12 10:03 ` Dmitry Gutov
2018-01-12 10:41 ` Eli Zaretskii [this message]
2018-01-12 12:06 ` Dmitry Gutov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83efmv2wc4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.