I looked around the forums but I did not see any reference to this problem.
If I start typing something and decide to backspace the Code Completion algorithm seems to handle things badly.
Example - Type exactly this (the items in the <brackets> indicate what to type):
dim<space>MyString<space>as<space>str<backspace-3-times><space>
This causes the editor to insert this:
dim<space>MyString<space>asAsciiz<space>
There are several problems with this result:
1) Pressing backspace 3 times takes out the "str" that was typed AND the preceding space back to the "as".
2) Pressing space then automatically selects Asciiz but puts the space AFTER the code that is added.
This is not specific to just this example. Other examples involving backspacing cause different but similar results. Maybe backspacing should disable code completion unless you hit a specific key after you get back to where you would like it to "help" again. Escape turns it off. Maybe after backspacing escape should turn it back on.
This is not an urgent problem but the next time you are looking at the editor a tweak would be nice.