unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: David Engster <deng@randomsample.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Why code completion using CEDET in Emacs so slow?
Date: Wed, 12 Oct 2011 21:15:26 +0200	[thread overview]
Message-ID: <87r52iqawh.fsf@arcor.de> (raw)
In-Reply-To: 32640549.post@talk.nabble.com

Judeau writes:
> David Engster wrote:
>> 
>> Yes. CEDET is written in Emacs Lisp, so it will always be slower than
>> those programs. Still, it should always be usable. Could you provide an
>> example file using boost::asio which demonstrates the slow completion?
>> 
>> -David
>> 
> I edited and supplied one example in above post.

I'm afraid I can't see any code there.

-David




  reply	other threads:[~2011-10-12 19:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-12 14:05 Why code completion using CEDET in Emacs so slow? Judeau
2011-10-12 17:42 ` David Engster
2011-10-12 18:08   ` Judeau
2011-10-12 18:25     ` David Engster
2011-10-12 18:54       ` Judeau
2011-10-12 19:15         ` David Engster [this message]
2011-10-13  3:57           ` Judeau
2011-10-13 16:02             ` David Engster

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=87r52iqawh.fsf@arcor.de \
    --to=deng@randomsample.de \
    --cc=help-gnu-emacs@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.
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).