Bug 538701 - Enable auto activation keys for content assists in MANIFEST.MF editor
Summary: Enable auto activation keys for content assists in MANIFEST.MF editor
Status: VERIFIED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.8   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 4.11 M1   Edit
Assignee: Julian Honnen CLA
QA Contact:
URL:
Whiteboard:
Keywords: bugday, helpwanted
Depends on:
Blocks:
 
Reported: 2018-09-06 05:13 EDT by Lars Vogel CLA
Modified: 2019-01-07 07:39 EST (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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