Bug 575572 - Content Assist
Summary: Content Assist
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.20   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2021-08-23 07:59 EDT by Leonid Shalaev CLA
Modified: 2023-09-10 02:50 EDT (History)
2 users (show)

See Also:


Attachments
screenshots (85.42 KB, application/octet-stream)
2021-08-23 07:59 EDT, Leonid Shalaev CLA
no flags Details
4.21 (41.38 KB, image/png)
2021-09-15 07:09 EDT, Leonid Shalaev CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Leonid Shalaev CLA 2021-08-23 07:59:42 EDT
Created attachment 286986 [details]
screenshots

in some cases Content Assist do not starts after pushing (Ctrl+space)
Comment 1 Rolf Theunissen CLA 2021-08-23 09:39:44 EDT
Looks like Java code, moving to the JDT project.
Comment 2 Andrey Loskutov CLA 2021-08-23 14:03:24 EDT
Please check with latest 4.21 M3 build. We've fixed multiple content assist regressions we had in 4.20, see bug 574913
Comment 3 Leonid Shalaev CLA 2021-09-15 07:08:34 EDT
bug still exists even in 4.21
Comment 4 Leonid Shalaev CLA 2021-09-15 07:09:21 EDT
Created attachment 287134 [details]
4.21

bug still exists even in 4.21
Comment 5 Andrey Loskutov CLA 2021-09-15 07:23:36 EDT
(In reply to Leonid Shalaev from comment #4)
> Created attachment 287134 [details]
> 4.21
> 
> bug still exists even in 4.21

I can't reproduce.

Please provide a simple java class demonstrating the problem.
Comment 6 Holger Voormann CLA 2021-09-19 14:18:29 EDT
I cannot reproduce it either, neither in 4.21, nor in I20210917-1800, with the following code:
	class bug_575422 {
		void sample(StringBuilder sb) {
			for (int i = 6; i < In/*content assist here*/ ; i++) {
				sb.append('.');
			}
		}
	}
Comment 7 Eclipse Genie CLA 2023-09-10 02:50:11 EDT
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.