Re: [ANN] project-buffers.el

[Steven Degutis <sbdegutis@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1449 bytes --]

I didn't realize Projectile had similar functionality until after I had
written project-buffers.el in the first place. And I probably wouldn't have
noticed, because I didn't realize that what I needed was similar to
Projectile until after `next-buffer-in-project` and
`previous-buffer-in-project` were written, because those were the two
functions I really wanted, and the functions `switch-project` and
`close-buffers-in-project` came afterwards due to a realization that they
would be really easy. Once those were written, it became more obvious that
what I had was similar to Projectile.

But now that I look at Projectile, I think it does Too Many Things™. For
example, to find a file in my project, I use find-file-in-repository
(MELPA) which does just one thing and does it extremely well. For running
tests in my project there are other utilities that do this too, same for
TAG files, grep, etc.

-Steven


On Mon, Apr 1, 2013 at 10:40 PM, Dmitry Gutov <dgutov@yandex.ru> wrote:

> Steven Degutis <sbdegutis@gmail.com> writes:
>
> > Thanks for the link, haven't seen that page before.
> >
> > Most packages on that page don't do what project-buffers.el does.
> >
> > Projectile almost does, but it doesn't have a per-project version of
> > next-buffer and previous-buffer, which was probably the main reason I
> > wrote project-buffers.el.
>
> You could have contributed two new commands to projectile, no?
>

[-- Attachment #2: Type: text/html, Size: 1928 bytes --]