[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: Dmitry Gutov
Subject: Re: master 1e3b0f2: Improve doc strings of project.el
Date: Sun, 21 Jun 2020 02:17:34 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0

On 20.06.2020 15:25, Eli Zaretskii wrote:

Compared to an ad-hoc variable (or having a command that adds such a
buffer manually), I'd much prefer an automatic approach.

Not sure what does "automatic" mean here.  If that means using only
currently available buffer-local variables, then who's to say that
this is good enough?

And/or adding new custom variables and hooks.

Why limit ourselves to only such solutions?  the
few presented examples already uncovered some deficiencies in relying
on one such variable.

As explained in the other email, it's a matter of interpretation.

OTOH, we could introduce a new buffer-local variable to be
automatically set by, say, a find-file-hook, or by project-find-file,
or via some other feature we have.  Same with recording relevant
buffers in some project-specific data structure.

find-file-hook seems a bit late to use if we wanted to save which project the current command was called from.

project-find-file would only affect file-visiting buffers, and only ones that we already consider a part of the current project. So what new info would it save?

"Some other feature" sounds nice.

IOW, it sounds like we have any number of ways for doing something
like that, and the only argument is whether we should.

I'm still not certain of what is the optimal solution.

reply via email to

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