From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Eric M. Ludlam" Newsgroups: gmane.emacs.devel Subject: Re: Current CEDET version in the trunk Date: Tue, 13 Jul 2010 22:45:55 -0400 Message-ID: <4C3D24E3.9040503@siege-engine.com> References: <4C3D09CF.2050203@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1279074684 11779 80.91.229.12 (14 Jul 2010 02:31:24 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 14 Jul 2010 02:31:24 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 14 04:31:23 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 1OYrko-0002FQ-S9 for ged-emacs-devel@m.gmane.org; Wed, 14 Jul 2010 04:31:23 +0200 Original-Received: from localhost ([127.0.0.1]:43142 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OYrkn-0007hE-GI for ged-emacs-devel@m.gmane.org; Tue, 13 Jul 2010 22:31:21 -0400 Original-Received: from [140.186.70.92] (port=45826 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OYrki-0007h2-4V for emacs-devel@gnu.org; Tue, 13 Jul 2010 22:31:17 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OYrkg-0007sz-Tm for emacs-devel@gnu.org; Tue, 13 Jul 2010 22:31:16 -0400 Original-Received: from bird.interbax.net ([75.126.100.114]:33215) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OYrkg-0007sp-PQ for emacs-devel@gnu.org; Tue, 13 Jul 2010 22:31:14 -0400 Original-Received: (qmail 4082 invoked from network); 13 Jul 2010 21:31:13 -0500 Original-Received: from static-71-184-83-10.bstnma.fios.verizon.net (HELO ?192.168.1.201?) (71.184.83.10) by interbax.net with SMTP; 13 Jul 2010 21:31:12 -0500 User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.3a1pre) Gecko/20091222 Shredder/3.1a1pre In-Reply-To: <4C3D09CF.2050203@gmail.com> X-detected-operating-system: by eggs.gnu.org: Windows 98 (1) 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:127240 Archived-At: Hi On 07/13/2010 08:50 PM, Christoph wrote: > The Semantic manual is a good way to get started, but there are quite a > few things that do not work according to the manual and it is not > obvious how to make it work. For example, using Smart completion (with > semantic-complete-analyze-inline) the manual says that M-n/M-p select > the next/previous matches. This does not work. M-n/M-p does nothing. C-h > k in this mode says, the keys are not assigned to anything. The keymaps used for completion are done via pre-command-hook which obscures them from C-h k. I just tried it out and M-n and p work for me with CEDET/CVS in Emacs Lisp mode using the idle completion feature. > Maybe we should better integrate and polish certain features one at a > time. Semantic seems like a great first choice to me. Semantic-based > completion and code browsing out of the box. I still have not been able I tend to agree. While CEDET/Semantic has some completion UI tools, there are others completion UIs that just use the the smart completion back-end to calculate values. (ie - company mode, predictive, hippie expand) The Emacs community here has a wide range of choice for selecting the 'official' way of doing smart completion inline. Do not assume that the completion engine I wrote is particularly special just because it is in the semantic package. That said, it does have some cool features. ;) > Is anybody actively working on integrating CEDET better with Emacs right > now? Or do we just merge the snapshots into the trunk? Lluis is trying to setup an CEDET/bzr repository for me where merges can happen more easily. My most recent papers should be at the FSF now, allowing free-flowing patches and merges to occur. > Now, going through the manual and playing with it I found quite a few > inconsistencies/bugs. Where is the right place to report those? The GNU > bug tracker or the Sourceforge tracker? I use the cedet-devel mailing lists on the CEDET sourceforge site, and usually just fix things as they arrive. If changes go into Emacs, I'll eventually get them so that is fine with me also. Eric