all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: "Stefan Monnier" <monnier@iro.umontreal.ca>,
	"João Távora" <joaotavora@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: scratch/eldoc-xref-project-gnu-elpa-core-packages b1631cd: Turn Eldoc, Xref and Project into GNU ELPA :core packages
Date: Tue, 12 May 2020 02:25:39 +0300	[thread overview]
Message-ID: <7335ba69-8555-5c3f-772c-0af20b0e5a8b@yandex.ru> (raw)
In-Reply-To: <jwvftc65ay2.fsf-monnier+emacs@gnu.org>

On 12.05.2020 02:17, Stefan Monnier wrote:
> IIUC a significant part of project's functionality works fine without
> xref, so you could consider that project does not Package-Require
> `xref`.

I don't know if that's true: project--files-in-directory is used a lot. 
For example, in the default impl of project-files (used to "transient" 
projects, as well as arbitrary user-defined projects that don't create 
their own implementation).

xref.el could be used without project.el, though (only the default 
xref-backend-references impl uses it, that code is old, and we could 
even make a point not to change it much in the future).



      reply	other threads:[~2020-05-11 23:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200511214134.32634.30981@vcs0.savannah.gnu.org>
     [not found] ` <20200511214135.F14AF20A23@vcs0.savannah.gnu.org>
2020-05-11 21:54   ` scratch/eldoc-xref-project-gnu-elpa-core-packages b1631cd: Turn Eldoc, Xref and Project into GNU ELPA :core packages Dmitry Gutov
2020-05-11 22:12     ` João Távora
2020-05-11 22:21       ` Dmitry Gutov
2020-05-11 22:36         ` João Távora
2020-05-11 23:17       ` Stefan Monnier
2020-05-11 23:25         ` Dmitry Gutov [this message]

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=7335ba69-8555-5c3f-772c-0af20b0e5a8b@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /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.