This issue exists in the current extension, but it appears to have already been resolved in a forked project.

You can find the related discussion and fix here: cfmleditor issue #33
I believe a similar approach could be applied to address the problem in this extension as well.