[Top][All Lists]

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

Re: master 1e3b0f2: Improve doc strings of project.el

From: Kévin Le Gouguec
Subject: Re: master 1e3b0f2: Improve doc strings of project.el
Date: Sat, 20 Jun 2020 13:46:36 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)

Dmitry Gutov <dgutov@yandex.ru> writes:

> On 20.06.2020 11:55, Eli Zaretskii wrote:
>> I proposed to find a different way of telling which buffer is related
>> to a project, other than by looking at its default-directory.  We
>> could design a way of doing that which would then support adding
>> buffers to a project quite easily.  But Dmitry doesn't think we should
>> go that way.
> If you can outline and propose that alternative way, I'm all for
> considering it.

A few messages back, Eli said:

>                                                        If we really
> want to record in these buffers what project they are related to, we
> need to have stronger evidence, like what was the current-buffer when
> the command was invoked, or maybe something else (like name the
> buffers in some special way).

Where "these buffers" refers, IIUC, to "stuff like *XREF*, Eshell,
Occur, *Compilation*, *Grep*, etc.".

Would it make sense for these special modes to have a buffer-local
variable pointing to the buffer where the command was invoked?
project.el could then consult that variable first, then fallback to

reply via email to

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