From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: Emacs learning curve Date: Mon, 2 Aug 2010 20:43:53 +0200 Message-ID: References: <10954D02-E217-49F3-8824-757DA34074AB@gmail.com> <83zkxzakr0.fsf@gnu.org> <83pqyva8ms.fsf@gnu.org> <834ofczxv2.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: dough.gmane.org 1280774663 6326 80.91.229.12 (2 Aug 2010 18:44:23 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 2 Aug 2010 18:44:23 +0000 (UTC) Cc: emacs-devel@gnu.org To: Tom , "Eric M. Ludlam" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Aug 02 20:44:21 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Ofzzo-0002Lo-N5 for ged-emacs-devel@m.gmane.org; Mon, 02 Aug 2010 20:44:20 +0200 Original-Received: from localhost ([127.0.0.1]:52894 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ofzzo-00040a-5U for ged-emacs-devel@m.gmane.org; Mon, 02 Aug 2010 14:44:20 -0400 Original-Received: from [140.186.70.92] (port=59658 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ofzzj-00040L-6d for emacs-devel@gnu.org; Mon, 02 Aug 2010 14:44:16 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Ofzzh-0000im-VI for emacs-devel@gnu.org; Mon, 02 Aug 2010 14:44:15 -0400 Original-Received: from mail-qy0-f169.google.com ([209.85.216.169]:45287) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Ofzzh-0000ia-T7 for emacs-devel@gnu.org; Mon, 02 Aug 2010 14:44:13 -0400 Original-Received: by qyk12 with SMTP id 12so257828qyk.0 for ; Mon, 02 Aug 2010 11:44:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type; bh=7oy2vx8l7iIpvR236LBj6qMiAwIOxODm2yqY0XZTlLg=; b=PX7/5YtlFV4saLlpXZFtFHo/6+wKuqODqr4zlqJ6PyVQhnFCz1TQbzaRcsg3SmtMWE uNwyJy1EafQMbuT3lNznZzwN0prtelXalYGx9RBpgfEn+6AfxU8BHWWNpezDQmXVkekc AJqGFwOZHtF7OoH2EvAh5vasiJirOb9uxGLm8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=sbNFWe5iU5REPS/0ifhLX+zqsvxk21xs76kYfRMtg2GdqAMtetx1aXCj9Wzy60FBW0 cwx7vdf/pvBI/cgCKoAgajzBgwZpX9DIVZNGlp6tgpAkFhLkhwkMqUyUFeL5s+7kFVxz i069b8LsaUI48T93bwHuzZLEB74tS5sG9TWo4= Original-Received: by 10.224.62.196 with SMTP id y4mr2016437qah.171.1280774653134; Mon, 02 Aug 2010 11:44:13 -0700 (PDT) Original-Received: by 10.229.9.84 with HTTP; Mon, 2 Aug 2010 11:43:53 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:128149 Archived-At: On Mon, Aug 2, 2010 at 8:39 PM, Tom wrote: > > And why not add these by simply reusing the work of others? > > The most requested and popular features are code > completion, refactoring and such. I know CEDET can do some of > these, but I wonder if Emacs should harness the effort put into > these areas by other development teams. > > Take a look at the screenshots IdeBridge for example: > > http://www.emacswiki.org/emacs/IdeBridge > > > It uses SharpDevelop libraries to provide completion. I know a > pure elisp solution would be the best, but given the plethora of > languages it's not a realistic goal to provide a comprehensive > Elisp backend solution for everything due to limited developer > resources. > > The best approach may be to provide a standard code > completion (refactoring, documentation lookup, etc.) frontend in > Emacs into which any backend implementation can be > plugged. People would write bridge code like in the above example > to handle communication between the frontend and the selected > backend. There are no licensing issues, because it can work > with process communication. I think that CEDET already makes this possible, but Eric can surely give a better answer. (Maybe this should be pointed out very clearly in Emacs doc, at least as a goal?)