[SQL Assist 6 Beta] snippet conflict with keywords

It looks like the snippets will not auto complete when there is a conflict with SQL keywords (and how that lookup is done)

My custom snippet 'ssf' (SELECT * FROM) completes fine.

The default snippets of 'case', 'being', 'proc' do not complete. It appears to be something related to the keyword lookup or conflict.

Or maybe I just broke something on my install :)

In such cases you cannot use snippet completion key while popup is active, but you can use Esc first and then completion key. Also if you don't like typing the snippet shortcut at all, just right-click in the editor and select it from the menu, for example, for "proc" choose use SQL Assistant -> Code Snippets -> proc (Ctrl+Enter)

As for keyboard use, try

proc + Esc + (Ctrl+Enter)

Hope this helps

This is the same reason why you cannot use a keyword as a snippet trigger word either, right?

That's correct. Unless you disable keyword suggestions completely. The keyword popup grabs input focus and shallows snippet completion key

I'd rather remove those words from the keyword list. That would work too, wouldn't it? But it would ruin case modification of formatting. Perhaps adding a '.' to the end of the snippet word helps (I began using that practice).

Last edited by gemisigo on Fri Jul 01, 2011 11:40 am; edited 1 time in total

Or you can shorten snippet names, for example, pr instead of proc, ca instead of case. That would make their use even more efficient, wouldn't it?

Removing from keyword list will impact keyword formatting.

You're right, removing from keyword list wasn't a good idea after all.

But shortening snippet keywords to 2 chars would require increasing Suggest Keyword After (chr) settings to 3 (or more) to work. By default it is set to 2 characters and then you get the popup instead of the snippet. I used to use last character for trigger. Now I had to add '.' to some my snippets (where required) so now I have some sort of a hybrid :) Many of the snippets work unaltered and those that were broken by keyword conflict regained their functionality with '.' as the trigger character. Pressing '.' dismisses the popup and triggers the snippet at the same time. 1 keypress instead of +Esc+Tab.