Re: A guide on setting up C/C++ development environment for Emacs

[Jai Dayal]

>I'll assume
that the directions given on the guide will make me more productive
while working on X.

Sure, however, if X is inherently broken, that's a completely unrelated
discussion. The author of the manual here isn't even involved in CEDET.

>Giving a heads-up is appropiate here.

Then giving a heads-up in regards to Emacs is completely valid, and all
discussion, in this thread, on Emacs' short-comings are completely valid as
well? That's horrible logic.


On Wed, Aug 27, 2014 at 3:28 PM, Óscar Fuentes <ofv@wanadoo.es> wrote:

> Jai Dayal <dayalsoap@gmail.com> writes:
>
> > Okay, then what's the limit? Should we discuss Emacs' limitations as an
> IDE
> > all together to avoid disappointed people? His manual is about how to
> > properly setup the CEDET tool, it is not about how to evaluate CEDET to
> > determine if it's sufficient or not.
>
> If I see a "Guide for setting up X development environment", I'll assume
> that the directions given on the guide will make me more productive
> while working on X. For the specific case of CEDET/C++ combo, that's far
> from assured. Giving a heads-up is appropiate here. Then each individual
> can decide if they invest time on the effort.
>
> In any case, thanks to the OP for writing the guide. I skimmed over it
> and looks like worth reading even for a veteran Emacs/C++ dev like me.
> It already mentions that CEDET is slow, (which I don't think it is the
> real problem) but says nothing about its limitations when using the
> built-in C++ parser.
>
>
>