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: wbe@psr.com, 28403@debbugs.gnu.org
Subject: bug#28403: 25.2; find-tag works, but xref-find-definitions
Date: Thu, 14 Sep 2017 20:13:31 +0300	[thread overview]
Message-ID: <83zi9xmcec.fsf@gnu.org> (raw)
In-Reply-To: <48b2816b-6fa5-bb3e-14e3-fff85d4fbc14@yandex.ru> (message from Dmitry Gutov on Thu, 14 Sep 2017 15:13:33 +0300)

> Cc: wbe@psr.com, 28403@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Thu, 14 Sep 2017 15:13:33 +0300
> 
> On 9/13/17 6:32 PM, Eli Zaretskii wrote:
> 
> >> Should it be a defcustom in etags.el, then? That's not far from what I
> >> suggested in the first place.
> > 
> > That'd be okay, if the UI will be more friendly than letting the user
> > concoct a list of function symbols.
> 
> I'd approve probably any patch that makes 
> etags-xref-find-definitions-tag-order into a defcustom, or even creates 
> a new option governing it.
> 
> But maybe it's not necessary after all? I think we've addressed 
> Winston's needs in different ways by now.

I just feel that having a user-friendly defcustom would be more
future-proof.  Like I said: it's a fire escape.  Every complex feature
needs one.

> Maybe the manual should advertise the necessity to call etags with 
> --regexp in certain cases more prominently instead.

Until very recently, --regex didn't even document the
back-substitution feature it provides.  So we still have a way to go
in that direction.





  reply	other threads:[~2017-09-14 17:13 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-09 22:40 bug#28403: 25.2; find-tag works, but xref-find-definitions doesn't; bug? Winston
2017-09-09 22:58 ` Drew Adams
2017-09-09 23:10 ` Dmitry Gutov
2017-09-10  2:50 ` bug#28403: 25.2; find-tag works, but xref-find-definitions Winston
2017-09-10  9:01   ` Dmitry Gutov
2017-09-10 14:29   ` Eli Zaretskii
2017-09-10 21:43     ` Dmitry Gutov
2017-09-11  2:38       ` Eli Zaretskii
2017-09-11  8:58         ` Dmitry Gutov
2017-09-11 14:43           ` Eli Zaretskii
2017-09-12 23:40             ` Dmitry Gutov
2017-09-13 15:32               ` Eli Zaretskii
2017-09-14 12:13                 ` Dmitry Gutov
2017-09-14 17:13                   ` Eli Zaretskii [this message]
2017-09-19  0:44                     ` Dmitry Gutov
2017-09-19  3:58                       ` Eli Zaretskii
2017-09-10 14:52 ` Winston
2017-09-10 18:27 ` Winston
2017-09-10 19:09   ` Eli Zaretskii
2017-09-10 19:06 ` Winston
2017-09-10 19:10 ` Winston
2017-09-10 20:12 ` Winston
2017-09-11  2:31   ` Eli Zaretskii
2017-09-10 21:19 ` Winston
2017-09-10 21:35   ` Dmitry Gutov
2017-09-11  2:34   ` Eli Zaretskii
2017-09-11  3:19 ` Winston
2017-09-11  4:05 ` Winston
2017-09-11 16:23   ` Eli Zaretskii
2017-09-11  4:11 ` Winston
2017-09-11  5:02 ` Winston
2017-09-11 16:51   ` Eli Zaretskii
2017-09-14 17:37 ` Winston
2017-09-14 22:08   ` 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=83zi9xmcec.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=28403@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=wbe@psr.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).