Pekka Klärck

This issue has a big risk of not making it to RF 5.0. It would be nice to have it, but we also want that release out as soon as...

I had some time for coding on a train ride and decided to look at this myself. I noticed implementation isn't exactly trivial because we don't currently store custom patterns...

I initially decided to make it so that if you specify a custom pattern, then the argument must be a string. That turned out to be a bad idea, because...

This turned out to be quite a bit bigger task than I anticipated. Especially handling the `\` escape character in patterns was pretty complicated. It didn't actually work correctly earlier....

Thanks for testing the beta and bringing this issue up @oboehmer. Conflicts like you explain are certainly a problem with embedded arguments and using the `[^"]+` pattern is a common...

Although I think these changes now need to be reverted due to backwards incompatibility problems, it is certainly somewhat strange that if you have keyword like ``` *** Keywords ***...

This functionality was disabled in 28a50a13ff8693112937af3e0bf4c19a9a352348. This issue was accidentally closed because GitHub interpreted the wording in the commit message so, but this is in fact still open and now...

RF 6.0 (previously known as RF 5.1) enhanced conflict resolution significantly (#4454) and silently deprecated variables not matching custom embedded arguments patterns (#4462). We will make that deprecation more loud...

Yeah, `ROBOT_AUTO_KEYWORDS = False` is a bit ugly. Would it be better if there would some way to use the `@library` decorator that works with classes also with modules? AFAIK...

Is output.xml really big?