Hilary James Oliver

(It is interesting that a fair number of people are evidently using the "wrong" syntax though!)

> I think we need to address this as we currently support two syntaxes, but only one of them globally, which is highly confusing. "currently support two syntaxes" is a...

> inherit statements (which must be going through a different interface for some reason?). That's done by `NameExpander.expand_parent_names()`. It's a different interface from name expansion in the graph and in...

> I don't think we can change this as a large number of workflows are relying on this behaviour to strip arbitrary whitespace from environment variables. Presumably you mean this...

Test drive it: ```ini [scheduling] [[graph]] R1 = a [runtime] [[a]] script = """ echo "only space: >>>${ONLY_SPACE}${LEADING_SPACE}" echo "trailing : ${TRAILING_SPACE}${UNQUOTED1}${UNQUOTED2} > x trailing : y >z>z

> After a quick scan it looks like a high proportion of workflows match the pattern "$ (which largely yields [environment] results). Not sure I understand that, can you give...

> It's a but difficult to scan for this one, will try and get a better handle on the likelyhood of issues and get back. Cool, thanks. > It is...

Sure, fair enough.

Re-targeted to master and 8.1.0 TBD: - fix the trailing comment case above - consider the likely impact on users, and hence whether or not we should continue optional support...

**Proposal:** if there are no existing flows, triggered tasks should default to [UPDATE after discussion below]~~all~~ *the most recent* previous flow~~s~~. This can only happen: - on restarting a completed...