Community
Participate
Working Groups
Auto activation also currently causesan annoying popup on every keystroke in .java files that aren't in a JDT source folder. To reproduce: • Create a blank non-java project • create a .java file in it with basic content and open it in Java editor • trigger completion (manually or automatically) -» An annoying popup interrupts typing.
Instead of a popup, it would be better integrated to show the error as a completion proposal. Hitting enter on it would show the popup or directly bring to preferences.
This is really a rare setup. Most other Java related things won't work either, though not showing a dialog.
Not so rare to me, it happens once every week.
I'd rather see the error reported as an error completion proposal in the completion popup. This would be less interrupting. @Dani what do you think?
(In reply to Mickael Istria from comment #4) > I'd rather see the error reported as an error completion proposal in the > completion popup. This would be less interrupting. +1
Created attachment 284739 [details] Screenshot Mickael, is this the popup you are also seeing? Super annoying Do I understand you correctly that you want to write a log error message instead of the popup?
(In reply to Lars Vogel from comment #6) > Mickael, is this the popup you are also seeing? Super annoying Yes. > Do I understand you correctly that you want to write a log error message > instead of the popup? I basically want to show the content-assist popup as usual, but with 1st entry like "⚠️ Completion not available because this compilation unit is not part of a project".
What's even stranger is that for files that are not in workspace at all, then completion is somewhat available. I think a .java file that's in the workspace but out of a source folder should be equally capable as a non-workspace file.
New Gerrit change created: https://git.eclipse.org/r/c/jdt/eclipse.jdt.ui/+/177057
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.
