|
From: | Dmitry Gutov |
Subject: | Re: xref--read-identifier should call project-identifier-completion-table? |
Date: | Mon, 3 Aug 2015 12:56:14 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:40.0) Gecko/20100101 Thunderbird/40.0 |
On 08/03/2015 12:47 PM, Stephen Leake wrote:
The default method for project-identifier-completion-table uses the current xref buffer-local variable, so that's the same as the current behavior. It might be better to change that to have a project- prefix.
What's the use, if the rest of the operations still use the buffer-local value of xref-find-function?
You'll get Elisp identifiers in completion, but won't be able to navigate to them.
The natural extension of this approach would be to have a project-xref-backend accessor, but do we really need that?
The same minor mode that enables your project globally could set xref-backend (the variable is still called xref-find-function, but not for long) in all buffers. It'll actually be a list, so you'll put an always-active element at its head, just like with project-find-functions.
[Prev in Thread] | Current Thread | [Next in Thread] |