unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philipp Haselwarter <philipp@haselwarter.org>
To: emacs-devel@gnu.org
Subject: Re: Does CEDET work?
Date: Thu, 26 Apr 2012 21:13:34 +0200	[thread overview]
Message-ID: <878vhie275.fsf@nzebook.haselwarter.org> (raw)
In-Reply-To: CANbX365-B15JBWe6s4JU3KTSvSmaF5sTvpd=e-2izzbCtP1nhg@mail.gmail.com

On Thu, Apr 26 2012 20:26 (@1335464766), Lennart Borgman wrote:

> On Thu, Apr 26, 2012 at 20:14, Philipp Haselwarter <philipp@haselwarter.org> wrote:
>
>     This is what most of the folks that see me using Emacs for C code (which
>     is arguably the language best supported by CEDET) want to have for
>     /their/ setup. Apart from a functioning CEDET, auto-complete is *very*
>     appealing visually and a for many (novice-) users a more attractive way
>     to be presented with context-completion than a completion-buffer
>     (actually the interface is provided by popup.el). It'd be nice to have
>     this in stock Emacs.
>    
>     As Eric has pointed out himself, the entry barrier is quite high though
>     and support for other languages often requires difficult customizations
>     (if possible at all).
>    
>     A better integration by default for some of the most-used languages
>     would increase Emacs's usefulness tremendously for the majority of
>     people writing code, which in my understanding is the main purpose of
>     Emacs.
>
> The CEDET framework is there, but the support for a language could be
> on many levels. Is there somewhere a table over the support for
> different languages?
>  


There is, at http://cedet.sourceforge.net/languagesupport.shtml

I just caught up on the cedet-ml and saw that the newtrunk branch got
merged (yay!).  This could be a Big Thing if it means that integration
and accessibility become an Emacs issue (as opposed to a
not-an-emacs-but-someone-other-package's-issue).


-- 
Philipp Haselwarter




  reply	other threads:[~2012-04-26 19:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18 21:36 Does CEDET work? Jordi Gutiérrez Hermoso
2012-04-18 22:05 ` joakim
2012-04-18 21:39   ` Leo
2012-04-19  1:50     ` Eric M. Ludlam
2012-04-19  2:03     ` Óscar Fuentes
2012-04-19  5:47       ` Andreas Röhler
2012-04-19  1:35 ` Tom Tromey
2012-04-19  4:29 ` Les Harris
2012-04-19  4:59   ` Jambunathan K
2012-04-19  5:22     ` Les Harris
2012-04-19 15:52       ` Jordi Gutiérrez Hermoso
2012-04-19 17:22         ` Aneesh Kumar K.V
2012-04-23 12:50   ` Nix
2012-04-26 18:14   ` Philipp Haselwarter
2012-04-26 18:26     ` Lennart Borgman
2012-04-26 19:13       ` Philipp Haselwarter [this message]
2012-04-26 19:17         ` Lennart Borgman
2012-04-26 23:36           ` Eric M. Ludlam
2012-04-26 23:58             ` Lennart Borgman
2012-04-26 18:42     ` David Engster
2012-04-26 21:11     ` Stefan Monnier

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878vhie275.fsf@nzebook.haselwarter.org \
    --to=philipp@haselwarter.org \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).