Bug 539165 - API to configure ContentAssistant to ignore completion trigger chars
Summary: API to configure ContentAssistant to ignore completion trigger chars
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 4.8   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 4.10 M1   Edit
Assignee: Mickael Istria CLA
QA Contact:
URL:
Whiteboard:
Keywords: api, noteworthy
Depends on:
Blocks: 348857
  Show dependency tree
 
Reported: 2018-09-17 16:53 EDT by Mickael Istria CLA
Modified: 2018-10-10 08:04 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mickael Istria CLA 2018-09-17 16:53:25 EDT
As the issue of auto-activate content-assist vs trigger chars (bug 348857) is pretty general and could apply to any editor, and since some extensions may assume that content-assist is always triggered manually and then can rely a lot on trigger chars, we need a generic way to disable those for any editor.

I suggest addition of a ContentAssistant.enableCompletionTriggerChars(boolean) method. By default, trigger char are enabled.
Comment 1 Mickael Istria CLA 2018-09-17 16:58:00 EDT
This involves adding a flag + getter + setter in ContentAssistant, and using this flag in CompletionProposalPopup.verifyKey(...)
Comment 2 Eclipse Genie CLA 2018-09-17 17:55:52 EDT
New Gerrit change created: https://git.eclipse.org/r/129576
Comment 4 Eclipse Genie CLA 2018-09-18 04:58:04 EDT
New Gerrit change created: https://git.eclipse.org/r/129603
Comment 6 Lars Vogel CLA 2018-09-18 05:10:49 EDT
Please add to N&N before marking as fixed.