Yes, that was what I meant by " if this character is a . then it wrongly adds an object as a variable. I uploaded a fix for this."
Sorry I tend to modify a post when I discover something new revelant to that post.
EDIT
I don't get that if I understand correctly - see my image in post 21 (just tested with /l:de-de and still doesn't create variables for each character typed).
I can't see how this could happen unless you type a space after each character and then delete the space for example, or if there is something in the way your keyboard works that causes a similar effect.
EDIT2
I was able to reproduce Scout's issue by putting a space in a line, then moving cursor to before the space and type a word. Every time a letter is typed it sees the word+space and thinks this is a finished word.
This would clearly happen a lot typing into an existing line before a space for example.
Can't win them all, I guess it all depends on how folk use it, but I think the big win is we understand the rules and there are a couple options (Options Parse variables as they are typed and Format that also rechecks all variables).
Thanks to Scout and AB for working to improve this.
EDIT3
Uploaded a version where it checks for variable assignment before adding to list of variables when parsing current line. That is, there must be a = following the variable (optionally after white space). Variables only need to be found once to be added and when a new variable is added by user it almost always is initially set to a value.
Sorry I tend to modify a post when I discover something new revelant to that post.
EDIT
I don't get that if I understand correctly - see my image in post 21 (just tested with /l:de-de and still doesn't create variables for each character typed).
I can't see how this could happen unless you type a space after each character and then delete the space for example, or if there is something in the way your keyboard works that causes a similar effect.
EDIT2
I was able to reproduce Scout's issue by putting a space in a line, then moving cursor to before the space and type a word. Every time a letter is typed it sees the word+space and thinks this is a finished word.
This would clearly happen a lot typing into an existing line before a space for example.
Can't win them all, I guess it all depends on how folk use it, but I think the big win is we understand the rules and there are a couple options (Options Parse variables as they are typed and Format that also rechecks all variables).
Thanks to Scout and AB for working to improve this.
EDIT3
Uploaded a version where it checks for variable assignment before adding to list of variables when parsing current line. That is, there must be a = following the variable (optionally after white space). Variables only need to be found once to be added and when a new variable is added by user it almost always is initially set to a value.