unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 22947@debbugs.gnu.org, rogers@modulargenetics.com
Subject: bug#22947: 25.0.92; xref-find-definitions fails for Perl & etags
Date: Sat, 12 Mar 2016 09:41:42 +0200	[thread overview]
Message-ID: <83lh5ogn2h.fsf@gnu.org> (raw)
In-Reply-To: <7471846c-3ea0-f05f-23b5-deec649c89d5@yandex.ru> (message from Dmitry Gutov on Sat, 12 Mar 2016 03:08:13 +0200)

> Cc: 22947@debbugs.gnu.org, rogers@modulargenetics.com
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Sat, 12 Mar 2016 03:08:13 +0200
> 
> On 03/11/2016 04:59 PM, Eli Zaretskii wrote:
> 
> > I said "etags", not "emacs".
> 
> I don't think this implies any considerable amount of work in etags 
> either. I could be wrong, of course.

I just said that etags never had these features, so we are talking
about an enhancement, not a bugfix.

> >> We can perfectly well choose to support this feature only for a few
> >> languages. It's better than nothing.
> >
> > I'm not sure "better than nothing" is good enough.
> 
> I'm not buying the argument that doing the right thing is somehow 
> undesirable because we can't afford to do the perfect thing right now.

I'm not selling it.

> > Anyway, I don't really understand what we are arguing about.
> 
> I'm arguing that -Q should output both qualified and unqualified tags, 
> so that the result is actually useful.
> 
> You seem to be arguing towards -Q preserving the previous behavior of 
> the parser, _in certain languages_, no matter the usefulness of the 
> resulting tag files.

No, I'm just saying this is a new feature whose implementation costs
are unknown to me at this point.

> >> Ultimately, it's your choice, of course.
> >
> > Volunteers are free to beat me to it, if they have an itch to scratch.
> 
> If you've made a deliberate choice, it doesn't seem like a patch from a 
> volunteer that would make a different choice is likely to be accepted.

I've made no choices, except not to work on this today.  I don't
understand why you think I'm against adding such a feature, if done
cleanly.  It's almost a reason to take offense, since I never said
anything that could be interpreted as such an intent.





  reply	other threads:[~2016-03-12  7:41 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08 18:27 bug#22947: 25.0.92; xref-find-definitions fails for Perl & etags Bob Rogers
2016-03-09  1:52 ` Dmitry Gutov
2016-03-09  2:43   ` Bob Rogers
2016-03-10 13:20     ` Eli Zaretskii
2016-03-10 13:36       ` Dmitry Gutov
2016-03-10 14:16         ` Eli Zaretskii
2016-03-10 14:34           ` Dmitry Gutov
2016-03-10 15:31         ` Eli Zaretskii
2016-03-10 15:50           ` Dmitry Gutov
2016-03-10 16:22             ` Eli Zaretskii
2016-03-11  1:45               ` Dmitry Gutov
2016-03-11  8:04                 ` Eli Zaretskii
2016-03-11 12:46                   ` Dmitry Gutov
2016-03-11 14:59                     ` Eli Zaretskii
2016-03-12  1:08                       ` Dmitry Gutov
2016-03-12  7:41                         ` Eli Zaretskii [this message]
2016-03-12 12:10                           ` Dmitry Gutov
2016-03-12 12:33                             ` Eli Zaretskii
2016-03-12 12:46                               ` Dmitry Gutov
2016-03-12 16:09                                 ` Eli Zaretskii
2016-03-10 19:07           ` Bob Rogers
2016-03-10 20:32             ` Eli Zaretskii
2016-03-11 18:08               ` Bob Rogers
2016-03-11 18:34                 ` Eli Zaretskii
2016-03-11 19:05                   ` Bob Rogers
2016-03-12  0:50                     ` Dmitry Gutov
2022-04-26 12:40                       ` Lars Ingebrigtsen
2022-04-26 17:00                         ` Bob Rogers
2022-04-27 12:14                           ` Lars Ingebrigtsen
2016-03-11  1:28             ` 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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83lh5ogn2h.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22947@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=rogers@modulargenetics.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).