emacs-devel
[Top][All Lists]
Advanced

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

Re: IDE


From: Dmitry Gutov
Subject: Re: IDE
Date: Tue, 27 Oct 2015 02:18:29 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 Thunderbird/42.0

On 10/27/2015 01:40 AM, Óscar Fuentes wrote:

For not-so-big C++ projects, that can be as useless as displaying all
the uses of "bar" on the code base.

Technically, it must be at least an order-of-magnitude better.

And there are other languages that we want to support, too. It's not just C++ out there.

If there is a common pattern, by all means, implement it (on a way that
provides for those subtle differences when they make sense.)

This kind of feature requests will have to be more detailed.

But those
packages still need to maintain compatibility with older Emacsen.

Not necessarily: they can have some duplication in the code, and work both ways.

Distributing the library on GNU ELPA instead of the Emacs core would
make things better for the external packages, though.

That's one solution, yes.

But then, what's
the difference from developing the library outside of Emacs core and
working directly with the authors of those external packages?

GNU ELPA is still a part of Emacs core, organizationally. Anyway, I don't understand the question.

If the
library or API is developed on emacs-devel, is it acceptable to design
it by the requirements of rtags, for instance?

Why not? As long as it's not *just* the requirements of rtags that are considered.



reply via email to

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