[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Making project-files the "canonical" generic

From: Dmitry Gutov
Subject: Re: Making project-files the "canonical" generic
Date: Fri, 18 Jan 2019 04:00:01 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:65.0) Gecko/20100101 Thunderbird/65.0

On 17.01.2019 16:25, Stefan Monnier wrote:
But again, why allow it?

For example because of backward compatibility.

We still consider project.el "experimental", and we should be allowed to roll back on bad ideas.

Or because there is one example of its possible use.

The sole goal of that example is to change the UI of project-find-file for its backend, and for that backend only.

That doesn't seem like a worthy goal.

And right now project-find-file is incompatible with that completion table. The obvious move it to make it use project-files instead, and thus project-file-completion-table entirely unused.

Another fix could be to (try to?) move the common-parent-directory logic into the default completion table. Not sure if it's feasible, but you could prove me wrong.

In that case, though, different project backends will be able to show different UIs to the users.

Why disallow it?

Per-backend, non-user-customizable UIs are bad. And we've seen no other use cases so far.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]