unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: stephen_leake@stephe-leake.org, emacs-devel@gnu.org
Subject: Re: Allow xref to use other than current major-mode
Date: Tue, 25 Aug 2015 20:25:01 +0300	[thread overview]
Message-ID: <55DCA4ED.7060806@yandex.ru> (raw)
In-Reply-To: <83lhczfl3r.fsf@gnu.org>

On 08/25/2015 06:23 PM, Eli Zaretskii wrote:

> It would be nice to have that capability without the need to create a
> project.

There may be no need to "create" a project, for a particular backend. 
But a specialized backend (for instance, one for Emacs sources) will 
know the directory tree layout and where to get information from. In 
Emacs's case, for example, from find-func and TAGS files inside lisp/ 
and src/.

And how to combine the information from the different sources better.

> E.g., how about adding to Emacs a few back-ends that support
> widely used combinations of languages, like C and Lisp in our case?

Someone is welcome to take that up. It won't be on my list for a while, 
probably not until after the 25.1 feature freeze.



  reply	other threads:[~2015-08-25 17:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25 10:00 Allow xref to use other than current major-mode Stephen Leake
2015-08-25 11:48 ` Dmitry Gutov
2015-08-25 12:19   ` João Távora
2015-08-25 12:25   ` David Engster
2015-08-25 14:47     ` Stephen Leake
2015-08-25 15:07       ` David Engster
2015-08-25 15:23   ` Eli Zaretskii
2015-08-25 17:25     ` Dmitry Gutov [this message]
2015-08-25 21:17       ` Stephen Leake
2015-08-25 15:31   ` Stephen Leake
2015-08-25 15:41     ` Stephen Leake
2015-08-25 17:05     ` Dmitry Gutov
2015-08-25 21:13       ` Stephen Leake
2015-08-25 22:11         ` Dmitry Gutov
2015-08-25 22:15     ` Stefan Monnier
2015-08-25 22:29       ` 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=55DCA4ED.7060806@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stephen_leake@stephe-leake.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 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).