Bug 538701

Summary: Enable auto activation keys for content assists in MANIFEST.MF editor
Product: [Eclipse Project] PDE Reporter: Lars Vogel <Lars.Vogel>
Component: UIAssignee: Julian Honnen <julian.honnen>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: fabian.pfaff, julian.honnen, Lars.Vogel, Vikas.Chandra
Version: 4.8Keywords: bugday, helpwanted
Target Milestone: 4.11 M1   
Hardware: PC   
OS: Linux   
See Also: https://git.eclipse.org/r/133938
https://git.eclipse.org/c/pde/eclipse.pde.ui.git/commit/?id=574fd193dcdb98ea7064dcad224d5aff14c9b934
Whiteboard:

Description Lars Vogel CLA 2018-09-06 05:13:46 EDT
I only noticed today that the MANIFEST.MF editor offers code completion for Require-Bundle and others.

We should enable content assists by default for the normal keys. I suggest the alphabet plus "." and ",".
Comment 1 Lars Vogel CLA 2018-09-06 05:18:36 EDT
Fabian, let's collaborate on this.
Comment 2 Lars Vogel CLA 2018-12-12 08:38:52 EST
Julian, something for you?
Comment 3 Eclipse Genie CLA 2018-12-12 11:07:26 EST
New Gerrit change created: https://git.eclipse.org/r/133938
Comment 4 Julian Honnen CLA 2018-12-12 11:12:40 EST
I've also never noticed the content assist there before - auto activation should be great for discoverability.

Alphabet characters felt very intrusive, I've settled on the separation chars: ':', ' ', ',', '.', ';', '='
Comment 6 Lars Vogel CLA 2018-12-18 04:26:28 EST
Ok, let's start with this, even though I'm a big fan of all characters should trigger code completion similar to IntelliJ.

Thanks, Julian.
Comment 7 Vikas Chandra CLA 2019-01-07 04:58:18 EST
Julian/Lars, can you please verify this defect?
Comment 8 Julian Honnen CLA 2019-01-07 07:39:52 EST
Verified on I20190106-1800