| Summary: | [rename][linked mode][content assist] Content assist during rename shows too many proposals if invoked where the variable is used | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Timo Kinnunen <timo.kinnunen> |
| Component: | Text | Assignee: | JDT-Text-Inbox <jdt-text-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | minor | ||
| Priority: | P3 | CC: | daniel_megert, timo.kinnunen |
| Version: | 4.4 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | stalebug | ||
|
Description
Timo Kinnunen
Bug 411414 could provide the detection code for when to suppress content assist. I cannot reproduce this using R4.3 [1]. Please reopen with more detailed steps if you see this in R4.3 or newer. [1] http://download.eclipse.org/eclipse/downloads/drops4/R-4.3-201306052000/ Reproduced in Eclipse SDK Version: 4.3.0 Build id: I20130605-2000 with the steps from description and using this code and these additional steps:
private void instanceMethod(String manager) {
String helper = "";
System.out.println(manager + " and " + |helper); // start rename with cursor at |
}
Start rename with cursor at the start of a variable name that's being passed to another function. Pressing 'a' displays a proposal list of classes starting from AbstractMethodError. Pressing backspace to erase the 'a' displays a list of all locals, fields and classes visible in scope.
OK, I see. This has nothing to do with auto activation. The same happens if you simply invoke content assist inside the linked mode. It works if the identifier is changed where it is declared, but not where it is used. Hmm, to me this seemed like an unintended interaction under very particular circumstances that should be prevented from happening and thus a change to Auto Activation, but that works for me as well. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |