From: Judeau <solidius4747@gmail.com>
To: Help-gnu-emacs@gnu.org
Subject: Re: Why code completion using CEDET in Emacs so slow?
Date: Wed, 12 Oct 2011 11:54:52 -0700 (PDT) [thread overview]
Message-ID: <32640549.post@talk.nabble.com> (raw)
In-Reply-To: <87vcruqd7c.fsf@arcor.de>
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. When I look up everything
in boost:: namespace, it takes a long time. For small project, it is always
usable and fast enough, but parsing included files from large library is
always long, and every time a new symbol is looked up if I use
semantic-complete-self-insert for every member selection (using . or ->, it
still has a brief delay i ,which is still annoying. After the first time,
everything seems fine, sometimes a brief delay happens when look up, but
usually it is instant. Because of the time taken to parse, I usually type
manually and use auto-complete mode instead.
Due to this reason, I have hard time to convince people to start trying
Emacs.
--
View this message in context: http://old.nabble.com/Why-code-completion-using-CEDET-in-Emacs-so-slow--tp32638310p32640549.html
Sent from the Emacs - Help mailing list archive at Nabble.com.
next prev parent reply other threads:[~2011-10-12 18:54 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 [this message]
2011-10-12 19:15 ` David Engster
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=32640549.post@talk.nabble.com \
--to=solidius4747@gmail.com \
--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.
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.