From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jai Dayal Newsgroups: gmane.emacs.help Subject: Re: A guide on setting up C/C++ development environment for Emacs Date: Wed, 27 Aug 2014 15:32:00 -0400 Message-ID: References: <513ad0e2-f7f4-484c-b17b-7c94a8c2fc7a@googlegroups.com> <8738chaieo.fsf@wanadoo.es> <87tx4x9353.fsf@wanadoo.es> <87ppfl91ft.fsf@wanadoo.es> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1409167961 17437 80.91.229.3 (27 Aug 2014 19:32:41 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 27 Aug 2014 19:32:41 +0000 (UTC) Cc: help-gnu-emacs To: =?UTF-8?Q?=C3=93scar_Fuentes?= Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Aug 27 21:32:34 2014 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XMixN-0003MF-N6 for geh-help-gnu-emacs@m.gmane.org; Wed, 27 Aug 2014 21:32:33 +0200 Original-Received: from localhost ([::1]:33033 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XMixN-0000wS-Au for geh-help-gnu-emacs@m.gmane.org; Wed, 27 Aug 2014 15:32:33 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58514) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XMixB-0000wL-Um for help-gnu-emacs@gnu.org; Wed, 27 Aug 2014 15:32:23 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XMixB-000637-0Q for help-gnu-emacs@gnu.org; Wed, 27 Aug 2014 15:32:21 -0400 Original-Received: from mail-vc0-x232.google.com ([2607:f8b0:400c:c03::232]:52720) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XMixA-000632-S7 for help-gnu-emacs@gnu.org; Wed, 27 Aug 2014 15:32:20 -0400 Original-Received: by mail-vc0-f178.google.com with SMTP id la4so146894vcb.9 for ; Wed, 27 Aug 2014 12:32:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=G8Awq3oVlIk61yg6+ytCrIjqH1Pn5fxI0fcUOj7Tazw=; b=GGLuQDS5jx29NPk8DLJ1jUwjiKyyJTbAn9ONuEgWR0jSf0nkKF5WhtXyZoTiOynm9c g7a0HRPQIwWdddp4XgR8wIguk++0dGMYO5pZ2AdH7vcaD+QpPAiYDb0wbpkb9qFtjtBB af8cewcFt1NtNiRj6UbCZNbk4N3RlycAg64yUJRYh91Pf7+P0ZyOQ03WaEWovAo5AT2q rp+JaMHKUPP7x0Vvqg+xX/sfj2Sf/KgWqlcBFGOMTZlK5ltZjC5klAvMQPHV+ssQKxvv EEgsKIlO/L3Zdj+/KNn9SwyZ/DqVE8x0V0n65Qnv0HiAgbNJjjQf9R8MrogRXqhDdRCB 6qAA== X-Received: by 10.52.245.66 with SMTP id xm2mr16418689vdc.36.1409167940337; Wed, 27 Aug 2014 12:32:20 -0700 (PDT) Original-Received: by 10.221.24.82 with HTTP; Wed, 27 Aug 2014 12:32:00 -0700 (PDT) In-Reply-To: <87ppfl91ft.fsf@wanadoo.es> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400c:c03::232 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:99438 Archived-At: >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, =C3=93scar Fuentes wrote: > Jai Dayal 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. > > >