Currently the extension, for the tagWord and tagComplete commands, uses the
following sources (ordered by descending priority):

1. The available abbreviations (from the Toolbox and Projects).
2. Internal snippets (from library/tagSnippets).
3. An array of existing HTML tags (+ empty and block elements, not sure in
what exact order the checks are done).

I can see users not wanting HTML Toolkit to use abbreviations. Or not
wanting it to use the internal snippets. Disabling the third source should
not be an option.

So maybe there could be options for #1 and #2 (in some preferences dialog).
The priority order should not change, but the user could choose to skip
step #1 or step #2 or both.

Options could look like this:

When autocompleting tags…
[x] Use the available abbreviations from the Toolbox or Projects
[x] Use the built-in snippets (eg. <a href=""></a> instead of <a></a>)

As a reminder, i talked about disabling another feature the other day, with
options such as:

When completing block-level HTML tags…
[x] Leave a blank line between the start and end tags
[x] … and indent that new line once

BUT, i'm not saying there should be options for everything. No need for
anyone (i think) to disable the CSS image hyperlink, the unobtrusive &nbsp;
shortcut, the jumpClosingTag or wrapBlockInTags features, etc. Or there
might be a need for SOME people, but definitely a tiny minority.