From: "Eric M. Ludlam" <eric@siege-engine.com>
To: emacs-devel@gnu.org
Subject: Re: Current CEDET version in the trunk
Date: Tue, 13 Jul 2010 22:45:55 -0400 [thread overview]
Message-ID: <4C3D24E3.9040503@siege-engine.com> (raw)
In-Reply-To: <4C3D09CF.2050203@gmail.com>
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
next prev parent reply other threads:[~2010-07-14 2:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 0:50 Current CEDET version in the trunk Christoph
2010-07-14 2:45 ` Eric M. Ludlam [this message]
2010-07-14 3:16 ` Christoph
2010-07-14 7:47 ` Lluís
2010-07-14 6:47 ` Eli Zaretskii
2010-07-14 7:06 ` David Kastrup
2010-07-14 7:34 ` Eli Zaretskii
2010-07-14 14:28 ` Chong Yidong
2010-07-14 14:27 ` Chong Yidong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C3D24E3.9040503@siege-engine.com \
--to=eric@siege-engine.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.