Interaction of Auto Correct With AutoHotkey

[kleinfelter]

I'm seeing a strange interaction between Auto Correct in UltraEdit-32 v 11.20b and AutoHotkey. When I edit a Ruby file (I've added the Ruby wordfile content from the downloads section of this site), any line that begins with an 'e' gets the 'e' turned into an 'E' if I insert a tab before the 'e'.

Only for e/E -- no other letter. It can be a line that begins with just an e, or the line can begin with something like 'exxxxxx'. Only if AutoHotkey is also running. My AutoHotkey script is NOT changing the e. I've reduced my AutoHotkey script to a single line:
#Persistent
which only holds the null AutoHotkey script resident in memory -- and has AutoHotkey checking keystrokes for any hotkeys that might match the empty list of hotkeys.

I think I know what is happening. Since E is defined in the /C4"Ruby Constants/Strings" section, it is a candidate for Auto Correct. Somehow the combination of Auto Correct and AutoHotkey is causing UE to 'think' that the e is a complete token.

If you're unfamiliar with AutoHotkey, it is an open source utility for scripting Windows and for executing scripts when 'hot' keys are pressed.

Other than disabling Auto Correct, not using AutoHotkey, or deleting E as a keyword for Ruby, do I have any options for preventing this behavior?
TIA

[Mofi]

The Ruby wordfile is case-sensitive because there is no Nocase keyword in the language definition line.

You have identified correctly that "word" E is at /C4"Ruby Constants/Strings" and the auto correct feature is always correcting a lower case e to E.

Except the options you already have listed you can add also a lower case e to the wordfile in a single line before the line /C5"Ruby Methods".

WIN32OLE::VERSION WNOHANG WUNTRACED
e
/C5"Ruby Methods"

Now UltraEdit allows "word" E and e.