Bug 199795 - Hippie Completion is too slow
Summary: Hippie Completion is too slow
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.4   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2007-08-13 16:09 EDT by Felix Berger CLA
Modified: 2007-08-23 05:44 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Berger CLA 2007-08-13 16:09:52 EDT 
The implementation of the Emacs like Hippie completion is too slow to allow for regular use. It is such a great feature since in certain contexts it should yield the desired result where the content-assist would be too slow or even useless, for example within string literals.
Comment 1 Dani Megert CLA 2007-08-21 06:07:05 EDT 
Please provide more info/test case. See also:
http://www.eclipse.org/eclipse/platform-text/development/bug-incomplete.htm
Comment 2 Felix Berger CLA 2007-08-22 16:27:54 EDT 
If I'm not mistaken hippie completion is supposed to work as Emacs completion going backwards in the current buffer looking for possible completion entries.

The following case takes almost a second:

public void callSomeMethod() {
	delegate.callS [Call hippie completion]

The correct completion entry is the second item that should be looked at, but the call takes too long.
Comment 3 Dani Megert CLA 2007-08-23 05:44:44 EDT 
Your example gives an immediate result here using plain Eclipse SDK 3.4 M1 and with Java or Text editor.