Pekka Klärck

For me the biggest issue with `Set Variable` is the inconsistency with `Set Global/Suite/Test Variable`. Having simple syntax that covers all these needs is a win. Still need to make...

I've started implementing this and progress has been pretty good. I have the parser part done locally, but I still want to integrate the new functionality to the execution side...

Decision: I believe we don't need `resolve` (or `resolve_name`) option for controlling should the name be resolved and the resulting value used as the name or not. As others have...

With `${scalar}` variables we need to decide how to handle there more or less values than one: ``` VAR ${x} first second VAR ${y} ``` We have the same situation...

There hasn't been too much interest towards this lately. I'll move this from RF 7 scope to 7.1.

`.--version` and `--help` honoring `--nostatusrc` would be a good idea. Unlike changing the default behavior, it would be totally backwards compatible. It ought to be easy to implement as well....

Is this still a problem?

Yes, this is still open. See also related #4068. Ping me on the #devel channel in our Slack if you need any help!

This issue exists to track the progress of renaming `Force Tags` to `Test Tags` and removing `Default Tags`. We have added `Test Tags` in RF 6.0 (#4368) and the `-tag`...

@glueologist You have a very good point related to backwards compatibility. We do take it seriously, but in this particular case we believe changes are worth the problems they cause....