Bug 552893

Summary:	Activate JDT postfix completion by default
Product:	[Eclipse Project] JDT	Reporter:	Lars Vogel <Lars.Vogel>
Component:	UI	Assignee:	Roland Grunberg <rgrunber>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	Lars.Vogel, noopur_gupta, rgrunber
Version:	4.14
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug
Bug Depends on:	552146
Bug Blocks:

Description Lars Vogel

2019-11-11 04:42:14 EST

Bug 458804 introduced the possibility to use postfix completion. 

I suggest to add this to the default code completion engines, as it really useful and will not affect the existing engines (different activation position).

Comment 1 Roland Grunberg

2019-11-11 16:01:48 EST

I think this could be done given how the completions are mainly templates being applied. Have you observed any bugs with respect to applying the postfix completions at any points ? I know such bugs might exist and would need to be diagnosed as either bugs in the completion logic, or with jdt.core statement recovery.

Comment 2 Lars Vogel

2019-11-11 16:59:32 EST

For me postfix completion works fine.

Comment 3 Roland Grunberg

2019-11-14 11:40:51 EST

Doing this also means we don't have to rush Bug 550226 into 4.14. Since postfix completion is the only new content assist that I'm aware of that was added for the 4.14 release. If it's enabled by default, we don't have to use the code in that bug to ensure it gets disabled.

Comment 4 Noopur Gupta

2019-11-15 00:13:32 EST

I would also like to see postfix completion enabled by default as it's very useful but I would prefer to enable it after known bug 552146 is fixed so that we have a strategy to fix this type of issues involving recovery when reported later in other scenarios also.

Comment 5 Eclipse Genie

2021-11-05 08:14:41 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.

Comment 6 Eclipse Genie

2023-10-27 10:40:32 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.