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 11:41:29 +0200 [thread overview]
Message-ID: <83k1wn2z3q.fsf@gnu.org> (raw)
In-Reply-To: <87f0ba0a-3999-fbb9-f3a1-cc6868445129@yandex.ru> (message from Dmitry Gutov on Fri, 12 Jan 2018 11:23:46 +0300)
> Cc: emacs-devel@gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Fri, 12 Jan 2018 11:23:46 +0300
>
> > It will only
> > try the fallbacks if all the means to detect the language failed. So
> > what do you mean by "detect, but without the fallbacks"?
>
> I'm saying I don't want the fallbacks. If you've failed to detect the
> language based on the file extension or the sharp-bang, stop, don't try
> to parse the file with something that will most likely get wrong results.
>
> > It will, for the files following --language=none on the command line
> > (but not for those that come before this switch). But if the
> > extension and/or sharp-bang are in the file, the detection should not
> > have failed,
>
> It does if etags is unfamiliar with the file's language.
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?
next prev parent reply other threads:[~2018-01-12 9: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 [this message]
2018-01-12 10:03 ` Dmitry Gutov
2018-01-12 10:41 ` Eli Zaretskii
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=83k1wn2z3q.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.