Community
Participate
Working Groups
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.
This involves adding a flag + getter + setter in ContentAssistant, and using this flag in CompletionProposalPopup.verifyKey(...)
New Gerrit change created: https://git.eclipse.org/r/129576
Gerrit change https://git.eclipse.org/r/129576 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.text.git/commit/?id=3c80a177e44f9924952496eeb79d87b7ea955a9d
New Gerrit change created: https://git.eclipse.org/r/129603
Gerrit change https://git.eclipse.org/r/129603 was merged to [master]. Commit: http://git.eclipse.org/c/www.eclipse.org/eclipse/news.git/commit/?id=aef959c4a84dd0f54e28e93cc5ed03855e0111df
Please add to N&N before marking as fixed.
(In reply to Eclipse Genie from comment #5) > Gerrit change https://git.eclipse.org/r/129603 was merged to [master]. > Commit: > http://git.eclipse.org/c/www.eclipse.org/eclipse/news.git/commit/?id=aef959c4a84dd0f54e28e93cc5ed03855e0111df > Added bug number comment to the entry - http://git.eclipse.org/c/www.eclipse.org/eclipse/news.git/commit/?id=d1c56e924527a90d509951abf552ab103a459113