Autocomplete won't work when keywords start with a non-word character

[ktekinay]

For example, in Xojo there are keywords that start with "#" (#pragma, #endif, etc.). Autocomplete will not trigger on these.

A solution is to scan the first character of every keyword in the definition file for non-word characters and add those to the regex pattern that will identify the start of a new word.

Another solution is to let the user specify such special characters either at runtime and/or through the definition file. This will be needed if the user wants to add such autocomplete words that are separate from the keywords found in the definition file.