all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Tom Tromey <tom@tromey.com>
Cc: 26612@debbugs.gnu.org
Subject: bug#26612: 25.2; find-file.el -vs- project.el
Date: Sun, 6 Aug 2017 23:59:41 +0300	[thread overview]
Message-ID: <115a5b79-4865-c4e8-2208-2fa58f19b18f@yandex.ru> (raw)
In-Reply-To: <87tw1ledek.fsf@tromey.com>

On 8/6/17 3:41 AM, Tom Tromey wrote:

> Dmitry> What would that command be called, though? And what generic
> Dmitry> function(s) on projects will we need to add?
> 
> The plain function is ff-find-other-file, so maybe
> project-ff-find-other-file?

"ff" meaning "find file"? Not a very semantic name, I'd say.

> Dmitry> So maybe do a search inside project-file-completion-table, for a file
> Dmitry> name matching the current (but with swapped extension)?
> 
> That would work fine, at least as a first draft.

Great!

> As an aside, why are EDE and project.el separate things?

1. Written by different people at different times (naturally).

2. project.el is an API with a sample (ish) implementation based on VC. 
The idea is that core Emacs code (like commands we have in project.el) 
can rely on it, and then a third-party implementation like Projectile 
can define an adapter "project.el backend", and then the said Emacs 
commands will automatically use Projectile (its config files, efficient 
file cache, etc) when the user has Projectile installed. Same for EDE 
users, and we include such adapter already.

We want to improve the VC-backend project backend too, though.

3. For dependencies purposes: Projectile users won't want to load EDE.





      reply	other threads:[~2017-08-06 20:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-22 20:19 bug#26612: 25.2; find-file.el -vs- project.el Tom Tromey
2017-05-01  2:05 ` Dmitry Gutov
2017-08-06  0:41   ` Tom Tromey
2017-08-06 20:59     ` 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=115a5b79-4865-c4e8-2208-2fa58f19b18f@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=26612@debbugs.gnu.org \
    --cc=tom@tromey.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.