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: Mon, 11 Sep 2017 05:38:30 +0300 [thread overview]
Message-ID: <83k216t0wp.fsf@gnu.org> (raw)
In-Reply-To: <a35ca633-87fb-3185-a48b-9f4c6fef1eb7@yandex.ru> (message from Dmitry Gutov on Mon, 11 Sep 2017 00:43:51 +0300)
> Cc: 28403@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Mon, 11 Sep 2017 00:43:51 +0300
>
> > Dmitry, how about providing a more user-friendly customization to that
> > effect? As a "fire escape"?
>
> We can turn etags-xref-find-definitions-tag-order into a defcustom, with
> descriptions of what every possible element means.
I rather had in mind a variable with a few simple values, and a :set
function which would put what's needed into
etags-xref-find-definitions-tag-order. IOW, hide the complexity from
the UI.
> 1) I have hard time imagining how we're going to have descriptions for
> both tag-exact-match-p and tag-implicit-name-match-p that are different
> and make sense to the user.
Simple values with solve that. For starters, we could use just 2:
'exact' and 'fuzzy'.
> 2) The user will have to find out about
> etags-xref-find-definitions-tag-order first anyway.
Will be solved by having the defcustom under a more descriptive name.
And since this is a "fire escape", it will be needed relatively
rarely. The point is to have it, so we could point users to it.
> Or we could add a custom variable to xref with a higher-level meaning...
Yes.
> that would require support from backends, then.
Why?
next prev parent reply other threads:[~2017-09-11 2:38 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83k216t0wp.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 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.