What is a raw template? -or- Why do templates come up as completions?
There is an option to include "raw" templates as possible text completions. Raw templates
are ones where the variables (e.g. ${cursor}) are not evaluated. If the template name would
be a valid completion, you will see the template as a completion option. In case you noticed,
this is also why the TextComplete plugin has a dependency on the JDT-UI plugin. Variables
can not be evaluated because currently templates are only valid in a Java context, which
only applies if you are editing a Java file.
Why doesn't TextComplete work in [some editor implementation]?
There are a few possible reasons:
The editor is not a subclass of AbstractText Editor
The editor does not return an appopriate IDocumentProvider/IDocument
The editor does something else uncooperative
I don't like how TextCompletion tokenizes/how it pick words to use as completions.
Can I modify how it behaves?
You can change the "Additional characters to count as word completion" preference. TextCompletion
will count anything that matches Character.isJavaIdentifierPart() plus all characters in
this preference as part of a completion word.
How is TextCompletion different from Genady's Emacs Complete?
TextCompletion uses the Content Assist pop up, so it's GUI based rather than text/cycle based.
TextCompletion also does not track history or give preference to recently used completions.