Fix A-Trust: Codes starting with letter

[mkg20001]

Codes starting with letter were broken

A negative lookahead for something that looks like a space-seperated otp code starting with a letter was added

[mkg20001]

Note that android doesn't support repetition for lookaheads so I had to manually expand it

[jd1378]

well, this is sad because I just triggered a release

[jd1378]

np, will do another release

[jd1378]

let me think about this, I don't like this solution

[mkg20001]

So the issue is that "TAN\n a b 1 2 3 4" will give the code 1234 because [^\d] is what terminates the parsing and a b will be treated as just a bunch of words. (?![a-z0-9] [a-z0-9] [a-z0-9] [a-z0-9]) is what matches "a b 1 2" (realizes the words aren't words but a code, due to the special one character formatting) and then goes on to parse the code as if [^\d] would have triggered (so it's basically [^ but with more complicated strings).

[jd1378]

I get it, what I don't remember is why I added the ignored words the way it is, and why I named it ignored words, because certainly adding [a-zA-Z0-9] [a-zA-Z0-9] [a-zA-Z0-9] [a-zA-Z0-9] ? to ignored Words array does the same thing

(this is where commenting stuff is necessary and I didn't lol)

[jd1378]

well I assume second usage of ignored words is unnecessary, because I don't remember the case and there isn't any test for it
if anything came up I will add it back again

I applied the change using the ignoredWords list and it's working

[jd1378]

release in v1.5.1